Requests

/api/v1/requests — GET

GET/api/v1/requests

Requests opened during calls, in ascending updated_at order. Incremental pull: store next_cursor and send it as cursor next time; has_more=false means nothing new for now. The phone is masked unless the company enabled personal data for the Data API. Email is not masked.

• Authentication: Authorization: Bearer rz_live_…
• Scope: read:requests
• Plan feature: Data API — if off, the endpoint answers 404 not_found

Parameters

Name	In	Type	Limits	Meaning
status	query	string | null		Request status: acik, islemde, tamamlandi, reddedildi.
since	query	string (date-time) | null		From this moment on (ISO 8601).
cursor	query	string | null		next_cursor from the previous response.
limit	query	integer	≥ 1, ≤ 100, default 50	Page size.

Example

curl -s -G "$RZ_API/api/v1/requests" -H "Authorization: Bearer $RZ_KEY" \
  --data-urlencode "since=2026-09-24T00:00:00+03:00" --data-urlencode "status=acik"

Response 200

{
  "items": [
    {
      "id": "0199…",
      "number": "TLP-000012",
      "call_id": "0199…",
      "kind": "iptal",
      "status": "acik",
      "order_number": "98765",
      "order_status": "processing",
      "customer_name": "Ayşe Yılmaz",
      "email": "[email protected]",
      "phone": "+90 532 *** ** 67",
      "details": {},
      "history": [],
      "created_at": "2026-09-24T09:12:03Z",
      "updated_at": "2026-09-24T09:12:03Z"
    }
  ],
  "next_cursor": "2026-09-24T09:12:03.120000+00:00_0199…",
  "has_more": false
}

Error statuses: 401, 403, 404, 413, 422, 429 — see Errors and limits.