canonical: https://jentic.com/apis/sakari.io/sakari

# Sakari

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 conv. The API exposes 26 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get token for accessing apis, create contact. Covers 26 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Get token for accessing APIs
- Create contact
- Fetch contacts
- Updates a contact
- Deletes a contact
- Send Messages

## Use cases

### E-Commerce Operations

Use the Sakari to perform e commerce operations programmatically. The API provides 26 endpoints covering core functionality including get token for accessing apis, create contact, fetch contacts.

Example prompt: Call POST `/oauth2/token` to get token for accessing apis

### Automated authentication Management

Automate authentication operations by combining multiple Sakari endpoints. Agents can create contact and then fetch contacts in a single workflow.

Example prompt: Call POST `/v1/accounts/{accountId}/contacts` to create contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sakari endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'get token for accessing apis', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth2/token` | Get token for accessing APIs |
| POST | `/v1/accounts/{accountId}/contacts` | Create contact |
| GET | `/v1/accounts/{accountId}/contacts` | Fetch contacts |
| GET | `/v1/accounts/{accountId}/contacts/{contactId}` | Fetch contact by ID |
| PUT | `/v1/accounts/{accountId}/contacts/{contactId}` | Updates a contact |
| DELETE | `/v1/accounts/{accountId}/contacts/{contactId}` | Deletes a contact |
| POST | `/v1/accounts/{accountId}/messages` | Send Messages |
| GET | `/v1/accounts/{accountId}/messages` | Fetch messages |

## Key resources

- **authentication** — Sakari uses OAuth2 for authentication. After you have created an account at [https://hub.sakari.io](
- **contacts** — Create, modify or delete contacts
- **messages** — Send or track messages to one contact, a group of contacts or your entire address book
- **templates** — Define reusable message or web templates
- **campaigns** — Define reusable message campaigns with a predefined contact list/filter, template and schedule

## Why Jentic

- **Setup:** Wiring Sakari by hand means running its OAuth2 flow at `/oauth2/token`, refreshing tokens against api.sakari.io, and handling your own retries. Through Jentic you install once, import Sakari from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Sakari puts the account and contact ids in the URL path (`/v1/accounts/{accountId}/contacts/{contactId}`), so a rule can pin your agent to one account: it can read and update contacts and send messages for that account and nothing else. You choose the operations it may call, so deleting a contact is not included unless you add it.
- **Credential handling:** Your Sakari credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a contact to an account' or 'send a message', and Jentic returns the matching Sakari operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Sakari use?

The Sakari uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get token for accessing apis with the Sakari?

Yes. Use the POST `/oauth2/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sakari?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get token for accessing apis through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get token for accessing apis'. Jentic returns the matching Sakari operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sakari have?

The Sakari exposes 26 endpoints covering authentication, contacts, messages operations.

### Can I limit what my agent is allowed to do with the Sakari API?

Yes. Because Sakari carries the account and contact IDs in the URL path, a rule in your own self-hosted Jentic One instance can pin your agent to a single account, letting it read and update contacts and send messages for that account and nothing else. You decide which operations the agent may call, so destructive actions like deleting a contact stay off the list unless you explicitly grant them. Your own rules, not Jentic, decide which Sakari operations and credentials the agent can use.