Skip to API content
TalkLabs API Docs v3
Recipes
POST Live telemetry

Increment a counter

Record one or more occurrences in a named counter.

POST /api/v3/{appid}/telemetry/contexts/{contextid}/metrics/{key}/increment

Record one or more occurrences in a named counter.

Use customer-defined keys to keep related counters separate. For example, reaction.primary and reaction.secondary can share a context while producing independent totals.

Request

Parameters

Values in the path and query string.

appid path
string TalkLabs ID required

The TalkLabs application ID assigned to your account.

Example: your-app-id
contextid path
string customer-defined required

A customer defined ID for the live context being measured.

key path
string customer-defined required

A customer defined name for this telemetry signal.

Request

JSON body

Send as application/json.

userId
string customer-defined required

The user expressing the reaction. Used for distinct user weighting and abuse limiting.

by
integer · int64

How many occurrences to add. Defaults to 1; values <= 0 are treated as 1.

Request example
{
  "userId": "u-8842",
  "by": 1
}
Response

Status codes

Every JSON response uses the API result envelope.

200 OK ApiResult
400 Bad Request ApiResult
403 Forbidden ApiResult
500 Internal Server Error ApiResult
Search all 118 endpoints Try “join room”, “moderate”, or “POST”.
Request environment

Connect your application

These values fill request examples and the API console. They stay in this browser tab and are never sent to TalkLabs until you run a request.

Credentials are stored in sessionStorage, not in cookies or analytics.