Skribble - Veryfront

At a glance

Availability: Experimental (how to enable).
Auth: Basic auth.
Connection: HTTP Basic auth with SKRIBBLE_API_USERNAME as the username and SKRIBBLE_API_KEY as the password.
Docs: https://api-doc.skribble.com/

Set these per environment. See Connect an integration.

Variable	Required	Description
`SKRIBBLE_API_USERNAME`	Yes	Skribble API username shown when the API key is created (for example api_demo_yourcompany) Docs.
`SKRIBBLE_API_KEY`	Yes	Skribble API key (acts as the password for the API username); shown only once at creation and cannot be recovered afterwards Docs.

Get a Skribble plan with API access: API integration is available on Skribble’s Pro, Scale, Business, and Enterprise plans. For development you can use Demo API keys: signatures requested with them carry no legal weight and are free of charge, so a demo key is the recommended way to test.
Create an API key: Sign in to Skribble, click ‘Admin area’ in the lower-left, go to ‘API keys’, and click ‘Create API key’ at the top right. Choose Demo (testing) or Production (live, invoiced signatures) and optionally add a description.
Store the credentials: On the next screen Skribble shows your API username and the API key (your password). Copy both immediately - the key cannot be recovered after you close the window. Set them as SKRIBBLE_API_USERNAME and SKRIBBLE_API_KEY.

The Skribble API uses a two-step authentication: you POST the username and API key as JSON to https://api.skribble.com/v2/access/login, which returns a JWT access token valid for about 20 minutes, and every subsequent API call sends that token as ‘Authorization: Bearer <token>’.
Because of this login-then-Bearer token exchange, hosted tools for this connector are not yet enabled; the credentials are still collected so signature-request tools can light up once runtime token-exchange support is available.
There is no logout endpoint - the access token simply expires after its lifetime.

No tools yet. The setup guide explains what is pending.