List invoices

Endpoint used to retrieve the invoices registered in the account.

This request returns a paginated list and allows filters to be applied in order to locate invoices by period, financial link, customer, external reference, or status.

Unlike retrieving a specific invoice, this method returns a paginated list containing all invoices matching the provided filters.

Query parameters

  • offset - Defines the starting position of the listing.

  • limit - Defines the number of records returned per request. The maximum limit is 100.

  • effectiveDate[ge] - Filters invoices with an issuance date equal to or greater than the informed date.

  • effectiveDate[le] - Filters invoices with an issuance date equal to or lower than the informed date.

  • payment - Filters by the identifier of the linked payment.

  • installment - Filters by the identifier of the linked installment.

  • externalReference - Filters by the invoice external reference in your system.

  • status - Filters by the invoice status.

Possible values include:

  • SCHEDULED

  • AUTHORIZED

  • PROCESSING_CANCELLATION

  • CANCELED

  • CANCELLATION_DENIED

  • ERROR

  • customer - Filters by the customer identifier.

Filter examples

Filter by issuance date:

GET https://api.asaas.com/v3/invoices?effectiveDate%5Bge%5D=2018-06-03&effectiveDate%5Ble%5D=2018-06-10

Filter by status:

GET https://api.asaas.com/v3/invoices?status=SCHEDULED
📘

Learn more

Filters can be combined for more specific queries.

  • It is possible to query invoices simultaneously by period, customer, linked payment, or status.
  • This behavior is useful for reporting, operational monitoring, and financial reconciliation.

Use cases

This endpoint is useful for:

  • monitoring issued invoices
  • financial reconciliation
  • report generation
  • tracking the issuance lifecycle
  • validating invoice processing statuses
Query Params
integer
integer
≤ 100
string
string
string
string
string
string
enum
Allowed:
string
Responses

403

Forbidden. Occurs when the request body is filled, GET method calls must have an empty body.

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json