List a customer’s services
The services Vigilbase runs for the customer, newest first. Billing amounts need read:billing.
Deprecated aliases: GET https://one.vigilbase.com/api/customers/{id}/service-records. They answer with the same bodies, with a Deprecation header and a successor-version link to this URL.
Authorizations
Send one of these:
Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login. Scope: one:api.
Organisation API key (vb_one_…) from Settings → API keys in Vigilbase One, sent as Authorization: Bearer vb_one_…. Read-only keys work. See organisation API keys.
Vigilbase Identity access token issued to an MCP client (mcp.vigilbase.com). Scope: one:read.
Path Parameters
Query Parameters
A cursor-paginated list: the response holds items, and while it has a nextCursor, pass it as cursor for the next page. See pagination.
The nextCursor of the previous page. Leave it out for the first page.
How many items to return per page.
50maximum 200Response
application/jsonSuccess
13 child attributes
Integration tool, e.g. cloudflare, ninja-one.
activeinactivependingerrorThe customer’s account at the provider.
Null unless the caller may read billing amounts.
2 response headers
The request ID: yours when it was well-formed, otherwise a new one. Quote it to support.
The major API version (informational; the version is in the path).
More about this endpoint in the guide.