MagicBell
MagicBell is a multichannel push notification infrastructure platform that enables developers to deliver in-app, email, mobile push, web push, SMS, Slack, and Microsoft Teams notifications through a single unified REST API. The platform provides a ready-made notification inbox component, built-in user preference management, smart delivery workflows with fallback rules, and full delivery observability with event logging and debugging. MagicBell handles all channel routing and token management so product teams can focus on building rather than maintaining notification infrastructure. It is a Y Combinator (W21) company offering SDKs for JavaScript, React, Go, Swift, Java, and Android along with a CLI for project management.
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 MagicBell the way a machine reads it — 51 machine-readable artifacts across 28 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 — MagicBell scores 56.8/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). 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 MagicBell
Each block below is one kind of artifact we hold for MagicBell. 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 28
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.
MagicBell REST API v1
The legacy MagicBell REST API (v1) for notification delivery, user management, and channel configuration. Supports API key and user external ID based authentication. Rate limits...
MagicBell apns API
The apns API from MagicBell — 6 operation(s) for apns.
MagicBell awssns API
The awssns API from MagicBell — 3 operation(s) for awssns.
MagicBell broadcasts API
The broadcasts API from MagicBell — 2 operation(s) for broadcasts.
MagicBell channel/email API
The channel/email API from MagicBell — 8 operation(s) for channel/email.
MagicBell channel/mobile_push API
The channel/mobile_push API from MagicBell — 6 operation(s) for channel/mobile_push.
MagicBell channel/slack API
The channel/slack API from MagicBell — 2 operation(s) for channel/slack.
MagicBell channel/sms API
The channel/sms API from MagicBell — 2 operation(s) for channel/sms.
MagicBell channel/web_push API
The channel/web_push API from MagicBell — 2 operation(s) for channel/web_push.
MagicBell channels API
The channels API from MagicBell — 25 operation(s) for channels.
MagicBell expo API
The expo API from MagicBell — 6 operation(s) for expo.
MagicBell fcm API
The fcm API from MagicBell — 6 operation(s) for fcm.
MagicBell github API
The github API from MagicBell — 3 operation(s) for github.
MagicBell inbox API
The inbox API from MagicBell — 4 operation(s) for inbox.
MagicBell integrations API
The integrations API from MagicBell — 42 operation(s) for integrations.
MagicBell mailgun API
The mailgun API from MagicBell — 2 operation(s) for mailgun.
MagicBell mobile_push API
The mobile_push API from MagicBell — 12 operation(s) for mobile_push.
MagicBell ping_email API
The ping_email API from MagicBell — 2 operation(s) for ping_email.
MagicBell project API
The project API from MagicBell — 52 operation(s) for project.
MagicBell sendgrid API
The sendgrid API from MagicBell — 2 operation(s) for sendgrid.
MagicBell ses API
The ses API from MagicBell — 2 operation(s) for ses.
MagicBell slack API
The slack API from MagicBell — 9 operation(s) for slack.
MagicBell stripe API
The stripe API from MagicBell — 3 operation(s) for stripe.
MagicBell teams API
The teams API from MagicBell — 4 operation(s) for teams.
MagicBell templates API
The templates API from MagicBell — 3 operation(s) for templates.
MagicBell twilio API
The twilio API from MagicBell — 2 operation(s) for twilio.
MagicBell user API
The user API from MagicBell — 20 operation(s) for user.
MagicBell web_push API
The web_push API from MagicBell — 8 operation(s) for web_push.
Scroll within the panel for all 28 ·
Pricing 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.
Magicbell 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.
Magicbell Finops
FINOPSSemantic 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.
Magicbell Context
JSON-LDSpectral Rules 1
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.
MagicBell API Rules
SPECTRALJSON Schema 11
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.
AccessToken
JSON SCHEMAAPNSToken
JSON SCHEMABroadcast
JSON SCHEMAEvent
JSON SCHEMAFCMToken
JSON SCHEMAIntegration
JSON SCHEMASlackToken
JSON SCHEMATeamsToken
JSON SCHEMAtopic
JSON SCHEMAuser
JSON SCHEMAWebPushToken
JSON SCHEMAScroll within the panel for all 11 ·
Examples 4
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.
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.
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 MagicBell — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
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/magicbell · machine-readable index on apis.io