Build a workflow around Stand.

The Public API lets your tools work on your Stand account. It is available on all plans, with the same role, ownership and plan checks as the underlying features. A permission does not add a paid capability or another person’s access.

Use the public OpenAPI document to find the operation, required scope, input and response. The current contract contains 109 operations across 19 business scopes. Paths include /v1; the production server origin is https://api.stand.chat. Only published operations are available to external clients.

The supported public OAuth client is stand-cli. Use Node.js 22 or newer on macOS, Linux or WSL, install the official package, and request only the scopes needed for the task. This conversation review needs profile:read and sessions:read, with no write permission. An explicit --scopes list replaces the previous selection.

Keep the command running while you complete signup or sign-in and consent in the browser. Wait for the CLI’s credential-storage result after the browser says Stand CLI authorized. A new account must also complete its initial profile and organization in the dashboard; the API cannot do that onboarding.

The CLI stores credentials privately and renews five-minute access tokens within the 30-day capped offline-session policy. Expiry or revocation can require another human login. A scheduled process uses that person’s authorization; this release does not provide custom-client registration, personal access tokens or an independent service account.

Inspect listArchivedSessions before making the request. Use scope=myself for your own accessible conversations; organization-wide history requires the current organization owner. An owner’s archived access does not grant access to a teammate’s live conversation.

Replace both timestamps with the period you intend to review. They filter close time, require a timezone, and use an exclusive upper bound. Keep all filters the same when moving between pages. The site filter matches literal text within a saved page URL, not an exact hostname; inspect those URLs if your analysis needs a single domain.

History pages contain 1–100 records and use offset pagination. Bound page count, elapsed time and bytes, and report whether more results remain. Concurrent changes can move page boundaries, so a page traversal is not a frozen snapshot. A sessions get read is also bounded to at most 500 messages.

The export endpoint freezes the matching conversation set and streams one JSON document. The CLI checks the whole response, failedSessionIds and exportedElements before publishing a new private file, and refuses to overwrite an existing file. An interrupted or invalid stream is not a completed export, even after HTTP 200.

Download only the conversations authorized for the task and keep the file outside your repository. A copy sent to another service has its own access and retention lifecycle. Record the account scope, dates, filters and count with any analysis; verify claims and quotations against the included conversation IDs.

Save the resource ID from the successful response. Names are not unique, and an inaccessible or missing resource is not permission to create a replacement. Read the operation schema, preserve the intended settings, and inspect the saved result.

There is no conditional revision check or general Idempotency-Key guarantee. Coordinate shared edits and stop when another writer may have changed the configuration.

Image uploads use multipart/form-data with a required file part. The CLI supplies the boundary and media type from a regular local file. Inspect the specific operation schema for accepted formats and limits before upload; do not send a base64 string or JSON filename in place of the file.

Your avatar and personal pin use profile:write; your Stand-in images use standins:write; organization pin images use org:write and require the owner. Request the corresponding read permissions to inspect existing settings. Write scopes do not include reads.

The CLI retries some transient GET failures within a bound, but never automatically replays writes. After a timeout, lost response, cancellation after dispatch or server error, read the affected resource and reconcile its ID and content before deciding whether a retry is safe.

Use the API error code and status together. Invalid or interrupted responses can fail validation even when a status was received. Broader scopes cannot supply ownership, restore a disabled membership, add a paid capability or accept browser consent.