Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration

Connect NIC E-invoice Portal to Apragya: IRN, Signed QR and E-way Bills From the Invoice

For finance heads and tax teams who generate e-invoices every day: get the IRN, signed QR and e-way bill from the invoice itself, without uploading JSON files by hand.

An accounts clerk handing a sealed sheet to a truck driver at a godown

To connect NIC e-invoice portal to Apragya, you register for API access on the e-invoice portal, add the API username, password, client ID and client secret against your GSTIN, and test the connection. Invoices then get their IRN and signed QR straight from NIC.

Many Indian businesses still export a JSON file, upload it on the portal, download the result and attach it to the invoice. Each step is a place for a mismatch.

This page covers the credentials, sandbox testing, an illustrative example and what to check before going live.

What manual e-invoice uploads cost

Queues at dispatch

Trucks wait while someone uploads, downloads and prints.

Mismatched details

The portal copy and the books drift when either is edited.

Unclear rejections

Portal errors are cryptic, so fixes take several attempts.

Cancellations missed

An IRN cancelled on the portal stays live in the books.

An example: an Ahmedabad chemicals trader

Take an illustrative trader raising about forty B2B invoices a day, most of them interstate with an e-way bill. The accounts clerk spent the first hour of every day on portal uploads.

One interstate invoice, reported from the record

Tax invoice

  1. NIC issues its token for this GSTIN.

  2. Checked before the request is sent.

  3. No retyping at invoice time.

  4. Stored on the invoice record.

  5. Decoded and shown on the invoice copy.

  6. Vehicle details added before dispatch.

The IRN, QR and e-way bill all land on the same invoice record.

After the switch, the clerk's morning upload disappeared. Rejections came back as plain messages on the invoice, so a wrong pincode was fixed in minutes rather than after three portal attempts.

Stamped sheets beside a toy lorry and a rubber stamp
Each invoice now leaves with its IRN, QR and e-way bill already on it.

How the e-invoice API integration works

Step 1 of 5

Register for API access

On the e-invoice portal, under API registration, per NIC's current eligibility rules.

  1. Register for API access: On the e-invoice portal, under API registration, per NIC's current eligibility rules.
  2. Add credentials: API username, API password, client ID and client secret, with the GSTIN.
  3. Add e-way bill access: E-way bill API access is a separate registration, added if you need it.
  4. Test in sandbox: Sandbox is a setting with its own credentials, using the same code.
  5. Go live: Switch to production credentials and generate the first IRN.

Choosing an e-way bill API integration and e-invoice link

A connection that talks to NIC directly removes the upload step, but only if it handles NIC's token rules and explains its errors. That is where most home-grown scripts fail.

Portal uploads, against Apragya

FeatureManual portal uploadApragya NIC connection
CredentialsPortal login sharedAPI credentials, encrypted
TokensNot applicableCached per GSTIN
ErrorsPortal codesTranslated on the invoice
CancellationOn the portal onlyCancel IRN and e-way bill from the record
SandboxSeparate habitA setting on the connection

Checked against public information on 16 September 2026.

What sets the NIC IRP API registration flow apart

Checks before sending

GSTIN, place of supply and HSN are checked first.

Several GSTINs

One connection per GSTIN, each with its own token.

Signed QR on the copy

The signed invoice is decoded and the QR printed.

GSTIN lookup

Party GSTIN details can be fetched through the same link.

Audit log

Who changed the connection, and when, is recorded.

Agents on exceptions

An agent can summarise rejections for review.

The invoice side is covered in e-invoicing and GSTR-1; for the rules themselves, see the e-invoicing guide.

Getting started

  1. Check on the e-invoice portal whether your GSTIN can register for direct API access.
  2. Register and note the API username, password, client ID and client secret.
  3. Add them in Apragya against the GSTIN and test in sandbox.
  4. Generate a sandbox IRN and e-way bill for a sample invoice.
  5. Switch to production credentials and run both methods side by side for a few days.

Keep the portal login for manual fallbacks; it is not the API password.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

Connecting the NIC e-invoice portal, answered

Is the API password the same as our portal login?
No. The API username and password are created under API registration on the portal. They are separate from the login used in a browser.
Do we need a GSP?
Apragya's connection talks to NIC directly. Whether your business can register for direct access depends on NIC's current rules, so check the portal.
We have several GSTINs. How does that work?
Each GSTIN gets its own connection, because NIC issues tokens per GSTIN.
Can we cancel an IRN from Apragya?
Yes, within the window NIC allows. The cancellation is recorded on the invoice. Check the current time limit in NIC's notification.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Generate your first IRN from the invoice

Add your NIC API credentials, test in sandbox, and report one invoice end to end.