Get invoice counts

Returns the number of valid sales invoices for companies managed by the authenticated ISV workspace. The response includes a count for each company and the combined total.

Endpoint

GET /v3/connect/invoices/counts

Base URL

All requests use the Complyance API base URL:

https://prod.gets.complyance.io

There is no separate sandbox hostname. Select the data environment with the X-Environment header: sandbox for test data, or production (the default) for live data.

Authentication

Send your API key in the X-API-Key header.

Keep API keys secret. Do not include a real API key in documentation, client-side code, or source control.

Request headers

Query parameters

When from and to are both omitted, the endpoint returns all-time counts.

The date range filters on each invoice's latest processing update date (updatedAt, falling back to createdAt when the invoice has no processing updates), not the invoice issue date.

Example: all-time counts

Replace {API_KEY} with an API key for your account.

curl --location 'https://prod.gets.complyance.io/v3/connect/invoices/counts?countryCode=AE' \
  --header 'X-API-Key: {API_KEY}' \
  --header 'X-Environment: sandbox' \
  --header 'Accept: application/json'

Example: counts within a date range

curl --get 'https://prod.gets.complyance.io/v3/connect/invoices/counts' \
  --header 'X-API-Key: {API_KEY}' \
  --header 'X-Environment: sandbox' \
  --header 'Accept: application/json' \
  --data-urlencode 'countryCode=AE' \
  --data-urlencode 'from=2026-07-01' \
  --data-urlencode 'to=2026-07-31'

Example: one company

curl --get 'https://prod.gets.complyance.io/v3/connect/invoices/counts' \
  --header 'X-API-Key: {API_KEY}' \
  --header 'X-Environment: sandbox' \
  --header 'Accept: application/json' \
  --data-urlencode 'countryCode=AE' \
  --data-urlencode 'companyId=company-1'

Successful response

{
  "success": true,
  "data": {
    "totalCount": 17,
    "clients": [
      {
        "clientId": "company-1",
        "count": 12
      },
      {
        "clientId": "company-2",
        "count": 5
      }
    ]
  },
  "meta": {
    "requestId": "01K1EXAMPLE000000000000000",
    "timestamp": "2026-08-12T10:00:00.000Z",
    "filters": {
      "countryCode": "AE",
      "environment": "sandbox"
    }
  }
}

The values in this example are illustrative.

Response fields

Managed companies with no matching valid invoices are included with a count of 0. Inactive companies remain included so their historical counts stay visible. If the workspace has no managed companies for the selected country, the endpoint returns:

{
  "success": true,
  "data": {
    "totalCount": 0,
    "clients": []
  },
  "meta": {
    "requestId": "01K1EXAMPLE000000000000000",
    "timestamp": "2026-08-12T10:00:00.000Z",
    "filters": {
      "countryCode": "AE",
      "environment": "sandbox"
    }
  }
}

Error response

Errors use the standard Connect API envelope:

{
  "success": false,
  "error": {
    "code": "CONNECT_INVALID_DATE_RANGE",
    "message": "from must be less than or equal to to."
  },
  "meta": {
    "requestId": "01K1EXAMPLE000000000000000",
    "timestamp": "2026-08-12T10:00:00.000Z"
  }
}

Error codes

Counting behavior

• Only sales invoices resolved to the valid status are counted.
• Purchase documents and non-valid invoices are excluded.
• from and to filter on the invoice's latest processing update date (updatedAt, falling back to createdAt), not the invoice issue date.
• Inactive companies remain included so their historical counts stay visible.
• Results are scoped to the workspace associated with the API key.
• companyId, when supplied, must belong to the authenticated ISV workspace.
• Date boundaries are inclusive and evaluated using the selected country's local calendar date.

Rate limit

This endpoint allows up to 120 requests per minute for each workspace.