RakeSign API and integration administration
The RakeSign API exposes signing documents, templates, contacts, forms, jobs, reports, and delegation under /v1/signing.
API documents appear in the integration’s RakeSign team.
Organization administrators can create scoped keys, rotate or revoke them, and inspect request metadata under Developers. Team webhooks include delivery history and event replay.
across_documents reads all files as one source
across_documents now joins the files of a run into one source and extracts one record from it. Before, it extracted each file on its own and kept one file’s value for each field. With citations off, that was always the first file.
The files are joined in the order you list them, so list them in reading order. For the parts of one recording, list them in recording order. A list field now collects items from every file. Citations still point to the original files, with pages and timecodes counted from the start of each file.
Confidence scores now come from the evidence judge
Grounding quotes the source and tells you where the quote sits. Grading how well that quote supports the value is a second pass, and you now ask for it separately.
A grounded run without judge: true returns citations with no confidence. Everything else about them is unchanged: fileId, text, and page and bbox, or timecodeStart and timecodeEnd. Send "judge": true alongside "citations": true to get the score back.
Realtime transcription
Stream live audio over a WebSocket and get text back while the speaker talks: partials about every 2 seconds, finals a few seconds after each pause, English and French in the same session. Your backend creates a session with POST /v1/realtime/transcriptions. The response carries a wss:// URL with a single-use ticket, so the browser never holds your API key.
Callback URLs must use https
A webhook on any /v1 run requires an https URL. A plain http URL is rejected at create with 400 invalid_request. This rule has applied since 2026-09-01. Saved endpoints already had it.
Run deliveries also stop following redirects. This covers capability runs, pipelines, and /process callbacks. A 3xx answer from your endpoint counts as a failed attempt, and its status appears in GET /v1/webhooks/{id}/deliveries. Agent run deliveries still follow up to five redirects, with the same POST at each hop.
Restrict an API key to the agent runs it started
By default, any API key in your organization can read and control every agent run in the organization, not only the runs it started. You can now turn on stricter scoping. Each key then sees only the runs it created. A run from another key returns a 404, the same response as an unknown id.
Ask your account team to enable this setting. It is opt-in for now and becomes the default in a future release, so test your integration against it early.
The summer release: CloudRaker, the public API, and playbooks that work with people
This is a big one — we hope you’re as excited as we are!