Sendiio API

Name: Sendiio API
Brand: Sendiio API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey22 EndpointsREST

For Agents

Programmatically check credentials, subscribe to list (json). Covers 22 operations with apiKey authentication.

I need to check credentials, I want to subscribe to list (json), Search for subscribe to list (redirect), Find all unsubscribe email

Install Jentic One Beta

Connect the Sendiio API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sendiio 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 Sendiio API.

Check credentials

Subscribe to list (JSON)

Unsubscribe email

Get email list

GET STARTED

Start building with Sendiio API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Sendiio API for, with concrete tasks.

★ Communications Operations

Use the Sendiio API to perform communications operations programmatically. The API provides 22 endpoints covering core functionality including check credentials, subscribe to list (json), subscribe to list (redirect).

Call POST /auth/check to check credentials

Automated Authentication Management

Automate authentication operations by combining multiple Sendiio API endpoints. Agents can subscribe to list (json) and then subscribe to list (redirect) in a single workflow.

Call POST /lists/subscribe/json to subscribe to list (json), then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sendiio 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.

Search Jentic for 'check credentials', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

22 endpoints — sendiio is an email and sms marketing platform.

METHOD

PATH

DESCRIPTION

POST

/auth/check

Check credentials

POST

/lists/subscribe/json

Subscribe to list (JSON)

POST

/lists/subscribe

Subscribe to list (redirect)

POST

/lists/{encryptedId}/unsubscribe

Unsubscribe email

POST

/lists/phone/{encryptedId}/unsubscribe

Unsubscribe phone

GET

/lists/email/{encryptedId}

Get email list

GET

/lists/phone/{encryptedId}

Get phone list

GET

/lists/email

Get all email lists

POST

/auth/check

Check credentials

POST

/lists/subscribe/json

Subscribe to list (JSON)

POST

/lists/subscribe

Subscribe to list (redirect)

POST

/lists/{encryptedId}/unsubscribe

Unsubscribe email

POST

/lists/phone/{encryptedId}/unsubscribe

Unsubscribe phone

Why Jentic?

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

Credential isolation

Sendiio API apiKey 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., 'check credentials') and Jentic returns the matching Sendiio API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Sendiio 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 Sendiio API through Jentic.

What authentication does the Sendiio API use?

The Sendiio API uses an API key passed in the `token` 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 check credentials with the Sendiio API?

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

What are the rate limits for the Sendiio 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 check credentials through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'check credentials'. Jentic returns the matching Sendiio API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Sendiio API have?

The Sendiio API exposes 22 endpoints covering authentication, fields, forms operations.

Sendiio API

Connect the Sendiio API to your agent

Capabilities

Start building with Sendiio API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs