Create an activity token

Creates a signed, workspace-scoped, project-scoped, subject-scoped token for customer-facing activity views. API keys need the events:read scope.

POST /v1/workspaces/{workspaceId}/activity-tokens

Create an activity token

cURL

curl --request POST \
  --url https://lodger.dev/v1/workspaces/{workspaceId}/activity-tokens \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "projectId": "core",
  "subject": "user_123",
  "expiresInSeconds": 900
}
'

200

{
  "token": "<string>",
  "activityUrl": "<string>",
  "subject": "<string>",
  "workspaceId": "<string>",
  "projectId": "<string>",
  "expiresAt": "2023-11-07T05:31:56Z"
}

Authorizations

Authorization · string · header · default: lodger_sk_your_key · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId · string · required

Example:

"org_01JZ2M9E7G6D8R5K3D"

Body

application/json

projectId · string · required

Example:

"core"

subject · string · required

Example:

"user_123"

expiresInSeconds · integer · default: 604800

Required range: 60 <= x <= 2592000

Response

200

application/json

A scoped activity token.

token · string · required

activityUrl · string · required

subject · string · required

workspaceId · string · required

projectId · string · required

expiresAt · string<date-time> · required