SlickText API

Name: SlickText API
Brand: SlickText API
Availability: InStock

✓ Official Vendor SpecMarketingEmail Marketingbearer21 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the SlickText API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SlickText API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SlickText API.

Retrieve brand information

Create a contact

Edit a specific contact

Delete a specific contact

GET STARTED

Start building with SlickText API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SlickText API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

21 endpoints — sms marketing and text messaging api for managing brands, contacts, campaigns, lists, and messaging workflows.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

SlickText API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'retrieve brand information') and Jentic returns the matching SlickText API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SlickText API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using SlickText API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

SlickText API

Connect the SlickText API to your agent

Capabilities

Start building with SlickText API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs