Skip to main content
POST
/
invoices
/
list
List invoices
curl --request POST \
  --url https://api.bitgpt.xyz/invoices/list \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "status": [
    "PENDING"
  ],
  "currency": [
    "<string>"
  ],
  "price_usd_from": 123,
  "price_usd_to": 123,
  "created_at_from": "<string>",
  "created_at_to": "<string>",
  "customer_email": "<string>",
  "provider_id": "<string>",
  "limit": 123,
  "offset": 123
}
'
{
  "status": 200,
  "data": {
    "id": "123"
  },
  "error": null,
  "log": null,
  "validator": null,
  "support_id": null,
  "message": "Resource created successfully",
  "env": "development"
}

Authorizations

​
Authorization
string
header
required

Send your access token as header Authorization: Bearer {accessToken}

​
Authorization
string
header
required

Your API key that starts with sk_live or sk_test. You can create yours at go.bitgpt.xyz/api-keys.

Body

application/json

Request body for filtering invoices

​
status
enum<string>[]

Filter by invoice status

Available options:
PENDING,
COMPLETED,
VOIDED,
PROCESSING,
WAITING_FOR_CONFIRMATIONS,
PARTIALLY_PAID
​
currency
string[]

Filter by currency code

​
price_usd_from

Filter invoices with usd amount greater than or equal to this value

​
price_usd_to

Filter invoices with usd amount less than or equal to this value

​
created_at_from
string<mysql-date-time>

Filter invoices created from this date

​
created_at_to
string<mysql-date-time>

Filter invoices created until this date

​
customer_email
string

Filter by customer email address

​
provider_id
string

Filter by payment provider

​
limit
integer

Maximum number of invoices to return

​
offset
integer

Number of invoices to skip for pagination

Response

Invoice list

​
status
enum<integer>
required

Status code of the response

Available options:
200,
201,
202
​
data
object
required

Response data containing the requested object

​
message
string | null
required

Message of the response, human readable

Example:

"Resource created successfully"

​
env
enum<string>
required

API environment

Available options:
development,
production
​
error
string | null

Error message of the response, human readable

Example:

"Invalid email address"

​
log

Useful informaiton, not always present, to debug the response

Examples:
{ "request_id": "req_1234567890" }

"Some pertinent log message"

​
validator
object

Validator response object, each key is the field name and value is the error message

Example:
{
  "email": "Invalid email address",
  "password": "Password is required"
}
​
support_id
string<uuid> | null

Support ID linked to the response, used to identify it when talking with our team

Example:

"support_uuidv7-something-else"