Automate Sakari

What Sakari is

# 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

API host: api.sakari.io

What HumDay can do in Sakari

15 documented operations change something in Sakari.

• POSTShare file - use to host a file and generate a short link to be used directly in a message or as a link to media for a MMS/v1/tools/sharefile
• POSTCreate contact/v1/accounts/{accountId}/contacts
• POSTSend Messages/v1/accounts/{accountId}/messages
• POSTSubscribe to message events/v1/accounts/{accountId}/webhooks
• POSTCreate campaign/v1/accounts/{accountId}/campaigns
• DELETEUnsubscribe to message events/v1/accounts/{accountId}/webhooks/{url}
• POSTGet token for accessing APIs/oauth2/token
• DELETEDeletes a contact/v1/accounts/{accountId}/contacts/{contactId}
• PUTUpdates a contact/v1/accounts/{accountId}/contacts/{contactId}
• POSTCreate template/v1/accounts/{accountId}/templates
• DELETEDeletes a campaign/v1/accounts/{accountId}/campaigns/{campaignId}
• PUTUpdates a campaign/v1/accounts/{accountId}/campaigns/{campaignId}
• DELETEDeletes a template/v1/accounts/{accountId}/templates/{templateId}
• PUTUpdates a template/v1/accounts/{accountId}/templates/{templateId}
• PUTCloses a conversation/v1/accounts/{accountId}/conversations/{conversationId}/close

What HumDay can read from Sakari

These are the operations a schedule or a trigger can watch.

• GETFetch contact by ID/v1/accounts/{accountId}/contacts/{contactId}
• GETFetch message by id/v1/accounts/{accountId}/messages/{messageId}
• GETFetch contacts/v1/accounts/{accountId}/contacts
• GETFetch messages/v1/accounts/{accountId}/messages
• GETFetch campaign by ID/v1/accounts/{accountId}/campaigns/{campaignId}
• GETFetch active webhooks/v1/accounts/{accountId}/webhooks
• GETFetch campaigns/v1/accounts/{accountId}/campaigns
• GETFetch templates/v1/accounts/{accountId}/templates
• GETFetch conversations/v1/accounts/{accountId}/conversations
• GETFetch template by ID/v1/accounts/{accountId}/templates/{templateId}
• GETFetch conversation by ID/v1/accounts/{accountId}/conversations/{conversationId}

How automating Sakari works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Sakari account.
4. Grant access, then go live. You approve the specific Sakari operations it may use — and only those.

Automate Sakari with these

• Zendesk636 operations
• Discord242 operations
• Twilio199 operations
• Slack174 operations
• Twilio Preview147 operations
• Circuitsandbox 2123 operations
• Intercom108 operations
• SIGNL4101 operations
• Twilio Conversations101 operations
• Telegram Bot74 operations
• Twilio Taskrouter60 operations
• WhatsApp Business55 operations

Categories

• Messaging

Questions about Sakari automation

Can HumDay connect to Sakari?

Yes. HumDay reads Sakari's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 26 operations are documented.

Do I need to write code to automate Sakari?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Sakari account.

What can HumDay do in Sakari?

15 of the 26 documented operations change something in Sakari, and 11 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Sakari account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Sakari is held behind that approval.

Where this came from

The operations above are read from a published API description for Sakari at developer.sakari.io/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.