Sendblue API

Name: Sendblue API API
Brand: Sendblue API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey9 EndpointsREST

For Agents

Programmatically send message, send group message. Covers 9 operations with apiKey authentication.

Use for: I need to send message, I want to send group message, Search for messages, Find all evaluate messaging service

Connect the Sendblue API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Sendblue API API.

Send message

Get messages

Evaluate messaging service

Create contact

List contacts

GET STARTED

Start building with Sendblue API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Sendblue API API for, with concrete tasks.

★ Communications Operations

Use the Sendblue API to perform communications operations programmatically. The API provides 9 endpoints covering core functionality including send message, send group message, get messages.

Call POST /send-message to send message

Automated Contacts Management

Automate contacts operations by combining multiple Sendblue API endpoints. Agents can send group message and then get messages in a single workflow.

Call POST /send-group-message to send group message, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sendblue 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 'send message', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — sendblue imessage, sms, and rcs messaging api.

METHOD

PATH

DESCRIPTION

POST

/send-message

Send message

POST

/send-group-message

Send group message

GET

/accounts/messages

Get messages

GET

/evaluate-service

Evaluate messaging service

POST

/contacts

Create contact

GET

/contacts

List contacts

GET

/contacts/{id}

Get contact

PUT

/contacts/{id}

Update contact

POST

/send-message

Send message

POST

/send-group-message

Send group message

GET

/accounts/messages

Get messages

GET

/evaluate-service

Evaluate messaging service

POST

/contacts

Create contact

GET

/contacts

Why though Jentic?

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

Credential isolation

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

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Sendblue API API through Jentic.

What authentication does the Sendblue API use?

The Sendblue API uses an API key passed in the `sb-api-key-id` 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 send message with the Sendblue API?

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

What are the rate limits for the Sendblue 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 send message through Jentic?

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

How many endpoints does the Sendblue API have?

The Sendblue API exposes 9 endpoints covering contacts, messages, service operations.