Skip to main content
Send one curl request and see an Operata contact in the response, in the v2 data model. You need a Group ID, an API token, and curl. Using the v1 format? See Quickstart (v1).

​
Before you start

  • An Operata account. Your Operata Group ID is the UUID in the console URL.
  • An API token generated under Settings → Config → API.

​
Make the request

​
What you should see

A JSON array with one contact. This example is shortened; the full response also has the agent’s machine and softphone, WebRTC endpoints, and headset data:

​
What the response means

  • You authenticated with HTTP Basic — Group ID as username, token as password. See Authentication.
  • You requested one contact from a 24-hour window using the v2 contact summary endpoint. See List contact summaries (v2).
  • Each contact carries accountProperties, contact, serviceAgent, webRTCSession, and billing. The contact ID is contact.id.current.
  • The response is a plain JSON array. The RecordCount response header holds how many contacts match in total, and you page with from and size. See Pagination.
  • A 429 response means you hit the per-token budget — back off using Retry-After. See Rate limits.
  • Errors come back as an HTTP status code with a short plain-text body. See Errors.

Concepts

The mental model behind contacts, signals, and observations.

API reference

Every endpoint, every parameter.

Data redaction

Choose which fields to strip before they reach Operata.