NF-e issuance

NF-e issuance is one of stackin's two document surfaces (the other is NFS-e). It's reachable through the same API key, the same base URL, and the same dashboard as everything else — issuing a service invoice tomorrow doesn't mean a new integration.

As a product surface, NF-e issuance is one call: POST /invoices with document_type: "nfe". The response returns synchronously once the authorizer has answered — issued with an access key, or rejected with the authorizer's own reason — there's no separate polling step for the common case.

Every document lands in one of three states — issued, rejected, or cancelled — visible on the dashboard alongside the raw payload sent and the authorizer's raw response, which matters when a rejection needs to be handed to whoever owns the company's tax compliance rather than debugged blind.

Quota is counted per successful issuance, not per attempt — a rejected submission (bad NCM, missing required field) doesn't consume plan volume, since nothing was actually transmitted to and authorized by SEFAZ.

The same endpoint, key, and response shape work in both homologation and production; the only thing that changes between environments is which one the API key was created against, which is fixed for that key's lifetime.

See the API reference for the exact request/response shape, and Issue NF-e for the fiscal fields NF-e specifically requires.