Aurora Platform API

Name: Aurora Platform API API
Brand: Aurora Platform API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat MessagingapiKey31 EndpointsREST

For Agents

Send and receive messages across WhatsApp, Messenger, and other channels, manage contacts, companies, opportunities, and webhooks via an X-API-Key authenticated REST API.

Quickstart

Get started with Aurora Platform API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a WhatsApp message via Aurora Inbox"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Aurora Platform API API.

Send a message into an existing chat via POST /Chats/{id}/Messages

Open a new chat with a contact through POST /Chats and route it to a team

Search the chat history with POST /Chats/Search and filter by channel or contact

Upsert a contact via POST /Contacts/Upsert to keep CRM records in sync

GET STARTED

Start building with Aurora Platform API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Aurora Platform API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Aurora Platform API, keeping it validated and agent-ready. Aurora Inbox is a multi-channel messaging and CRM platform that unifies WhatsApp Business, WhatsApp Cloud API, Messenger, and other conversational channels into a single inbox. The Platform API exposes 31 endpoints across channels, chats, contacts, companies, opportunities, teams, users, chatbots, and webhooks, so an external CRM, ticketing tool, or AI agent can read inbound messages and write replies, manage contact records, and track sales opportunities tied to conversations.

Use Cases

Patterns agents use Aurora Platform API API for, with concrete tasks.

★ WhatsApp customer support automation

Support teams receive thousands of inbound WhatsApp messages and need an AI tier to triage and reply to common questions. Webhooks from Aurora Inbox notify the agent of a new message; the agent calls POST /Chats/{id}/Messages to reply, GET /Contacts/{id} to fetch context, and POST /Contacts/Upsert to enrich the record. Complex conversations stay in Aurora and humans take them over from the same inbox.

On a new-message webhook, GET /Contacts/{id} for the sender, POST /Chats/{id}/Messages with a tailored reply, and POST /Contacts/Upsert to add the resolved tag.

Sales pipeline from conversations

Sales teams qualifying inbound enquiries on WhatsApp or Messenger want each qualified chat to become a tracked opportunity. /Chats/Search surfaces conversations matching a qualification keyword, /Contacts/{id} provides the lead record, and POST /Opportunities creates a pipeline entry tied to the contact. The pipeline stays current without a rep retyping notes into a separate CRM.

Search /Chats/Search for chats containing 'pricing' in the last 24 hours, and for each unique contact_id POST /Opportunities with a default stage and value of 0.

Contact and company sync to a primary CRM

Companies running HubSpot or Salesforce as the primary CRM still want messaging contacts mirrored. POST /Contacts/Upsert and GET /Companies keep Aurora's records aligned with the CRM, and webhooks push new contact and chat events outward. The result is one place to message and one place of record, kept consistent by the API.

List GET /Contacts updated in the last hour and call POST /Contacts/Upsert in the primary CRM with the same email and phone.

AI agent integration via Jentic

A chat-ops agent built on Jentic can reply across WhatsApp and Messenger without storing the X-API-Key in its prompt. The agent searches an intent like 'send a WhatsApp message via Aurora Inbox', Jentic returns the matching POST /Chats/{id}/Messages operation with its input schema, and execution uses the API key resolved from the Jentic vault.

Use Jentic search 'send a message in an Aurora Inbox chat', load the schema for POST /Chats/{id}/Messages, and execute it with the chat_id and a templated reply body.

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for aurora platform api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Chats

Create a chat

POST

/Chats/{id}/Messages

Send a message in a chat

POST

/Chats/Search

Search chats with filters

GET

/Contacts

List contacts

POST

/Contacts/Upsert

Upsert a contact by external ID

GET

/Channels/WhatsAppBusiness

List WhatsApp Business channels

GET

/Channels/WhatsAppCloudAPI

List WhatsApp Cloud API channels

GET

/Channels/Messenger

List Messenger channels

POST

/Chats

Create a chat

POST

/Chats/{id}/Messages

Send a message in a chat

POST

/Chats/Search

Search chats with filters

GET

/Contacts

List contacts

POST

/Contacts/Upsert

Upsert a contact by external ID

GET

Why though Jentic?

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

Credential isolation

Aurora X-API-Key values are stored encrypted in the Jentic vault. Agents receive scoped execution access; the raw key is never exposed to the agent's prompt or memory.

Intent-based discovery

Agents search by intent (e.g., 'send a WhatsApp message') and Jentic returns the matching Aurora operation across the 31-endpoint surface with its input schema, so the agent picks /Chats/{id}/Messages or /Contacts/Upsert without browsing developer docs.

Time to first call

Direct Aurora integration: 2-3 days for X-API-Key handling, channel resolution, and webhook setup. Through Jentic: under 1 hour from search to first executed call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Conversations API

Twilio Conversations is the larger multi-channel messaging API with WhatsApp and SMS coverage.

Choose Twilio for SMS-first or developer-led integrations at scale; use Aurora when a unified inbox UI plus pipeline is part of the product.

Alternative

MessageBird SMS API

MessageBird offers WhatsApp and SMS APIs with a focus on omnichannel messaging.

Choose MessageBird for a more API-first, developer-tier path; use Aurora when the team needs the inbox and CRM features together.

Complementary

HubSpot CRM API

HubSpot CRM holds the canonical contact and deal records that Aurora messaging contacts sync into.

Choose HubSpot for full CRM and marketing automation; use Aurora when conversations are the inbound channel feeding HubSpot records.

FAQs

Specific to using Aurora Platform API API through Jentic.

Why is there no official OpenAPI spec for Aurora Platform API?

Aurora Inbox publishes developer documentation at developers.aurorainbox.com but does not distribute an OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Aurora Platform API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Aurora Platform API use?

The Aurora Platform API uses an API key passed in the X-API-Key header on every request. Keys are issued per workspace from the Aurora developer portal. Through Jentic the X-API-Key is held in the vault and injected at execution time.

Can I send WhatsApp messages with the Aurora Platform API?

Yes. Aurora connects to both WhatsApp Business and WhatsApp Cloud API channels. List the available channels via GET /Channels/WhatsAppBusiness or GET /Channels/WhatsAppCloudAPI, open a chat with POST /Chats, and send a message with POST /Chats/{id}/Messages.

What are the rate limits for the Aurora Platform API?

Aurora Inbox enforces a per-workspace rate limit that is not declared in the spec; the platform returns 429 with standard rate-limit headers when exceeded. WhatsApp tier limits also flow through, so high-volume sends should respect Meta's per-number quality-rating throttling.

How do I track new messaging-driven opportunities through Jentic?

Run jentic search 'create an Aurora Inbox opportunity', load the schema for POST /Opportunities, and execute it with the contact_id pulled from a chat. Jentic resolves the X-API-Key from the vault at execution time. With pip install jentic the call is one async invocation.

Is the Aurora Platform API free?

API access is included in Aurora Inbox's paid workspace plans. WhatsApp messaging itself is metered by Meta's conversation-based pricing, separate from the API call cost.