Navigation
VigilbaseDocs

    Type at least two letters.

    Open Vigilbase One

    Get a customer’s login organisation

    Whether the customer has its Vigilbase Identity organisation, and its id.

    Deprecated aliases: GET https://one.vigilbase.com/api/customers/{id}/organization. They answer with the same bodies, with a Deprecation header and a successor-version link to this URL.

    GET/customers/{customerId}/organization

    Authorizations

    Send one of these:

    AuthorizationstringAccess tokenheaderrequired

    Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login. Scope: one:api.

    AuthorizationstringAPI keyheaderrequired

    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.

    AuthorizationstringMCP tokenheaderrequired

    Vigilbase Identity access token issued to an MCP client (mcp.vigilbase.com). Scope: one:read.

    Permissions checkedread:customers

    Path Parameters

    customerIdstringuuidrequired

    Response

    application/json

    Success

    hasOrganizationbooleanrequired
    organizationIdstring | nullrequired

    The Identity organisation the customer’s people sign in to.

    2 response headers
    X-Request-Idstring

    The request ID: yours when it was well-formed, otherwise a new one. Quote it to support.

    API-Versionstring

    The major API version (informational; the version is in the path).

    More about this endpoint in the guide.

    Was this page helpful?