Amazon SNS
Amazon Simple Notification Service (SNS) is a fully managed messaging service for both application-to-application (A2A) and application-to-person (A2P) communication. It enables pub/sub, SMS, email, and mobile push notifications.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon SNS the way a machine reads it — 115 machine-readable artifacts across 8 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 — Amazon SNS scores 62.2/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). 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 Amazon SNS
Each block below is one kind of artifact we hold for Amazon SNS. 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 8
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.
Amazon SNS ?Action=ListTagsForResource API
The ?Action=ListTagsForResource API from Amazon SNS — 1 operation(s) for ?action=listtagsforresource.
Amazon SNS ?Action=TagResource API
The ?Action=TagResource API from Amazon SNS — 1 operation(s) for ?action=tagresource.
Amazon SNS ?Action=UntagResource API
The ?Action=UntagResource API from Amazon SNS — 1 operation(s) for ?action=untagresource.
Amazon SNS Platform Applications API
Operations for managing platform applications used for mobile push notifications via APNs, FCM, and other push services.
Amazon SNS Publishing API
Operations for publishing messages to SNS topics or directly to endpoints. Messages can be plain text or structured JSON for per-protocol delivery.
Amazon SNS SMS API
Operations for managing SMS messaging attributes and phone number opt-out lists.
Amazon SNS Subscriptions API
Operations for subscribing endpoints to topics, confirming subscriptions, listing subscriptions, and unsubscribing. Subscriptions define which endpoints receive messages publish...
Amazon SNS Topics API
Operations for creating, listing, configuring, and deleting SNS topics. Topics are communication channels to which messages are published and from which notifications are delive...
Scroll within the panel for all 8 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Amazon SNS Amazon Simple Notification Service (SNS) API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
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.
Amazon Sns Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Sns Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Pub/Sub Messaging
Fan-out messages to multiple subscribers through topics supporting HTTP/S, email, SQS, Lambda, and SMS protocols.
FIFO Topics
Strict message ordering and exactly-once delivery for use cases requiring sequence-preserving fan-out.
Message Filtering
Subscription filter policies enabling subscribers to receive only the messages relevant to them.
Mobile Push Notifications
Cross-platform mobile push via APNs, FCM, and other push services through platform applications.
SMS Messaging
Direct SMS text messaging to phone numbers worldwide with support for transactional and promotional messages.
Dead-Letter Queues
Capture undeliverable messages for analysis and reprocessing to ensure no messages are lost.
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.
Amazon SNS Notifications
Amazon Simple Notification Service (SNS) delivers notifications to subscribed endpoints when messages are published to topics. This AsyncAPI specification describes the notifica...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Sns Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 28
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CheckIfPhoneNumberIsOptedOutResponse
JSON SCHEMAConfirmSubscriptionResponse
JSON SCHEMACreatePlatformApplicationResponse
JSON SCHEMACreateTopicResponse
JSON SCHEMADeleteTopicResponse
JSON SCHEMAErrorResponse
JSON SCHEMAGetSMSAttributesResponse
JSON SCHEMAGetSubscriptionAttributesResponse
JSON SCHEMAGetTopicAttributesResponse
JSON SCHEMAListSubscriptionsByTopicResponse
JSON SCHEMAListSubscriptionsResponse
JSON SCHEMAListTagsForResourceResponse
JSON SCHEMAListTopicsResponse
JSON SCHEMAMessageAttributeValue
JSON SCHEMAAmazon SNS Notification Message
JSON SCHEMAPublishBatchRequestEntry
JSON SCHEMAPublishBatchResponse
JSON SCHEMAPublishResponse
JSON SCHEMAResponseMetadata
JSON SCHEMASetSubscriptionAttributesResponse
JSON SCHEMASetTopicAttributesResponse
JSON SCHEMASubscribeResponse
JSON SCHEMASubscriptionMember
JSON SCHEMATagResourceResponse
JSON SCHEMATag
JSON SCHEMATopicMember
JSON SCHEMAUnsubscribeResponse
JSON SCHEMAUntagResourceResponse
JSON SCHEMAScroll within the panel for all 28 ·
JSON Structure 27
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Sns Confirm Subscription Response Structure
JSON STRUCTUREAmazon Sns Create Topic Response Structure
JSON STRUCTUREAmazon Sns Delete Topic Response Structure
JSON STRUCTUREAmazon Sns Error Response Structure
JSON STRUCTUREAmazon Sns Get Sms Attributes Response Structure
JSON STRUCTUREAmazon Sns Get Topic Attributes Response Structure
JSON STRUCTUREAmazon Sns List Subscriptions Response Structure
JSON STRUCTUREAmazon Sns List Tags For Resource Response Structure
JSON STRUCTUREAmazon Sns List Topics Response Structure
JSON STRUCTUREAmazon Sns Message Attribute Value Structure
JSON STRUCTUREAmazon Sns Publish Batch Request Entry Structure
JSON STRUCTUREAmazon Sns Publish Batch Response Structure
JSON STRUCTUREAmazon Sns Publish Response Structure
JSON STRUCTUREAmazon Sns Response Metadata Structure
JSON STRUCTUREAmazon Sns Set Topic Attributes Response Structure
JSON STRUCTUREAmazon Sns Subscribe Response Structure
JSON STRUCTUREAmazon Sns Subscription Member Structure
JSON STRUCTUREAmazon Sns Tag Resource Response Structure
JSON STRUCTUREAmazon Sns Tag Structure
JSON STRUCTUREAmazon Sns Topic Member Structure
JSON STRUCTUREAmazon Sns Unsubscribe Response Structure
JSON STRUCTUREAmazon Sns Untag Resource Response Structure
JSON STRUCTUREScroll within the panel for all 27 ·
Examples 27
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amazon Sns Tag Example
EXAMPLEScroll within the panel for all 27 ·
Security 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.
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.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Application Event Fan-Out
Broadcast application events to multiple microservices simultaneously using pub/sub topic subscriptions.
Mobile Push Campaigns
Send targeted push notifications to mobile applications across iOS and Android platforms.
Alert and Monitoring Systems
Deliver operational alerts via SMS, email, and HTTP endpoints for infrastructure monitoring.
Order Confirmation Notifications
Send transactional notifications for order confirmations, shipping updates, and account activity.
Cross-Account Event Distribution
Share events across AWS accounts using SNS topic policies for multi-account architectures.
Resources
Every other property we hold for Amazon SNS — 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 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
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/amazon-sns · machine-readable index on apis.io