Skip to main content
GET
List generation requests
List a platform customer’s eBRC generation requests. Use this to find older request IDs, audit past submissions, or drive a status dashboard on your side.

Request example

Filters: requestId, status, fromDate / toDate (ISO dates), plus page / limit for pagination. status matches case-insensitively as a substring and accepts a comma-separated list, so status=Failed,Error,Rejected returns every refused filing in one call.

Response

A generation-request array in data.data plus a meta block with total, page, limit and totalPages, wrapped in the standard envelope. Each row carries the request’s identifiers and lifecycle fields — requestId, iecNumber, recordResCount, uploadType, dgftAckId, status, processedAt, createdAt, updatedAt. The submitted records and the certificate numbers are not included by default, because one request can cover thousands of invoices and every row on the page would carry them. Both are available on request through the two flags below.

Getting your submitted records back

Add includeRecords=true and each row gains ebrcBulkGenDtos: the records you sent in Submit new IRMs, echoed back in the order you submitted them.
Use it to reconcile your side against what we hold, without spending a live DGFT call on Fetch eBRC details just to read data back. It is opt-in for the same reason as includeCertificates, only more so: a record is a full ~20-field object rather than a two-string pair. When the flag is set, page size is capped at 5 and each request returns at most 2000 records, oldest-first by submission order. Past that, recordsTruncated is true for that row and the remainder is only retrievable through Fetch eBRC details.
Before August 2026 the documented response listed ebrcBulkGenDtos unconditionally, but the API stopped returning it on 25 July 2026 when the list projection was slimmed to keep large batches from exhausting memory. includeRecords=true is the supported way to get it back.

Getting eBRC numbers in this response

Add includeCertificates=true and each request row gains a compact certificates array: the invoice number and eBRC number of every certificate issued for that request:
Pass ebrcNumber straight to Download eBRC PDF. No DGFT call is made (these are read from data already stored), so you do not need Fetch eBRC details just to obtain the number. It is opt-in because a generation request is a batch: one request can cover thousands of invoices. When the flag is set, page size is capped at 10 and each request returns at most 2000 certificates. If a request somehow exceeds that, certificatesTruncated is true for that row. The remaining certificates are only retrievable through Fetch eBRC details, which queries DGFT directly.

status values

Next steps

Authorizations

x-api-key
string
header
required

Query Parameters

platformCustomerId
string
required
requestId
string
status
enum<string>

Filter by request status

Available options:
Pending,
Validated,
Failed,
Processed,
Errored,
Error
fromDate
string<date>
toDate
string<date>
page
integer
default:1
Required range: x >= 1
limit
integer
default:10
Required range: x >= 1
includeCertificates
boolean
default:false

Include a compact certificates array on each request row (invoice number + eBRC number). Page size is capped at 10 and each request returns at most 2000 certificates, with certificatesTruncated set when there are more.

includeRecords
boolean
default:false

Include the ebrcBulkGenDtos array on each request row: the records you submitted in push-irm, echoed back. Page size is capped at 5 and each request returns at most 2000 records, with recordsTruncated set when there are more.

Response

200 - application/json

Paginated GenEBRC requests

data
object[]
meta
object