FBR invoice integration API
FBR invoice integration API work starts with the PRAL Digital Invoicing API using an IRIS bearer token. Integron exposes the same submission path through a managed dashboard plus optional REST endpoints — so your team does not maintain low-level PRAL client code.
API integration in practice
PRAL API vs Integron REST
FBR’s official integration surface is the Digital Invoicing API (operated by PRAL). You authenticate with a token generated in the IRIS portal for your NTN. Integron uses that token on your behalf for validate/submit from the web app. Taxpayer accounts can also create API keys to call Integron’s REST API and configure outbound webhooks when invoice status changes.
Typical integration patterns
- ERP or billing system posts invoice JSON → Integron → FBR
- Nightly batch import via CSV/API, validate in sandbox, submit in production
- Webhook notifies your system when IRN and QR data are stored
- Connector import pulls external billing rows into drafts before validate/submit
- Async FBR jobs with email and in-app alerts when submission fails
Sandbox, production, and compliance
Always test invoice scenarios in sandbox before switching the production token. Notified registered persons must use an integration route permitted by FBR, including a licensed integrator or PRAL where applicable — complete that IRIS setup before API automation. Software uses the bearer token from your completed IRIS configuration; it does not replace integrator or registration requirements. See FBR invoice integration overview.
Setup help: IRIS bearer token guide, Help center, contact.
Connect your stack to FBR
Start with the dashboard, then enable API keys when you are ready to automate.