Scrive
E-signing: agents prepare documents, send them for signature and check their status through the Scrive eSign API.
Connect it with: Sign in (OAuth), API key. Scrive's own documentation: https://apidocs.scrive.com/.
What agents can do
Connect Scrive so the agents working your tasks can reach it. With it connected, they can:
- Create a document from a PDF or a template, add signing parties and send it for signature.
- Check a document's status: who has signed, who has not, and when it expires.
- Download signed documents and their evidence attachments.
- Send reminders to parties who have not signed, or cancel a document that is no longer needed.
Before you start
- A Scrive eSign account on a plan that includes API access.
- For an API key: access to your account's Integration settings to generate personal access credentials.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Scrive
This is the quickest way in: you sign in to Scrive and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Scrive and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Scrive. Scrive's sign-in window opens.
- Sign in to Scrive if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Scrive yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Scrive for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
doc:check | Agents check who has signed, read document details and download signed files | Yes |
doc:create | Agents prepare documents from a PDF or template and add the signing parties | No — you may untick it |
doc:send | Agents send a prepared document out for signature | No — you may untick it |
offline_access | Lets Jaah renew the one-hour access token, so you do not sign in again every hour | Yes |
Connect with an API key
Prefer this when you cannot sign in with Scrive — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Client credentials identifier: In Scrive, open Account > Integration settings (scrive.com/new/integrations), and under Personal access credentials select Generate (or Show if they exist). Copy Client credentials identifier.
- Client credentials secret: Shown beside the identifier under Personal access credentials, in Account > Integration settings.
- Token credentials identifier: Shown under Personal access credentials, in Account > Integration settings.
- Token credentials secret: Shown under Personal access credentials, in Account > Integration settings. Generating new personal credentials replaces all four values.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Scrive card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Client credentials identifier, Client credentials secret, Token credentials identifier, Token credentials secret.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Scrive when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Scrive's developer console, https://scrive.com/new/integrations (Scrive's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Scrive secret, select Use your own OAuth app, paste both values and select Connect Scrive.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Scrive's API once (GET https://scrive.com/api/v2/documents/list?max=1) with the stored values, and shows whether Scrive accepted it, or which value Scrive refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: api_client_id, api_client_secret, api_token_id, api_token_secret.
Tell the agent in your task description which secret to use, for example “use the Scrive secret org/scrive”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Scrive once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Scrive ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Scrive's side too, revoke Jaah in Scrive's settings, or revoke or delete the key at Scrive.
Limitations
- Personal access credentials act as you, with everything your Scrive user can do (a sign-in is limited to the scopes you approve); there is one set per user, and generating new ones invalidates the old set.
- Signed-in agents can read, prepare and send documents; cancelling a document or sending reminders needs personal access credentials, which carry full access.
- This integration reaches Scrive's production service at scrive.com (not scrive.eu); the API testbed (api-testbed.scrive.com) needs its own account and is not connected here.
- Sending a document for signature is real: signing invitations go out to the parties at once.
- Agents can do only what the connected Scrive account and its granted scopes allow.
Troubleshooting
Test says Scrive rejected the token credentials secret (401 or 403)
One of the four personal access credentials was mistyped, or they were regenerated since you copied them. Open Account > Integration settings, copy all four values again, and select Replace on the secret.
Test says Scrive rejected the access token and asks you to reconnect
The sign-in has ended: Scrive's refresh token lasts 30 days without use, and an admin may have removed the OAuth client. Select Reconnect on the secret and sign in to Scrive again.
Integration settings or Personal access credentials are missing in Scrive
Your plan or your user role does not include API access. Ask your Scrive company admin to enable it, or contact Scrive support.
Still stuck? Select Test and read the result: it names the value Scrive refused and the status it answered.
FAQ
Should I sign in or use personal access credentials?
Sign in with Connect Scrive when it is available: you never copy a key, and you can end access from Scrive at any time. Use personal access credentials for a dedicated integration user or when the Jaah app is not configured.
Will agents send documents without asking?
Agents do what the task tells them. Sending starts signing invitations right away, so say in the task whether the agent should only prepare a draft for you to send.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Scrive account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.