Connect Reaktive to the systems you already use.
A key-based API for service users, documented in OpenAPI 3.1: your ERP starts automations and reads the outcome, with the cost in euros for every run.
How an integration flows
Your system starts, a person approves, the result comes back.
Your system
- ERP: new order
- CRM: new contact
- Intranet: a button
Reaktive
- Automation: the steps
- Agent: checks and writes
- Approval: a person decides
Result
- Run status and cost in euros
- Word, Excel, PDF files
- Email sent, sheet on Drive
Back in your system
- Order updated with the document
- Contact with the dossier
- Cost reconciled in management accounting
The same actions as the workspace, from your software.
A closed list of routes, documented one by one. What is not on the list cannot be done with a key.
Start an automation
With input data from your system: the active version starts, queued as from the “Run” button.
- POST/api/workflows/{id}/runs
- GET/api/workflows/{id}/tasks/{taskId}
Follow runs and download files
Status, duration, cost in euros and files produced by every run; cancel queued ones.
- GET/api/runs · /api/runs/{id}
- GET/api/runs/{id}/files/{fileId}
Talk to an agent
Create the chat, send the message, read the answer as it arrives, attach files. A turn costs the same as in the interface.
- POST/api/chats · /api/chats/{id}/messages
- POST/stream · /api/chats/{id}/files
Approvals
Read pending sends and decide, if you are entitled to: from your own internal panel too.
- GET/api/approvals · /api/approvals/{id}
- POST/api/approvals/{id}
Agents and usage
List and card of agents; spending per person, agent and automation, to reconcile costs.
- GET/api/agents · /api/agents/{id}
- GET/api/usage
Team and keys
With the admin scope: team invitations and user keys, which stay pending until the Owner approves them.
- GET/api/team · POST /api/team
- GET/api/api-keys · POST /api/api-keys
Three steps, and your system works with Reaktive.
A service user
In Team you create “ERP” as a service user, with its own spending cap: its actions are attributed and limited like a person’s.
An approved key
The service user creates the rk_… key; the Owner approves it. The key is shown only once.
Calls with the key
Authorization: Bearer rk_… and an Idempotency-Key so the same run never starts twice if the network drops.
Browser tests (“Try the call”) are on the Developers page of the workspace, after sign-in: they are real calls and use credit.
# 1. The ERP starts the automation for the new order curl -X POST \ https://reaktive.cloud/api/workflows/<id>/runs \ -H "Authorization: Bearer rk_…" \ -H "Idempotency-Key: order-10492" \ -H "Content-Type: application/json" \ -d '{"source":"active","input":{"order":"10492"}}' # 202 Accepted {"taskId":"5b7d9f1a-…","status":"queued"} # 2. Reads the state until terminal is true curl -H "Authorization: Bearer rk_…" \ https://reaktive.cloud/api/workflows/<id>/tasks/5b7d9f1a-… {"task":{"status":"done"},"run":{"id":"4e6a8c0b-…","outcome":"completed","costEur":"0.004120000000"},"terminal":true} # 3. Downloads the files produced by the run curl -H "Authorization: Bearer rk_…" \ https://reaktive.cloud/api/runs/4e6a8c0b-…
Every route documented, with examples, in Italian and English.
Generated from the same OpenAPI 3.1 document the platform uses in its tests: if the API changes, the page changes. Read-only here; tests after sign-in.
Additive changes appear in the “What’s new” section; a breaking change only comes with a new prefix, announced 90 days in advance.
Clear rules, the same for everyone.
Two scopes
User and admin. The person’s role remains the limit: a key never does more than whoever created it, and never has platform powers.
Isolation
An object of another organization answers 404, as in the interface. Keys are stored only as a fingerprint.
Limits per key
600 requests and 60 starts per minute; beyond that, 429 with Retry-After.
Idempotency
Same Idempotency-Key and same body within 24 hours: same answer, no double run.
Coded errors
{error, message, details}, with the message in the Accept-Language language.
Audit
Every write with origin “api”; “last used” on every key.
Costs
No fee for the API: every run or turn costs the same as in the interface, within the service user’s cap.
Version
Version 1 is implicit in /api/…; breaking changes only with a new prefix, announced 90 days in advance.
Three ways to connect company systems.
Real mechanisms, example data.
ERP
For every new order the ERP starts “Supplier check and confirmation draft”: the agent checks the supplier on the web, drafts the email and asks for approval; the ERP reads the outcome and the document.
CRM
For every new contact the CRM starts research on the company (website, news, tenders won) and receives the dossier, which the automation also saves in the salesperson’s Drive folder.
Intranet
An “Extra press review” button on the intranet starts the automation with the chosen topic and shows the files produced when the run ends; approvals stay with whoever is entitled to them.
What joins the list as soon as it is ready and tested.
Signed outgoing webhooks
Reaktive calls your system when a run ends.
Start with stream
The run’s events as they happen.
Agents from the API
Creation and editing with the admin key.
Chat without stream
A single call, complete answer.
Want to see it on your case?
A 30-minute technical demo: we start an automation from your system and read the outcome together.