---
title: "Touch presence"
method: POST
path: "/api/v1/collaboration/presence/touch"
tags: ["collaboration"]
---

# Touch presence

`POST /api/v1/collaboration/presence/touch`

## Request

- Base URL: `https://point11.ai`
- URL: `https://point11.ai/api/v1/collaboration/presence/touch`
- Auth: OAuth 2 (authorization code, authorization URL `https://auth.point11.ai/oauth2/authorize`, token URL `https://auth.point11.ai/oauth2/token`)

Mark the signed-in member as active now on the organization's dashboard for 60 seconds and return who else is active now (the dashboard visible and used within the last 5 minutes), with when to touch again to stay present. Name the browser tab (`tabId`) so that tab's leave (`collaboration_presence_leave`) can end it sooner; once that leave runs, a touch under its id renews nothing, so a tab that comes back touches under a new one. A Point11 operator acting as a member is never shown; they only read. Needs a signed-in user: API keys are refused.

## Headers

- `Point11-Organization` string, uuid
- `Idempotency-Key` string, uuid, required

## Request body

- CollaborationPresenceTouchRequest
  - `tabId` string: The browser tab touching presence, so its leave can end it; after that leave this id renews nothing, so touch under a new one. A touch without one ends only by expiry

## Response `200`

Success.

- CollaborationPresenceTouchResponse
  - `viewers` object[], required: Other members active now, the most recent arrival first, at most a handful
    - `userId` string, required
    - `name` string, nullable, required
    - `initials` string, required
    - `imageUrl` string, nullable, required
  - `total` integer, required: How many other members are active now
  - `nextHeartbeatMs` integer, required: Touch again after this many milliseconds to stay present

## Other responses

- `400`: The input, query, or Idempotency-Key is invalid.
- `401`: The bearer is missing, expired, or not accepted.
- `402`: Billing refused the write: the code names the reason and `details.reason` carries it.
- `403`: The credential lacks the operation's scope or role, or the operation needs a different door.
- `404`: The resource or organization does not exist for this caller.
- `405`: This path takes another HTTP method, named in `Allow`.
- `409`: The request conflicts with current state or with prior use of its Idempotency-Key.
- `413`: The request, or the answer it asks for, is too large; narrow it.
- `429`: The credential's rate budget is spent; retry after `Retry-After` seconds.
- `500`: An unexpected server failure; retry later. Only `request_id` identifies it.
- `503`: A dependency is temporarily unavailable; retry after `Retry-After` seconds.
- `default`: Another status a product answers for its own refusal (for example `415` for an unsupported attachment); branch on `code`.

---

[API](https://skmtc.dev/point11/apis/point11-api.md) · [All operations](https://skmtc.dev/point11/apis/point11-api/llms.txt) · [OpenAPI document](https://skmtc.dev/point11/apis/point11-api/revisions/36a84c7aca11?raw)