SendX REST API
✓ Official Vendor SpecMarketingEmail MarketingapiKey6 EndpointsREST
For Agents
Programmatically get all contacts, get all campaigns. Covers 6 operations with apiKey authentication.
Use for: I need to all contacts, I want to all campaigns, Search for all tags, Find all all contact lists
Not supported: Does not handle payments, communications, or crm — use for marketing only.
SendX REST API for managing contacts, campaigns, tags, lists, senders, and webhooks for email marketing and marketing automation. The API exposes 6 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the SendX REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SendX REST 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.
1
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 | sh2
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 instanceJentic 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 SendX REST API.
Get all contacts
Manage marketing data programmatically
Integrate SendX REST API into automated workflows
Query and filter SendX REST API records by parameters
Monitor SendX REST API operational status and events
Use Cases
Patterns agents use SendX REST API for, with concrete tasks.
★ Marketing Operations
Use the SendX REST API to perform marketing operations programmatically. The API provides 6 endpoints covering core functionality including get all contacts, get all campaigns, get all tags.
Call GET /contact to get all contacts
Automated Campaigns Management
Automate campaigns operations by combining multiple SendX REST API endpoints. Agents can get all campaigns and then get all tags in a single workflow.
Call GET /campaign to get all campaigns, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SendX REST 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 'get all contacts', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
6 endpoints — sendx rest api for managing contacts, campaigns, tags, lists, senders, and webhooks for email marketing and marketing automation.
METHOD
PATH
DESCRIPTION
GET
/contact
Get all contacts
GET
/campaign
Get all campaigns
GET
/tag
Get all tags
GET
/list
Get all contact lists
GET
/sender
Get all verified sender addresses
GET
/webhook
Get all webhooks
GET
/contact
Get all contacts
GET
/campaign
Get all campaigns
GET
/tag
Get all tags
GET
/list
Get all contact lists
GET
/sender
Get all verified sender addresses
GET
/webhook
Get all webhooks
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
SendX REST 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., 'get all contacts') and Jentic returns the matching SendX REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct SendX REST 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.
FAQs
Specific to using SendX REST API through Jentic.
What authentication does the SendX REST API use?
The SendX REST API uses an API key passed in the `X-Team-ApiKey` 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 get all contacts with the SendX REST API?
Yes. Use the GET /contact endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SendX REST 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 get all contacts through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get all contacts'. Jentic returns the matching SendX REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the SendX REST API have?
The SendX REST API exposes 6 endpoints covering campaigns, contacts, lists operations.
GET STARTED