Swisscom
Swisscom is Switzerland's largest telecommunications provider and the incumbent mobile network operator, fixed-line carrier and IT services company for the Swiss market, majority-owned by the Swiss Confederation and also operating Fastweb in Italy. In the telecom value chain it is a facilities-based MNO that owns the radio access and core network, sells mobile, broadband, TV and enterprise IT, and monetises network-derived data. Its API posture is unusual for a European incumbent: alongside the expected partner-gated enterprise surface it runs a genuine first-party API marketplace at digital.swisscom.com listing ten productive API products (SMS, SMS token 2FA, inbound SMS, mobility heatmaps, dwell times, origin-destination, NATEL go smart catalogs, AI inference endpoints and a business identity validator) served from a live api.swisscom.com gateway, plus a separately maintained, actively released Swisscom Sign Integration API with a downloadable OpenAPI 3.1 document. The catch is that every API reference, key and spec beyond Swisscom Sign sits behind a Swisscom login and, for several products, a signed service contract — the marketplace is a storefront, not open documentation. On network APIs Swisscom was one of the 21 founding signatories of the GSMA Open Gateway Memorandum of Understanding in February 2023, but it publishes no CAMARA API, no Open Gateway developer portal and no callable network-API endpoint; developers who want SIM-swap or phone-verification signals from the Swisscom network have historically reached them through third-party channels such as IPification rather than from Swisscom directly. Its legacy developer programme (developer.swisscom.com, the Cloud Foundry Application Cloud, the swisscom-developer GitHub SDKs) is dead or redirected, and the older Messaging and Voice APIs are still documented only as RAML-rendered HTML in a GitHub wiki.
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.
API Evangelist profiles Swisscom the way a machine reads it — 21 machine-readable artifacts across 13 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 — Swisscom scores 59.2/100 (developing), with a separate agent-readiness read of 78/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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Swisscom
Each block below is one kind of artifact we hold for Swisscom. 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 13
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.
Swisscom Sign Integration API
REST API that lets backend systems create, configure, release and monitor digital signature processes end to end — create a process, attach PDF documents, invite signers, releas...
Swisscom All-in Signing Service (AIS) API
The Swisscom Trust Services All-in Signing Service REST interface for creating AdES signatures and seals under eIDAS and ZertES, following the ETSI TS 119 432 remote signature c...
Swisscom Text Messaging (SMS) API
Application-to-person SMS sending over the Swisscom messaging infrastructure with onward delivery to 260+ operators globally, including delivery-notification callbacks to a cust...
Swisscom Phone Number Validation API
Two-factor authentication API that starts an SMS token validation flow against an MSISDN and then verifies the token the user received. This is Swisscom's own SMS-OTP product, n...
Swisscom Receive SMS API
Inbound SMS API that exposes message inboxes so applications can receive texts from customers and build two-way messaging flows, alerting and device control alongside the outbou...
Swisscom Heatmaps API
Mobility Insights API returning estimated population density per 100m x 100m tile per hour across the whole of Switzerland, from yesterday back two years on a rolling window, wi...
Swisscom Dwell Times API
Mobility Insights API returning a frequency distribution of observed dwell times per 500m x 500m tile per day across Switzerland, bucketed from 0-5 minutes up to 8-24 hours, for...
Swisscom Origin Destination API
Mobility Insights API estimating the number of trips people make between two Swiss regions for weekdays and weekends over a full calendar month, including the share made by trai...
Swisscom Smart Catalogs for NATEL go API
Business/wholesale provisioning API covering the full NATEL go mobile subscription procurement lifecycle — activations, number portability, option and roaming configuration, SIM...
Swiss AI Platform Inference Endpoints API
OpenAI-compatible inference endpoints for chat, multimodal, audio, embedding, reasoning and guardrail models hosted by Swisscom on NVIDIA SuperPod infrastructure in Switzerland,...
Swisscom Business Identity Validator API
REST API that looks up legal entities and their authorised signatories against Swiss federal and cantonal commercial registries and selected EU business registers, for KYB onboa...
Swisscom Voice VoIP API
Legacy Voice API cluster for controlling a Swisscom VoIP subscriber — placing and listing calls, managing call forwardings, simultaneous ringing and phonebooks, and subscribing ...
Swisscom Voice Mail API
Legacy Voice API for listing and retrieving recent voicemail messages for a Swisscom MSISDN, secured by OAuth 2.0 client-credentials or authorization-code grants. Documented as ...
Scroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
swisscom-mcp.yml
MCP SERVEREvent 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.
Swisscom Messaging Webhooks
ASYNCAPISecurity Posture 4
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.
Swisscom Trust Center
Qualified certification service provider under ZertES, Qualified trust service provider under eIDAS, Remote signature issuance conformity under ZertES
SECURITYScopes 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.
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.
Resources
Every other property we hold for Swisscom — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 10
Authentication, authorization, and security posture
Scroll within the panel for all 10 ·
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/swisscom · machine-readable index on apis.io