Skip to the operations

Compliance

Autentique in a decision flow.

5 Autentique operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Compliance
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Brazilian electronic signature service, priced per document.

Autentique collects legally valid electronic signatures on documents and keeps the audit trail behind each one — who signed, when, from where, and how they were authenticated. It is the low-cost end of the Brazilian signature market and sells to small businesses and to developers, with an API rather than a sales process. The interface is GraphQL only, which is unusual for the category.

What a flow can call

5 operations, each one a step you can place on the canvas.

  1. POST/v2/graphql

    Create a document to sign

    Creates a document from a file already hosted somewhere Autentique can read, and invites the signers in the same call.

  2. POST/v2/graphql

    Check whether it has been signed

    Reads one document and the state of every signature on it.

  3. POST/v2/graphql

    List documents

    Pages through the organisation's documents. Useful for a reconciliation job that looks for contracts still unsigned, rather than inside a decision — it reads the whole account, not one application.

  4. POST/v2/graphql

    Add a signer to a document

    Adds a party to a document that already exists — a guarantor the decision only asked for once the score came back.

  5. POST/v2/graphql

    Verify the API key

    Returns the account the key belongs to. The cheapest way to confirm a new connection works, and a good first node when setting one up.

Where it sits in the decision

Compliance calls have a natural place in a flow.

Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.

Whatever Autentique returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Autentique as a connection authenticating with an API key.
  • 02Autentique has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Create a document to sign” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Autentique in a flow.

How do I connect Autentique to a decision flow?

Add Autentique as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Autentique in a decision without ever seeing the secret.

Can I test Autentique without touching production?

Autentique exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Autentique?

5 operations, including “Create a document to sign”, “Check whether it has been signed”, “List documents”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Create a document to sign”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Autentique be called?

Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.

Also in Compliance

Ready when you are

Wire Autentique into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs