Inboxroute MailSquad API

Name: MailSquad API
Brand: MailSquad
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey8 EndpointsREST

For Agents

Manage MailSquad contacts, lists, and subscriptions. Useful for syncing contact data and powering subscribe and unsubscribe flows.

Install Jentic One Beta

Connect the MailSquad API to your agent

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

List contacts in the account

Manage contact lists used for segmenting recipients

Subscribe a contact to a specific list

Update contact details by id

GET STARTED

Start building with MailSquad API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MailSquad API for, with concrete tasks.

★ Website Signup to List

Power a website newsletter signup by calling POST /subscription/{listid} with the form input. The API adds the contact to MailSquad and to the chosen list in one call, which is the right pattern for landing pages and lead magnets.

Subscribe email priya@example.com to list id 1234 from a website signup form.

List Lifecycle Management

Marketing operators can create, rename, and delete contact lists through the lists endpoints. The contact list resources support clean segmentation for campaigns without leaving the API surface for the dashboard.

Create a new list called 'Q3-Webinar-Attendees' and return the new list id.

Contact Sync from CRM

Sync contact records from a CRM to MailSquad by listing existing contacts, calling PUT /contacts/{contactid} to update changes, and DELETE for hard-deletes. The flow keeps the marketing audience aligned with the source-of-truth in the CRM.

Update contact id c-9876 to set their first name to 'Alex' and remove contact id c-1234 from MailSquad entirely.

Jentic Subscriber Agent

Through Jentic, an agent can manage MailSquad subscriptions from a chat surface. The agent searches by intent, loads the schema, and executes the right MailSquad endpoint without needing to remember the path or auth header format.

Search Jentic for 'subscribe a contact to a list', load the schema, and subscribe alex@example.com to list 5678.

Key Endpoints

8 endpoints — mailsquad is an email marketing platform for designing, sending, and tracking campaigns.

METHOD

PATH

DESCRIPTION

GET

/contacts

List contacts

GET

/contacts/lists

List contact lists

POST

/contacts/lists

Create a contact list

PUT

/contacts/{contactid}

Update a contact

DELETE

/contacts/{contactid}

Delete a contact

POST

/subscription/{listid}

Subscribe a contact to a list

GET

/contacts

List contacts

GET

/contacts/lists

List contact lists

POST

/contacts/lists

Create a contact list

PUT

/contacts/{contactid}

Update a contact

DELETE

/contacts/{contactid}

Delete a contact

POST

Why Jentic?

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

Credential isolation

MailSquad API keys are stored encrypted in the Jentic vault. Agents call the API with a scoped Jentic token; the raw Authorization header value never enters agent prompts or logs.

Intent-based discovery

Agents search Jentic by intent such as 'subscribe a contact to a list' and Jentic returns the matching MailSquad operation with its input schema, so the agent does not need to memorise the endpoint paths.

Time to first call

Direct MailSquad integration: half a day for auth, list CRUD, and subscribe flow. Through Jentic: under 30 minutes. Search, load, execute.

FAQs

Specific to using MailSquad API through Jentic.

What authentication does the MailSquad API use?

MailSquad uses an Authorization header containing the API key issued from the MailSquad dashboard. Through Jentic, the key is stored in the encrypted vault and injected at runtime, so the raw key never enters the agent prompt or logs.

Can I subscribe a contact to a specific list?

Yes. POST /subscription/{listid} with the contact email and any custom fields adds the contact to MailSquad and to the specified list in one call, which is the recommended pattern for newsletter signups.

What are the rate limits for the MailSquad API?

The published spec does not declare hard rate limits. MailSquad enforces per-account fair-use limits, so bulk imports and sweeps should be paced and the response checked for 429 before retrying.

How do I add a contact to a list through Jentic?

Search Jentic for 'subscribe a contact to a list' to find the operation backed by POST /subscription/{listid}. Load the schema, pass the list id and contact email, and execute. Jentic injects the Authorization header at runtime.

Can I delete a contact via the MailSquad API?

Yes. DELETE /contacts/{contactid} removes the contact from MailSquad. Use this for hard-delete flows when a CRM record is removed or a user invokes a right-to-erasure request.

Inboxroute MailSquad API

Connect the MailSquad API to your agent

Capabilities

Start building with MailSquad API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs