Track client-side analytics events

curl --request POST \
  --url https://api.verlon.ai/v1/analytics/events \
  --header 'Content-Type: application/json' \
  --data '
{
  "events": [
    {
      "event_name": "<string>",
      "user_id": "<string>",
      "session_id": "<string>",
      "anonymous_id": "<string>",
      "gate_id": "<string>",
      "properties": {}
    }
  ]
}
'

{
  "error": "<string>",
  "message": "<string>",
  "details": "<unknown>"
}

Analytics

Track client-side analytics events

Use when: caller is reporting batched client-side analytics events (page views, feature usage) — for Layer’s product analytics, not for billing or rate limiting

Public endpoint (auth optional). Accepts batched client-side analytics events — page views, button clicks, feature usage. Auth is best-effort: if a valid Bearer token is provided, events are attributed to that user; otherwise the request body’s user_id / anonymous_id is used. Used by Layer’s marketing site and dashboard for product analytics, not for billing or rate limiting.

POST

analytics

events

Track client-side analytics events

curl --request POST \
  --url https://api.verlon.ai/v1/analytics/events \
  --header 'Content-Type: application/json' \
  --data '
{
  "events": [
    {
      "event_name": "<string>",
      "user_id": "<string>",
      "session_id": "<string>",
      "anonymous_id": "<string>",
      "gate_id": "<string>",
      "properties": {}
    }
  ]
}
'

{
  "error": "<string>",
  "message": "<string>",
  "details": "<unknown>"
}

Body

application/json

events

object[]

required

Minimum array length: 1

Show child attributes

Response

Events tracked; response includes the count.

Get the public model + provider registry List experiments owned by the caller

Documentation Index

Body

Response