Skip to content
Communication/messaging

sakari.io

Sakari sandbox and mock API

# Introduction Welcome to the documentation for the Sakari Messaging REST API. Sakari provides an advanced platform to drive large scale customized SMS communication REST is a web-service protocol that lends itself to rapid development by using everyday HTTP and JSON technology. To find out more about our product offering, please visit [https://sakari.io](https://sakari.io). # Quickstart For your Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
26
Collections
-
Event types
-
Start this simulation
example request
curl https://your-sakari.slurry.io/v1/accounts/123/campaigns \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 26.

  • POST/oauth2/token
  • GET/v1/accounts/{accountId}/campaigns
  • POST/v1/accounts/{accountId}/campaigns
  • GET/v1/accounts/{accountId}/campaigns/{campaignId}
  • PUT/v1/accounts/{accountId}/campaigns/{campaignId}
  • DELETE/v1/accounts/{accountId}/campaigns/{campaignId}
  • GET/v1/accounts/{accountId}/contacts
  • POST/v1/accounts/{accountId}/contacts
  • GET/v1/accounts/{accountId}/contacts/{contactId}
  • PUT/v1/accounts/{accountId}/contacts/{contactId}
  • DELETE/v1/accounts/{accountId}/contacts/{contactId}
  • GET/v1/accounts/{accountId}/conversations