---
title: "Search contacts"
method: GET
path: "/v1/accounts/{accountID}/contacts"
tags: ["Contacts"]
---

# Search contacts

`GET /v1/accounts/{accountID}/contacts`

Search contacts on a specific account using merged account contacts, network search, and exact identifier lookup.

## Path parameters

- `accountID` string, required — Account ID this resource belongs to.

## Query parameters

- `query` string, required — Text to search users by. Network-specific behavior.

## Response `200`

Request executed successfully

- SearchContactsOutput
  - `items` object[], required
    - `id` string, required — Stable Beeper user ID. Use as the primary key when referencing a person.
    - `username` string — Human-readable handle if available (e.g., '@alice'). May be network-specific and not globally unique.
    - `phoneNumber` string — User's phone number in E.164 format (e.g., '+14155552671'). Omit if unknown.
    - `email` string — Email address if known. Not guaranteed verified.
    - `fullName` string — Display name as shown in clients (e.g., 'Alice Example'). May include emojis.
    - `imgURL` string — Avatar image URL if available. May be temporary or local-only to this device; download promptly if durable access is needed.
    - `cannotMessage` boolean — True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
    - `isSelf` boolean — True if this user represents the authenticated account's own identity.

## Other responses

- `400` — Invalid request parameters
- `401` — Access token is missing or invalid
- `403` — Access token does not have the required scope
- `404` — Resource not found
- `422` — Unprocessable entity - validation error
- `429` — Too many requests - rate limit exceeded
- `500` — Internal server error

## Changes

- **2026-02-20** `4acef56b00be` — 14 info
  - added `subschema #1, subschema #2, subschema #3` to the `details` response property `anyOf` list for the response status `400`
  - added `subschema #1, subschema #2, subschema #3` to the `details` response property `anyOf` list for the response status `401`
  - added `subschema #1, subschema #2, subschema #3` to the `details` response property `anyOf` list for the response status `403`
  - added `subschema #1, subschema #2, subschema #3` to the `details` response property `anyOf` list for the response status `404`
  - …10 more

[Change history](https://skmtc.dev/beeper/apis/beeper-desktop-api/changes/v1/accounts/:accountID/contacts/get.md)

---

[API](https://skmtc.dev/beeper/apis/beeper-desktop-api.md) · [All operations](https://skmtc.dev/beeper/apis/beeper-desktop-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/beeper/beeper-desktop-api/revisions/5a8ac7b545c4/schema)