Connect Aurora to your systems with one request.
A public REST API with scoped keys, signed outbound webhooks and an address to send your leads to. Paths, fields and events are all in the documentation.
# Inbound webhook: the new lead lands in Aurora
curl -X POST https://api.aurorasuite.ai/public/leads/{key} \
-H "Content-Type: application/json" \
-d '{
"name": "Luca Ricci",
"phone": "+393471234567",
"email": "[email protected]",
"consent": true
}'
# Aurora creates the contact; with "Lead in 60 seconds"
# switched on, the agent calls within a minute.You'll find the source key in Aurora. The lead details are an example.
Your keys, with the right permissions.
Read and write your account's data from your own software. Each key does only what you allow, so an integration can't do more than it needs to.
- REST APIHTTPS requests and JSON responses, documented one by one.public
- KeysOne key per integration, with only the scopes it needs.scopes
- WorkspacesEach key belongs to one workspace: one client's integration can't see another client's data.per workspace
- Server-sideKeep keys on your server, never in code that runs in the browser.tip
# Aurora → your server, as soon as something happens
POST https://yourserver.com/webhook/aurora
# with Aurora's signature in the headers
{
"event": "appointment.created",
"created_at": "2026-11-06T21:41:08+01:00",
"data": {
"contact": {
"name": "Laura Bianchi",
"phone": "+39347•••4812"
},
"appointment": {
"start": "2026-11-11T10:30:00+01:00",
"channel": "phone"
}
}
}Event names and fields are an example: the real ones are in the catalogue in the documentation.
Aurora tells your server. And you can trust it.
When something happens in your account, such as an appointment booked or a contact updated, Aurora sends it to your address. You choose the events.
- SignedEvery webhook carries a signature: you check that it really comes from Aurora and that nobody has altered it.security
- CatalogueSubscribe only to the events you need. The full list is in the documentation.events
Send us your leads. Aurora calls them back.
Your form, CRM or back-office system sends the new contact to POST /public/leads/{key}. Four fields are all it takes.
- nameThe contact's name, as they wrote it.text
- phoneThe number to call, ideally with the international code.text
- emailThe email address, if you have it.text
- consentWhether they agreed to be contacted. You record it in your own form.true / false
Website forms and Google Ads leads work too.
Received at 10:02:11New
Consultation booked for Thursday at 5:30 pmBooked
The agent uses your services mid-conversation.
Give the agent a tool that calls one of your services, for example to check an order. During the conversation it uses it and answers with real data.
- API toolsConnect one of your services to the agent: it calls it during the conversation and uses the answer.agents
- MCP serverTo use Aurora's data and functions from Claude, Cursor and the other AI assistants you already use.coming soon
Developer questions
Where is the documentation?
At docs.aurorasuite.ai you'll find paths, parameters, examples and the catalogue of webhook events.
Can I limit what a key can do?
Yes. Each key has its own scopes and belongs to one workspace: give every integration only what it needs.
How do I check that a webhook comes from Aurora?
Outbound webhooks are signed. You verify the signature on your server as described in the documentation.
Can I send leads from my CRM to Aurora?
Yes, with the inbound webhook: a POST request with name, phone, email and consent. The contact lands in Aurora and automations such as Lead in 60 seconds start on their own.
When is the MCP server coming?
It is on its way and not available yet. In the meantime you can use the REST API and webhooks.
Enter your website. In a few minutes you hear your assistant.
Aurora reads the site, tells you what it understood and prepares the agent. Then you try it live: it calls you, answers in your chat, fills in your form. You decide afterwards.
Rather talk it through with us?