engageSPARK
engageSPARK is a mobile messaging and engagement platform for reaching hard-to-reach populations in low- and middle-income countries at scale. It lets NGOs, researchers, microfinance institutions, and businesses run SMS, automated voice (IVR), WhatsApp, and pre-paid airtime top-up campaigns across 180+ countries without writing code, or programmatically through its HTTP API. The engageSPARK API (api.engagespark.com, v1) exposes token-authenticated endpoints for sending SMS, WhatsApp, and airtime top-ups, managing contacts and organizations, subscribing and unsubscribing contacts to voice and SMS campaigns, reading message and top-up history, checking organization balance, and managing files. Incoming-SMS and campaign-action webhooks let the platform push survey responses and inbound messages into external systems such as Salesforce or Qualtrics.
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 engageSPARK the way a machine reads it — 11 machine-readable artifacts across 7 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 — engageSPARK scores 46.9/100 (developing), with a separate agent-readiness read of 42/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 engageSPARK
Each block below is one kind of artifact we hold for engageSPARK. 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 7
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.
engageSPARK Balance API
The Balance API from engageSPARK — 1 operation(s) for balance.
engageSPARK Campaigns API
The Campaigns API from engageSPARK — 2 operation(s) for campaigns.
engageSPARK Contacts API
The Contacts API from engageSPARK — 2 operation(s) for contacts.
engageSPARK Files API
The Files API from engageSPARK — 2 operation(s) for files.
engageSPARK SMS API
The SMS API from engageSPARK — 4 operation(s) for sms.
engageSPARK Top-Up API
The Top-Up API from engageSPARK — 3 operation(s) for top-up.
engageSPARK WhatsApp API
The WhatsApp API from engageSPARK — 3 operation(s) for whatsapp.
Scroll within the panel for all 7 ·
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.
Engagespark Webhooks
ASYNCAPISecurity 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 engageSPARK — 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 3
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/engagespark · machine-readable index on apis.io