canonical: https://jentic.com/apis/spoki.it/spoki-it

# Spoki It Spoki API

Spoki WhatsApp marketing automation API. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create contact, list contacts. Covers 6 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create contact
- List contacts
- Get contact
- Update contact
- Send WhatsApp message

## Use cases

### Marketing Operations

Use the Spoki API to perform marketing operations programmatically. The API provides 6 endpoints covering core functionality including create contact, list contacts, get contact.

Example prompt: Call POST /contacts to create contact

### Automated Contacts Management

Automate contacts operations by combining multiple Spoki API endpoints. Agents can list contacts and then get contact in a single workflow.

Example prompt: Call GET /contacts to list contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Spoki API 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contacts` | Create contact |
| GET | `/contacts` | List contacts |
| GET | `/contacts/{id}` | Get contact |
| PUT | `/contacts/{id}` | Update contact |
| POST | `/messages/send` | Send WhatsApp message |
| GET | `/templates` | List message templates |

## Key resources

- **Contacts** — Operations related to Contacts
- **Messages** — Operations related to Messages
- **Templates** — Operations related to Templates

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/spoki.it/spoki-it/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Spoki API by hand means provisioning its API key, attaching it to every request, and pointing calls at the api.spoki.it/v1 host yourself. Through Jentic you install once, import the Spoki API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Spoki puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to reading and updating one contact. You choose the operations it may call, so sending messages is not included unless you add it.
- **Credential handling:** Your Spoki API key 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 'create a contact' or 'send a template message', and Jentic returns the matching Spoki API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Spoki API use?

The Spoki API uses an API key passed in the `Authorization` header. 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 create contact with the Spoki API?

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

### What are the rate limits for the Spoki API?

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 create contact through Jentic?

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

### How many endpoints does the Spoki API have?

The Spoki API exposes 6 endpoints covering contacts, messages, templates operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Spoki operations and credentials the agent may use. Spoki puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to reading and updating a single contact while blocking POST /contacts. You choose the operations it may call, so sending a WhatsApp message via POST `/messages/send` stays off unless you explicitly grant it.