This page is also inEN
iTeam
API guide · Productivity, documents and e-signature With your company’s credentials

Clicksign API: what you can do and how to use it with AI agents

Clicksign is a Brazilian e-signature service. Its API lets you send documents for electronic signature, add signers, use templates and follow progress through to completion. Real estate agencies, HR, legal and sales teams that close contracts in volume use it. Access is through an account token, with a separate test environment.

Nina
API guide

What the Clicksign API offers

Documents

Upload files or generate them from templates for signature.

Signers

Register who signs, with the authentication method and signing order.

Envelopes and flows

Group documents and signers into a single signing process.

Templates

Documents with variable fields filled in automatically.

Notifications and webhooks

Reminders to signers and events when someone signs, declines or the document is completed.

How to access the Clicksign API

  • With your company’s credentialsUses an access token generated in the Clicksign dashboard, with separate tokens for the test (sandbox) and production environments.
  • Test in the sandbox before sending real documents.
  • Check signer details: a wrong email sends the contract to someone else.
  • Documents contain personal data: apply Brazil's LGPD (the data-protection law) when filing.

Official documentation: developers.clicksign.com

What an iTeam agent does with the Clicksign API

Contract generated from the proposal

When the proposal is accepted in the CRM, the agent fills in the template, sends it for signature and notifies the salesperson.

Chasing pending signatures

The agent tracks stalled documents and sends a reminder to the right signer, without bothering those who already signed.

Paperless onboarding

The HR agent sends the new employee's document package and only releases the next step once everything is signed.

Final document filing

Once the document is complete, the agent downloads the signed version and files it in the client's folder with a standard name.

From the credential to the agent at work, with approval

01

Generate the token

In the Clicksign dashboard, create the token first in the test environment and then the production one.

02

Register in the vault and choose templates

Store the token in the iTeam vault and define which templates and folders each agent can use.

03

Approve before sending

In the first weeks, every document goes through a human check before it reaches the signer.

Questions

Questions about the Clicksign API

Is the Clicksign API free?

API access depends on the plan you contract. It is usually included in integration-oriented plans, and the cost follows the volume of envelopes or documents.

Do I need to write code to use the Clicksign API with iTeam?

Not necessarily. iTeam reads the Clicksign documentation and the deployment team sets up templates, flows and approvals.

Can the agent sign on behalf of the company?

That is not recommended. The agent prepares and sends. The person with the authority to sign remains the one who signs.

Next step

Put an AI team to work this week.

Start free with a pre-built team, or talk to us and our squad puts AI in production with your people.

300+integrations
4languages
Agents working right now