Skip to main content

User

Introspection endpoints for a poweruser key. Use them to confirm which user and company a key acts as, and to discover every endpoint available on the Poweruser API surface.

All paths on this page are relative to https://api.autessa.com/autessa_poweruser/user. Every request is a POST with a JSON body — send {} when there are no parameters. See the Poweruser API overview for authentication and conventions.


Get the current user​

POST/user/me

Returns the identity behind the key: the linked user and the company scope every request executes in. Call this first when wiring up an integration to verify you are acting as the account you expect.

Request parameters​

None — send an empty object {}.

Response​

  • Name
    email
    Type
    string
    Description

    Email address of the linked user.

  • Name
    name
    Type
    string
    Description

    Display name of the linked user.

  • Name
    companyName
    Type
    string
    Description

    Name of the company the key is scoped to. All resources you create or read belong to this company.

  • Name
    errors
    Type
    array<string>
    Description

    Error messages, if any occurred.

curl https://api.autessa.com/autessa_poweruser/user/me \
-X POST \
-H "Authorization: $POWERUSER_KEY" \
-H "Content-Type: application/json" \
-d '{}'
Response
{
"email": "jane@acme.com",
"name": "Jane Doe",
"companyName": "Acme Corp"
}

List available endpoints​

POST/user/available-endpoints

Returns the complete registry of Poweruser API endpoints — every endpoint key, its request path, and the group it belongs to. This is the same list of endpoint keys you choose from when creating a scoped key, so use it to build key-provisioning UIs or to check what a given key value maps to.

The registry is static: it always returns every endpoint on the platform, regardless of the calling key's own scope. To find out whether your key can call an endpoint, call it — scoped keys receive HTTP 403 for endpoints outside their allow-list.

Request parameters​

None — send an empty object {}.

Response​

  • Name
    endpoints
    Type
    array<EndpointInfo>
    Description

    One entry per endpoint on the Poweruser API.

  • Name
    endpoints[].key
    Type
    string
    Description

    Stable enum key for the endpoint (for example AGENTS_CREATE). Use these values when defining a scoped key's allow-list.

  • Name
    endpoints[].path
    Type
    string
    Description

    Full request path, including the /autessa_poweruser prefix.

  • Name
    endpoints[].group
    Type
    string
    Description

    Human-readable group the endpoint belongs to (for example "Agents", "AutessaDB Queries").

  • Name
    errors
    Type
    array<string>
    Description

    Error messages, if any occurred.

curl https://api.autessa.com/autessa_poweruser/user/available-endpoints \
-X POST \
-H "Authorization: $POWERUSER_KEY" \
-H "Content-Type: application/json" \
-d '{}'
Response (truncated)
{
"endpoints": [
{
"key": "USER_ME",
"path": "/autessa_poweruser/user/me",
"group": "User"
},
{
"key": "AGENTS_CREATE",
"path": "/autessa_poweruser/agents/create",
"group": "Agents"
},
{
"key": "AUTESSADB_QUERY_QUERY",
"path": "/autessa_poweruser/autessadb/query/query",
"group": "AutessaDB Queries"
}
],
"errors": []
}

Errors​

StatusWhen
200Success.
401Invalid or expired key.
403Scoped key without USER_ME / USER_AVAILABLE_ENDPOINTS in its allow-list.
408Server-side error; errors contains the message.