Boldsign integration

Quick start

Call Boldsign from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Boldsign's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "BOLDSIGN_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for Boldsign. End-users click Connect on the integration card in your app, complete the OAuth flow with Boldsign, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2.

Available actions

14 actions exposed via the Boldsign integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• BOLDSIGN_BRAND_GET
• BOLDSIGN_BRAND_LIST
• BOLDSIGN_CUSTOM_FIELD_CREATE
• BOLDSIGN_CUSTOM_FIELD_EDIT
• BOLDSIGN_DOCUMENT_BEHALF_LIST
• BOLDSIGN_DOCUMENT_EDIT_BETA
• BOLDSIGN_DOCUMENT_EXTEND_EXPIRY
• BOLDSIGN_DOCUMENT_LIST
• BOLDSIGN_DOCUMENT_REMOVE_AUTHENTICATION
• BOLDSIGN_DOCUMENT_SEND
• BOLDSIGN_DOCUMENT_TEAM_LIST
• BOLDSIGN_EMBEDDED_REQUEST_CREATE_LINK