Find a contact by phone number
A separate path from GET /contacts/{id}, not an id that happens to read as a word. Pass the number in E.164 form; a local number is refused rather than guessed.
Try it — GET /contacts/lookup
Kept for this tab only — it disappears when you close it, and it is never sent anywhere except as the Authorization header on the call below.
Authorization
bearerAuth contacts:readAuthorization: Bearer sk_live_.... Keys in the query string or the
request body are refused — a URL is logged by every proxy it passes,
and that is how customer keys leak.
A key carries scopes. A call outside them answers 403 with
insufficient_scope and names the scope it wanted.
In: header
Scope: contacts:read
Query Parameters
E.164, with the leading +.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET https://app.sendkuy.com/api/v1/contacts/lookup \ -H "Authorization: Bearer sk_live_YOUR_API_KEY"{ "data": { "object": "contact", "id": "con_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3", "group_id": "grp_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3", "first_name": "string", "last_name": "string", "whatsapp": "+6281234567890", "email": "string", "sms": "+6281234567890", "attributes": {}, "status": "active", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" }}