List User Accounts

GET

/users/{user_id}/accounts

Returns the accounts associated with the given user.

Authorizations

Send your API key in the x-api-key header. See Authentication.

Parameters

Path Parameters

user_id

required

string

Query Parameters

page

integer

The desired page from the result set. Defaults to 1.

per_page

integer

The number of items per page. Defaults to 100.

Responses

200

Success

object

total

Total number of items across all pages.

integer

15

per_page

Number of items per page.

integer

100

current_page

The current page number (1-based).

integer

1

last_page

The last available page number.

integer

1

from

The index of the first item on this page (1-based).

integer

1

to

The index of the last item on this page (1-based).

integer

15

data

Array<object>

object

id

integer

100

created_at

string format: date-time

updated_at

string format: date-time

name

string

Acme Corporation

description

string | null

closed_at

string | null format: date-time

billing_portal_url

string format: uri

is_account_verified

boolean

true

is_free

boolean

account_closure_in_progress

boolean

account_status

string

Active

terminate_after_date

string | null format: date-time

has_cancellation_zendesk_ticket

boolean

Example

{
  "current_page": 1,
  "data": [
    {
      "id": 100,
      "account_status": "Active",
      "billing_portal_url": "https://www.billingportal.com/manage/1000000/1000000/100000000",
      "closed_at": null,
      "account_closure_in_progress": false,
      "created_at": "2024-01-10T08:00:00Z",
      "description": null,
      "has_cancellation_zendesk_ticket": false,
      "is_account_verified": true,
      "is_free": false,
      "name": "Acme Corporation",
      "terminate_after_date": null,
      "updated_at": "2024-01-10T08:00:00Z"
    },
    {
      "id": 200,
      "account_status": "Closed",
      "billing_portal_url": "https://www.billingportal.com/manage/2000000/2000000/200000000",
      "closed_at": "2025-03-15T12:00:00Z",
      "account_closure_in_progress": false,
      "created_at": "2024-03-05T14:30:00Z",
      "description": null,
      "has_cancellation_zendesk_ticket": true,
      "is_account_verified": true,
      "is_free": false,
      "name": "Wayne Enterprises",
      "terminate_after_date": "2025-06-15T00:00:00Z",
      "updated_at": "2025-03-15T12:00:00Z"
    }
  ],
  "from": 1,
  "to": 2,
  "last_page": 1,
  "per_page": 100,
  "total": 2
}

401

The x-api-key header is missing or the key is not valid, or the caller can’t access an ID in the request. IDs that don’t exist return the same response as IDs the caller can’t access.

Error envelope returned with 4xx and 5xx responses.

object

error

object

code

Usually the HTTP status code. It can differ; a request to an unknown path returns HTTP 400 with code 500.

integer

401

message

Human-readable description of the error.

string

type

The kind of error, for example Authorization or REST.

string

REST

fields

Returned only with 422 responses. It may give more details about what failed validation, as lists of messages keyed by the name of the input.

object

key

additional properties

Array<string>

Examples

{
  "error": {
    "code": 401,
    "message": "The request does not include a valid access token. Please provide a valid access token.",
    "type": "Authorization"
  }
}

{
  "error": {
    "code": 401,
    "message": "x-api-key: x-api-key is invalid",
    "type": "REST"
  }
}

{
  "error": {
    "code": 401,
    "message": "User does not have access to requested resource.",
    "type": "Authorization"
  }
}