What this endpoint does#
Lists phone-verification contacts for the community resolved from the Bearer API key.It is not loyalty overview. It does not verify a phone number. An empty page is a successful read.Authenticate → GET /v1/community-analytics/phone-verification-contacts → read data.data and data.pagination.
Quick start#
Authentication and permission#
Bearer community API key. Community comes from the token. Keep the key server-side.Complete examples#
Empty page (200). message is Phone verification contacts fetched successfully. Envelope { status: "success", message, data: { data, pagination } }.pagination includes total, page, limit, totalPages. limit defaults to 100 when omitted. data.data: [] with total: 0 means no contacts, not a missing route.Success and readback#
HTTP 200. Repeat with another page to refresh. This GET is a read.A 200 with data: [] means this community has no phone-verification contacts on that page.
Errors and recovery#
| Status | When | Recovery |
|---|
401 | Missing or invalid token | Add a valid community key. |
Retry safety#
This GET does not write contacts. Retry timeouts with bounded backoff.
Gotchas#
Do not invent a row schema from an empty list.
Next steps#
Get Loyalty Overview
Community-wide loyalty rows (XP, coins, redemptions, visits) are a separate read.