Phone numbers

A WhatsApp number is a normal phone line with the WhatsApp Cloud API turned on. LazyApp does not sell or port numbers: you connect a number you control through Embedded Signup, or claim the shared test sandbox in the console. The test sandbox is free; connecting your own number needs a plan, and an extra number beyond the plan’s allowance is an add-on. Once a number is connected, everything on this page works from the console (Connections → Settings on a number) and from the API. Every endpoint takes the connection uuid from GET /v1/connections. Reads need messages:read. Changes need connections:write, so a key that only sends messages cannot deregister a number or rename the business.

List and inspect numbers

curl https://lazyapp.in/v1/connections \
  -H "Authorization: Bearer $LAZYAPP_API_KEY"

{
  "data": [
    {
      "uuid": "6f1c2b0e-8d3a-4c55-9e0f-2a1b3c4d5e6f",
      "phone_number_id": "106540352242922",
      "display_phone_number": "+919812345670",
      "verified_name": "Acme",
      "status": "active",
      "is_default": true,
      "quality_rating": "GREEN",
      "messaging_limit": "TIER_2K",
      "throughput_level": "STANDARD",
      "registration_status": "registered",
      "two_step_pin_set": true,
      "coexistence": false
    }
  ]
}

The list reads LazyApp’s stored copy and never calls Meta, so it is cheap to poll. GET /v1/connections/{uuid} adds a live block from Meta (display name review, blue tick, phone status, account time zone), cached for five minutes. Pass ?refresh=1 to ask Meta again.

Can this number send right now?

GET /v1/connections/{uuid}/health returns Meta’s own answer for everything involved in a send: the number, its WhatsApp account, your business portfolio and LazyApp’s Meta app.

{
  "can_send_message": "LIMITED",
  "entities": [
    {
      "entity_type": "PHONE_NUMBER",
      "can_send_message": "LIMITED",
      "additional_info": [
        "Your display name has not been approved yet. Your message limit will increase after the display name is approved."
      ],
      "errors": []
    }
  ]
}

`can_send_message`	Meaning
`AVAILABLE`	Everything checks out.
`LIMITED`	Sending works, with a limit. `additional_info` says why.
`BLOCKED`	Meta refuses sends. Each blocked node has `errors` with Meta’s `possible_solution`.

Check health when sends start failing or a customer says messages stopped. Policy restrictions are explained, and can be appealed, in Meta’s Business Support Home; there is no API for appeals.

Limits, quality and speed

Field	What it means
`messaging_limit`	How many different customers you can start conversations with in any 24 hours. Replies inside a customer’s 24-hour window do not count. Since October 2025 the limit belongs to your business portfolio, so every number in it shares it.
`quality_rating`	`GREEN`, `YELLOW` or `RED`, from how customers reacted over the last 7 days.
`throughput_level`	`STANDARD` is up to 80 messages a second, `HIGH` up to 1,000. A number also used in the WhatsApp Business app is fixed at 20.

New portfolios start at 250. To reach 2,000, verify your business in Meta Business Suite, or send 2,000 high-quality template messages to different customers within 30 days. After that, Meta raises the limit automatically (within about 6 hours) when you use at least half of it over 7 days with good quality. The 1,000-a-second speed comes automatically to numbers on an unlimited portfolio that message 100,000 customers a day with at least medium quality. Prefer webhooks to polling: phone_number.quality_changed and connection.attention_required fire when these change. See Event reference.

Verify and register a number

Embedded Signup verifies and registers the number for you. You need these calls when you add a number to an account, move a number from another provider, change the display name, or Meta deregisters a number.

# 1. Meta texts (or calls) the number a 6-digit code
curl -X POST https://lazyapp.in/v1/connections/{uuid}/request-code \
  -H "Authorization: Bearer $LAZYAPP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"code_method": "SMS"}'

# 2. Submit it (123-456 and 123456 both work)
curl -X POST https://lazyapp.in/v1/connections/{uuid}/verify-code \
  -H "Authorization: Bearer $LAZYAPP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"code": "123456"}'

# 3. Register with the two-step PIN (a new number takes this as its PIN)
curl -X POST https://lazyapp.in/v1/connections/{uuid}/register \
  -H "Authorization: Bearer $LAZYAPP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"pin": "212834"}'

Endpoint	Use it to
`POST …/two-step-pin`	Change the 6-digit PIN. There is no way to turn two-step verification off.
`POST …/deregister`	Stop the number on the Cloud API until you register it again. Not allowed for numbers also used in the WhatsApp Business app.

