canonical: https://jentic.com/apis/slicktext.com/slicktext

# SlickText API

SMS marketing and text messaging API for managing brands, contacts, campaigns, lists, and messaging workflows. The API exposes 21 endpoints secured with bearer authentication.

## For AI agents

Programmatically retrieve brand information, retrieve credit usage from brand. Covers 21 operations with bearer authentication.

## Scope

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

## Capabilities

- Retrieve brand information
- Create a contact
- Edit a specific contact
- Delete a specific contact
- Monitor SlickText API operational status and events

## Use cases

### Marketing Operations

Use the SlickText API to perform marketing operations programmatically. The API provides 21 endpoints covering core functionality including retrieve brand information, retrieve credit usage from brand, create a contact.

Example prompt: Call GET /brands to retrieve brand information

### Automated Brands Management

Automate brands operations by combining multiple SlickText API endpoints. Agents can retrieve credit usage from brand and then create a contact in a single workflow.

Example prompt: Call GET `/brands/{brand_id}/usage` to retrieve credit usage from brand, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SlickText 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 bearer tokens manually.

Example prompt: Search Jentic for 'retrieve brand information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/brands` | Retrieve brand information |
| GET | `/brands/{brand_id}/usage` | Retrieve credit usage from brand |
| POST | `/brands/{brand_id}/contacts` | Create a contact |
| GET | `/brands/{brand_id}/contacts` | Retrieve all contacts |
| GET | `/brands/{brand_id}/contacts/{id}` | Retrieve a specific contact |
| PUT | `/brands/{brand_id}/contacts/{id}` | Edit a specific contact |
| DELETE | `/brands/{brand_id}/contacts/{id}` | Delete a specific contact |
| POST | `/brands/{brand_id}/campaigns` | Create a campaign |

## Key resources

- **Brands** — Operations for brands

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 77 / 100
- **View full report:** https://jentic.com/apis/slicktext.com/slicktext/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 SlickText API by hand means sending a bearer token in the Authorization header to dev.slicktext.com/v1 and managing the brands, contacts, and campaigns calls yourself. Through Jentic you install once, import SlickText from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** SlickText puts the brand id and contact id in the URL path (`/brands/{brand_id}/contacts/{id}`), so a rule can pin your agent to one brand. You choose the operations it may call, so destructive ones like contact deletion are not included unless you add them.
- **Credential handling:** Your SlickText bearer token 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 a brand' or 'create a campaign', and Jentic returns the matching SlickText 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 SlickText API use?

The SlickText API uses a Bearer token 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 retrieve brand information with the SlickText API?

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

### What are the rate limits for the SlickText 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 retrieve brand information through Jentic?

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

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

The SlickText API exposes 21 endpoints covering brands operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which SlickText operations and credentials the agent may use. SlickText carries the brand id and contact id in the URL path, such as `/brands/{brand_id}/contacts/{id}`, so you can pin the agent to a single brand and choose exactly which endpoints it may call. Destructive operations like DELETE on a contact stay out of reach unless you explicitly grant them.