Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Syniverse

Syniverse is a United States headquartered wholesale telecommunications company that sits between mobile network operators rather than in front of consumers. Its mobility business runs inter-carrier roaming, IPX network and signaling, 5G SEPP, clearing and settlement, global SIM and satellite roaming for carriers, and none of that carrier-side estate is exposed as a public API. Its messaging business is the opposite: an A2P/CPaaS aggregator selling SMS, MMS, RCS, WhatsApp, push, voice, 10DLC campaign registration, messaging trust/anti-spam and mobile identity services to enterprises, and it is published through a genuine self-serve developer portal, the Syniverse Developer Community (SDC), where anyone can sign up for a free API key, read the docs, and download eleven Redoc-rendered OpenAPI/Swagger definitions. On network APIs Syniverse is a channel, not a source — it joined GSMA Open Gateway in April 2025 as a channel partner and announced an integration with Aduna in June 2025, but no CAMARA-defined API is documented or callable on its developer portal today.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Syniverse the way a machine reads it — 18 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Syniverse scores 51.0/100 (developing), with a separate agent-readiness read of 66/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 51.0/100 · developing
Contract Quality 15.3 / 25
Developer Ergonomics 13.0 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 5.8 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 66/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Syniverse

Each block below is one kind of artifact we hold for Syniverse. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 12

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Syniverse Omni-Channel Messaging API (SCG)

The Syniverse Communication Gateway (SCG) API — the core of the Syniverse Developer Community platform. 72 documented paths and 148 operations covering message requests, message...

Syniverse Multi-Factor Authentication API

Generates and validates one-time passwords and delivers customized tokens over SMS, voice or push to verify an end user. Documented as part of the SCG API surface with applicati...

Syniverse Phone Number Verification API

Single-number lookup service that returns the current carrier, line type and status of a phone number so an enterprise can detect ported, deactivated, disconnected or reassigned...

Syniverse Right Party Verification API

A single POST /v2/match operation that returns match scores comparing an end user's asserted identity against Syniverse-sourced mobile data. This is Syniverse's own identity-mat...

Syniverse Account Takeover Detection API

A single POST /v1/simCheck operation that reports whether an end user's mobile channel has had recent SIM changes or call forwarding enabled, as an account-takeover risk signal....

Syniverse Messaging Trust Resolve API

Resolves inbound text and MMS traffic to a disposition — the spam and messaging-abuse classification service sold to messaging operators and enterprises. Two operations, /v1/txt...

Syniverse Messaging Trust Spam Datafeed API

Submits spam reports into the Messaging Trust datafeed via a single POST /spam/report operation, secured with OAuth2 client credentials against the Messaging Trust token endpoint.

Syniverse 10DLC API

US 10DLC (10-digit long code) campaign provisioning — create, retrieve, suspend and resume campaigns, attach and detach long codes and number pools, and manage AT&T DCA campaign...

Syniverse 10DLC Number Pool API (v1, deprecated)

The deprecated version 1 of the 10DLC provisioning API, still published in the SDC documentation under an explicitly deprecated section. Adds and removes 10DLC long codes and nu...

Syniverse Whitelisting Service API

Developer Community gateway service for managing whitelists of entities and transactions, used to allow trial-account destination numbers and similar platform-level allow lists....

Syniverse SDC Application Access Token Management API

Regenerates the access token associated with an SDC application via GET /saop-rest-data/v1/apptoken-refresh. This is the token-lifecycle piece of the Syniverse Developer Communi...

Syniverse Event Subscription Service API (Event Manager)

The webhook and event layer of the Syniverse Developer Community. The Event Subscription Service (ESS) API manages topics, topic-subscriptions, delivery-configurations, event-ty...

Scroll within the panel for all 12 ·

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Syniverse Rate Limits

4 limits

RATE LIMITS

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Syniverse Authentication

apiKey/http/oauth2 · 5 schemes

SECURITY

Syniverse Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Syniverse Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Syniverse Agentic Access

187 operations · 117 acting

187 operations · 117 acting

AGENTIC

Resources

Every other property we hold for Syniverse — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Company 4

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/syniverse · machine-readable index on apis.io