TraceeDocs

Apps

Call a connected app's own API

Signed with the workspace's connection, for anything no action covers. GET runs straight away; anything else becomes an approval request.

POSThttps://traceeai.com/api/v1/apps/{app}/request

CLI:tracee apps request·MCP:appsaction request

Authorizations

  • Authorizationstringheaderrequired

    Bearer <key>: a personal key (tracee login or Settings → Personal keys), a workspace key, or an MCP client's OAuth token. See Authentication.

Headers

  • Tracee-Workspacestring

    For a personal key or OAuth token that reaches several workspaces: the workspace id to act on. Workspace keys don't need it.

    uuid

Path parameters

  • appstringrequired

    The toolkit slug, e.g. hubspot. From GET /api/v1/connections (connectedApps[].app)

    up to 60 characters

Body

application/json
  • endpointstringrequired

    A path relative to the app's API, or a full URL on its domain

    up to 1,000 characters

  • methodstring

    Default GET

    Available options:GETPOSTPUTPATCHDELETE

  • paramsobject

    Query string parameters

    any keys

  • bodyany

    The JSON body

  • connection_idstring

    Which connection, if the app has several. From GET /api/v1/connections (connectedApps[].connection_id).

  • notestring

    Context for the approver

    up to 500 characters

Response

Errors
  • 200Done.

    The action's result, exactly as the MCP tool returns it to agents. A next field, when present, names the endpoint that follows up.