---
title: "GET /connections/{phoneNumber}/reachout-timelock"
method: GET
path: "/connections/{phoneNumber}/reachout-timelock"
tags: ["Connections"]
---

# GET /connections/{phoneNumber}/reachout-timelock

`GET /connections/{phoneNumber}/reachout-timelock`

Fetch the account's reach-out time-lock state — the restriction behind error 463 ('account restricted') that blocks starting new chats. Read-only: queries WhatsApp directly (MEX) without sending a message, so it is safe to call on a restricted account.

## Path parameters

- `phoneNumber` string, required

## Response `200`

Reach-out time-lock state retrieved successfully

- object
  - `data` object
    - `isActive` boolean — Whether the reach-out time-lock is currently enforced
    - `timeEnforcementEnds` string, date-time, nullable — When the current enforcement window ends
    - `enforcementType` string — Reason/type of enforcement. 'DEFAULT' means no restriction.

## Other responses

- `403` — Forbidden — the API key does not own this connection. Returned when a connection is bound to a different API key.
- `404` — Phone number not connected
- `421` — Misdirected Request — in cluster mode, this instance does not own the connection. The owning instance id is in the x-baileys-owner header; a proxy re-routes the request there. Not returned for the explicit-takeover routes: POST /connections/{phoneNumber}, /import-session and /restart.

---

[API](https://skmtc.net/fazer-ai/apis/fazer-ai-baileys-api.md) · [All operations](https://skmtc.net/fazer-ai/apis/fazer-ai-baileys-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fazer-ai/fazer-ai-baileys-api/revisions/5299037901a9/schema)