Skip to the operations

Business verification

Serpro in a decision flow.

4 Serpro 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
Business verification
Type
Integration
Authentication
OAuth 2.0 client credentials
Test environment
Production host only

Who they are

The Brazilian government's data processing company.

Serpro is state-owned and operates the technology behind Receita Federal and other federal bodies, which makes it the primary source for CPF and CNPJ registration data rather than a reseller of it. It sells that data through a developer portal, per product, with free demonstration endpoints that answer for published test documents. Where an audit has to name where a fact came from, this is the answer that ends the question.

What a flow can call

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

  1. GET/consulta-cpf/v1/cpf/$data.cpf

    Look up a CPF (Receita Federal)

    Name, date of birth and registration status for a CPF, straight from Receita Federal.

  2. GET/consulta-cnpj/v2/basica/$data.cnpj

    Look up a CNPJ (registration data)

    Registration data for a company: legal name, trading name, opening date, registration status and main activity.

  3. GET/consulta-cpf-df/v1/cpf/$data.cpf

    Look up a CPF (free demonstration)

    The same call against Serpro's free demonstration product, which answers only for a published set of test documents.

  4. GET/consulta-cnpj-df/v2/basica/$data.cnpj

    Look up a CNPJ (free demonstration)

    The demonstration twin of the CNPJ lookup, answering for a fixed set of test companies.

Where it sits in the decision

Business verification calls have a natural place in a flow.

Company checks answer whether the entity applying exists, who controls it, and whether its filings support the application. They usually run early: if the company cannot be verified, most of what follows is moot, and the flow can decline or refer before spending on anything else.

Whatever Serpro 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 Serpro as a connection authenticating with OAuth 2.0 client credentials.
  • 02Serpro has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Look up a CPF (Receita Federal)” 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 Serpro in a flow.

How do I connect Serpro to a decision flow?

Add Serpro as a connection in your workspace authenticating with OAuth 2.0 client credentials, 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 Serpro in a decision without ever seeing the secret.

Can I test Serpro without touching production?

Serpro 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 Serpro?

4 operations, including “Look up a CPF (Receita Federal)”, “Look up a CNPJ (registration data)”, “Look up a CPF (free demonstration)”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Look up a CPF (Receita Federal)”. 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 Serpro be called?

Company checks answer whether the entity applying exists, who controls it, and whether its filings support the application. They usually run early: if the company cannot be verified, most of what follows is moot, and the flow can decline or refer before spending on anything else.

Also in Business verification

Ready when you are

Wire Serpro 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