Reinf API coverage

The public API follows the whole operational trail of EFD-Reinf: structural events, periodic series, closings, reopenings, exclusions, submissions, webhooks, reports, receipts and proofs.

Initial registrations

Context, taxpayers and the structure of the operation.

Integration context and account permissions
Taxpayers and establishments
Reinf responsibles, R-1000, R-1070 and auxiliary tables
Digital certificates per taxpayer

Submissions

Reinf messaging, batches and artifacts.

R-2000, R-3000 and R-4000 series
Preview, creation and tracking of a request
Event lookups, history, artifacts and operational tracking
Closings and exclusions in the same integration

This trail does not end at submission. It continues through webhook, batch lookup, reports and artifacts so the team understands what has already returned, what still needs action and which fiscal evidence was materialized.

Official spreadsheets

Import via the official template, as an additional entry to speed up registration.

Official .xlsx spreadsheets per event
Upload, preview and confirmation flow
The same public integration used for authentication, submission and tracking
Compatible with AI agents that work with assessment files, XML, PDF, Excel, CSV and operation documents

Tracking

Webhook, dashboard and reports.

Webhook configuration, history and resend
Operational dashboard per period
Reports and reconciliation proofs
OpenAPI specification with a dedicated playground

Portal, API, webhook and reports follow the same operation. The goal is to avoid reconciling receipts, protocols, XMLs and proofs in external controls.