PASAR API
Brazilian e-signature platform meeting local integrity/authenticity/non-repudiation requirements; REST API plus webhooks and an embedded signing widget, authenticated with an access token.
View docs ↗ More Auth & identity APIs# Clicksign ~ electronic signature API needs an access token ~ get yours at: # https://developers.clicksign.com/ curl 'https://app.clicksign.com/api/v1/' \ -H 'Authorization: Bearer YOUR_TOKEN'
I'm integrating a Brazil API into my app. API: Clicksign ~ electronic signature API Provider: Clicksign Auth: requires an access token (sign up: https://developers.clicksign.com/) Pricing: paid Base URL: https://app.clicksign.com/api/v1/ Important note: Brazilian e-signature platform meeting local integrity/authenticity/non-repudiation requirements; REST API plus webhooks and an embedded signing widget, authenticated with an access token. Source: Clicksign (https://developers.clicksign.com/) Source type: Provider API or developer docs Endpoint type: Provider API base URL Integration difficulty: Needs token Last checked: 2026-07-05 Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs. Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.