Follow this guide to connect your Scrive e-signing account to Journeys, so you can send documents for e-signature, track signing status, and pull signed agreements back into your journeys.
Before you start
A Scrive account on the Business plan or higher. API access is required and isn't available on Essentials.
API access enabled on your account. This is what makes the Create button appear under Personal access credentials. If you don't see it (see Step 1), your account doesn't have API access yet — use "Request access" on the Integration settings page or contact Scrive support.
🔒 Logging in with SSO/Google/Microsoft is fine — the steps below don't require a password.
Step 1: Generate your Scrive access credentials
Log in to Scrive and go to Integrations → Integration settings.
Find the Personal access credentials section ("Use these credentials to access your own Scrive account through the API").
Click Create.
If a set of credentials already exists, delete it first, then click Create - the secrets are only shown at the moment of creation, so an existing set won't reveal them.
The page now shows four values. Copy all four:
Client credentials identifier
Client credentials secret
Token credentials identifier
Token credentials secret
⚠️ Copy all four immediately. The two secret values are shown only once. If you leave the page, you'll need to delete and create a new set to see them again.
Step 2: Go back to Journeys and connect
Now that you have your four values, return to Journeys — to the Scrive integration screen where you started.
Open your Scrive integration.
Go to Authentication and paste each value into its matching field:
Client credentials identifier → your Client credentials identifier
Client credentials secret → your Client credentials secret
Token credentials identifier → your Token credentials identifier
Token credentials secret → your Token credentials secret
Host →
https://scrive.com(orapi-testbed.scrive.com
Click Connect and confirm you get a successful response.
And you are done! 🎉 You can now start using the Scrive integration in your journeys 😄
Optional: generate credentials from the terminal
If you prefer, you can generate the same four values with a single API call instead of using the dashboard. This requires an email and password (it won't work with SSO-only logins).
Open your terminal (Mac: Terminal; Windows: Command Prompt or PowerShell).
Replace the placeholders and run. For
{SERVER}, use the host you log in to —scrive.comfor most accounts, orscrive.eufor EU-region accounts.
curl -X POST 'https://{SERVER}/api/v2/getpersonaltoken' \
--data-urlencode 'email={YOUR_EMAIL}' \
--data-urlencode 'password={YOUR_PASSWORD}'
The response contains your four values:
{
"apitoken": "1a2b3c4d5e6f7g8h_12345",
"apisecret": "0a1b2c3d4e5f6g7h",
"accesstoken": "9z8y7x6w5v4u3t2s_67890",
"accesssecret": "1q2w3e4r5t6y7u8i"
}They map to the Journeys fields as:
apitoken → Client credentials identifier,
apisecret → Client credentials secret,
accesstoken → Token credentials identifier,
accesssecret → Token credentials secret.
Troubleshooting
There's no Create button under Personal access credentials API access isn't enabled on your account. Use "Request access" on the Integration settings page or contact Scrive support, and confirm you're on the Business plan or higher.
I can't see the secret values They're shown only once, at creation. Delete the existing set and click Create again, then copy all four immediately.
401 or "OAuth token not valid" in Journeys Re-check that all four values were pasted into the correct fields, with no extra spaces.
Keeping your connection secure
🔒 Treat the two secret values like passwords:
Don't share them in emails, chats, or tickets.
If a secret is ever exposed, delete and recreate your personal access credentials in Scrive, then update the new values in Journeys.