eSignatures.io integration

Quick start

Call eSignatures.io from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to eSignatures.io'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(
  "ESIGNATURES_IO_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

End-users supply their own eSignatures.io API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

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

• ESIGNATURES_IO_ADD_TEMPLATE_COLLABORATOR
• ESIGNATURES_IO_COPY_TEMPLATE
• ESIGNATURES_IO_CREATE_CONTRACT
• ESIGNATURES_IO_CREATE_SIGNER
• ESIGNATURES_IO_CREATE_TEMPLATE
• ESIGNATURES_IO_DELETE_SIGNER
• ESIGNATURES_IO_DELETE_TEMPLATE
• ESIGNATURES_IO_GENERATE_CONTRACT_PDF_PREVIEW
• ESIGNATURES_IO_GET_CONTRACT
• ESIGNATURES_IO_GET_TEMPLATE
• ESIGNATURES_IO_LIST_TEMPLATE_COLLABORATORS
• ESIGNATURES_IO_LIST_TEMPLATES