Oten Fiscal · Electronic documents API
Issue NFCom and São Paulo NFS-e through one API.
Official Oten Tecnologia documentation to integrate issuance, queries, cancellation, and fiscal files into your product — with ready-to-use examples and the same JSON contract in every environment.
Two documents. One integration contract.
SEFAZ
NFCom
Electronic Communication Service Invoice. Built for telecom, internet, pay TV, and other communication services authorized by SEFAZ.
NFCom documentation →
3550308
São Paulo NFS-e
Electronic Service Invoice for the City of São Paulo. Same municipal `/nfse` route, with specific ISS and TributacaoRPS rules.
São Paulo NFS-e docs →
How issuance works
Send the JSON
The API validates the schema and business rules and immediately returns the invoice identifier.
Asynchronous processing
The document is forwarded to the authorizer — SEFAZ for NFCom, São Paulo City Hall for NFS-e.
Poll or receive a webhook
Track the status until CONCLUIDO or REJEITADO, then download the PDF and XML.
Built for teams that actually integrate
Stable contract
Fields, statuses, and examples match the API your customers will call.
Sandbox first
Validate the full flow in a test environment before switching to production.
Idempotency via idIntegracao
A unique identifier per invoice prevents duplicates even if the request is retried.
Ready for the tax team
Summary queries, history, PDF, XML, email, and cancellation live in the same route set.