Meta allows 10 register or deregister calls per number in 72 hours. The eleventh returns 422 with meta.code: 133016 and blocks the number for 72 hours, so do not retry registration in a loop.

Display name

curl -X POST https://lazyapp.in/v1/connections/{uuid}/display-name \
  -H "Authorization: Bearer $LAZYAPP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"display_name": "Acme Retail"}'

This answers 202: Meta reviews the name, and customers keep seeing the old one until it is approved. Watch live.requested_display_name_status on the connection or the phone_number.updated webhook. Once approved, register the number again within 14 days (same PIN) or the change lapses. Meta allows 10 changes in 30 days. A number with the blue tick must ask Meta support instead. The profile photo, about text, address, email, websites and category live on the business profile; upload a photo with POST …/business-profile/photo (JPG or PNG, at least 192 × 192 pixels, up to 5 MB).

The blue tick (Official Business Account)

A blue tick shows customers you are the real business and lets people find you in WhatsApp search. Meta decides; you apply. GET …/official-business-account returns Meta’s status and a checklist of what Meta requires: a verified business, a two-step PIN, an approved display name, 30 days on the platform, and not being a WhatsApp Business app or test number.

curl -X POST https://lazyapp.in/v1/connections/{uuid}/official-business-account \
  -H "Authorization: Bearer $LAZYAPP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "business_website_url": "https://acme.example",
    "primary_country_of_operation": "India",
    "supporting_links": [
      "https://news.example/acme",
      "https://reviews.example/acme",
      "https://directory.example/acme",
      "https://press.example/acme-launch",
      "https://magazine.example/acme"
    ]
  }'

Supporting links are optional, but when you send them Meta wants 5 to 10 independent pages about your business. If Meta says no, you can apply again after 30 days.

More numbers on the same account

Embedded Signup returns one number, but a WhatsApp account can hold several. GET …/account lists every number on it with connected showing whether it is already in your workspace.

Connect one you already have: POST …/account/phone-numbers/{phone_number_id}/connect. No Facebook login needed; LazyApp reuses the access it has.
Add a new one: POST …/account/phone-numbers with country_code, phone_number and the display_name customers will see. The new connection starts as phone_registration_pending; then verify and register it.

New portfolios can register 2 numbers; Meta raises that to 20 once the business is verified or reaches the 2,000 limit. PATCH …/account renames the account (only you see the name, in WhatsApp Manager) or sets its time zone with Meta’s numeric timezone_id (for example 71 is Asia/Kolkata). Meta does not allow a time zone change once a partner credit line pays for the account.

When Meta refuses

Every Meta refusal comes back in the same shape, with a sentence you can show to people and Meta’s own code for logs:

{
  "code": "meta_rejected",
  "message": "This number was registered or deregistered too many times. Meta blocks further attempts for 72 hours.",
  "meta": { "code": 133016, "message": "(#133016) Registration or Deregistration failed…", "fbtrace_id": "AXsgnV2Cm3ZMGF3dF_cfYIn" }
}

Status	`code`	What to do
`422`	`meta_rejected`	Fix the request; retrying the same thing fails the same way.
`422`	`meta_permission_missing`	Reconnect the number and approve every permission Meta asks for.
`409`	`connection_token_expired`	Reconnect the number.
`429`	`meta_rate_limited`	Meta is limiting changes to this account. Back off for a few minutes.
`503`	`meta_unavailable`	Meta had a temporary problem. Retry later.

Quote meta.fbtrace_id if you contact support.

Connecting WhatsApp: connect, reconnect and coexistence
QR codes, opt-in links and conversation starters
Capabilities: which features each number has
Event reference: connection.* and phone_number.*

Getting started

Core concepts

WhatsApp

Security

Billing

Sending

Receiving

Platforms

Migrating

Reference

List and inspect numbers

Can this number send right now?

Limits, quality and speed

Verify and register a number

Display name

The blue tick (Official Business Account)

More numbers on the same account

When Meta refuses

​List and inspect numbers

​Can this number send right now?

​Limits, quality and speed

​Verify and register a number

​Display name

​The blue tick (Official Business Account)

​More numbers on the same account

​When Meta refuses

​Related

List and inspect numbers

Can this number send right now?

Limits, quality and speed

Verify and register a number

Display name

The blue tick (Official Business Account)

More numbers on the same account

When Meta refuses

Related