API pricing
This page provides detailed information about Autentique’s API pricing structure. It includes tables with the costs for different actions, along with usage and billing examples.
API usage follows the same plans as regular usage through the web application. However, the plan’s cost serves as a monthly usage commitment, and additional charges apply if total API usage exceeds that amount. The free plan has no fees but is limited to 20 documents per month.
You can check your current API usage on Plans and Payment section of your account.
Prices per document and signature request
Document creation
$ 0.01
R$ 0,06
Signature request via Email
$ 0.002
R$ 0,013
Signature request via Whatsapp
$ 0.02
R$ 0,12
Signature request via SMS
$ 0.03
R$ 0,16
Signature request via link, signed through email
$ 0.002
R$ 0,013
Signature request via link, signed through SMS
$ 0.03
R$ 0,16
Signature request via link, signed through Whatsapp
$ 0.02
R$ 0,30
Signature with additional Phone validation
$ 0.03
R$ 0,16
Prices are cumulative and depend on the number of signers and the signature methods used.
Signers added via a signing link can select their preferred signing method: email, SMS, WhatsApp, or authentication via Google, Microsoft, or Facebook. They are charged according to the method they choose to sign the document, but signatures completed via Google, Microsoft, or Facebook login are free of charge.
The cost of signing via a WhatsApp link may differ from the cost of sending a signature request through WhatsApp due to WhatsApp API message category pricing. However, this is not usually the case. Keep this in mind when designing your signing flow to optimize message delivery costs.
If you have a specific use case that’s not feasible under this pricing model, feel free to reach out to our sales team. Custom, volume-based pricing can be negotiated under the Corporate plan.
Pricing per query
Some queries incur a cost when executed. This charge is primarily intended to discourage implementations that make excessive data requests (we’ve all been there). Still, those workarounds started adding up on our end, so please don’t use Autentique as your backend.
Retrieve document data (per document)
$ 0,0002
R$ 0,001
Webhook Delivery
$ 0,00004
R$ 0,0002
“Retrieve document data” charges are applied per document retrieved, not per query. So if you request 10 documents in a single query, you’ll be charged $ 0.0002 × 10.
You typically don’t need to worry about query costs unless you’re doing something very wrong. If you ever notice a significant charge from queries, it might be a good time to sit in the shower, stare at the tiles, and reconsider your architecture choices.
Webhook pricing
To keep your application updated efficiently, you can set up webhook endpoints to receive real-time updates. This is the clean, no-hacks way to keep your systems in sync with the latest document information. Check out our documentation for details, and contact support if you have any questions.
Failed webhook deliveries appear in your dashboard, where you can review and retry them. Failed deliveries are included in billing, but retries are not.
Deprecated webhook events are also counted but do not appear in the failed webhooks list.
Request limit
Each plan includes a default rate limit (requests per minute) per API token. If you need a higher limit, just reach out and we’ll adjust it based on your needs.
Free
10 per minute
Professional
60 per minute
Corporate
200 per minute
Usage commitment and billing
The plan’s cost represents a minimum monthly usage commitment. If your API usage exceeds that amount, the excess will be billed on an additional invoice covering the previous month’s activity.
Important: Actions performed through the web application don’t generate charges and don’t affect API billing.
Sandbox and tests
Documents created with the parameter sandbox: true are not charged. However, they are meant strictly for testing and are automatically deleted after a few days.
Do not use real documents in sandbox. The sandbox is for testing purposes only. Sandbox documents are automatically deleted, they do not generate audit logs, and cannot be used for verifying signatures or authenticating documents.
Last updated
Was this helpful?