Connect customer profiles and events through the API, then let your team manage audiences, content and journeys from the dashboard. Send transactional email and push from your code and receive signed webhook updates. API access is included on every plan.
# Create or update a contact by your own ID
curl https://api.kirora.io/v1/contacts/identify \
-H "Authorization: Bearer kirora_live_…" \
-d '{
"externalId": "user_8812",
"email": "amaka@juniperkitchen.com",
"firstName": "Amaka",
"timezone": "Europe/London",
"attributes": { "plan": "pro" },
"emailConsent": true
}'# Record what they did. Journeys listening for it start.
curl https://api.kirora.io/v1/events/track \
-H "Authorization: Bearer kirora_live_…" \
-d '{
"externalId": "user_8812",
"eventName": "Order Completed",
"properties": {
"total": 18500,
"currency": "USD"
}
}'# A receipt that never sends twice, even on retry
curl https://api.kirora.io/v1/transactional/messages \
-H "Authorization: Bearer kirora_live_…" \
-H "Idempotency-Key: order-55120-receipt" \
-d '{
"to": { "externalId": "user_8812" },
"email": {
"templateId": "order-receipt",
"data": { "orderNumber": "55120" }
}
}'Call identify with your own user ID to create or update a contact, then track what they do. Any journey listening for that event enrols them. Event names are yours; properties can filter who enters and fill in message content.
Send email or push with a stored template alias and your data, or inline content. Reuse the same idempotency key and payload on retries to avoid creating a second message. Transactional mail is kept apart from marketing in reports and logs.
Subscribe an HTTPS endpoint to delivery, engagement, contact, form, campaign and journey events. Every delivery is signed and failures are retried. You can test, pause, rotate the secret and replay from the dashboard.
Give Claude or your own agent a restricted agent key and it can read data and draft campaigns, journeys and templates. Agent keys cannot send, schedule, activate, or change contacts and consent. A person confirms those.
Pick exactly what each key may do, set an expiry and an IP allow-list, and rotate with a 7-day overlap.
Retry-sensitive endpoints accept an Idempotency-Key, to prevent duplicate actions when you retry matching requests.
Everything lives under /v1, and a path or field is never removed or repurposed while it does.
Every API request and every webhook delivery is visible in the dashboard.
Accepts the tracking calls you already send from another platform, so you can switch without a rewrite.
Connect your payment provider and successful payments arrive as purchase events.
Join the waitlist for launch updates. Bring campaigns, journeys and transactional messages together when Kirora opens.
Kirora is for permission-based email and push. See our Acceptable Use Policy, Terms and Privacy Policy.