Skip to main content
Give each customer its own dedicated number from Blujay’s ready numbers, in the area code you choose. When a customer no longer needs it, release it.
Partner accounts only. These calls need a partner admin key and the customer’s Blujay-Workspace header.

Assign a number

Name an area_code, or leave it out for any available number.
201 Created (shortened)
The number is ready to send. The full response also has its limits, health and capabilities, like GET /v1/phone-numbers. Full reference: Assign a phone number. The area code is matched exactly, never swapped for a nearby one. If none is free, 409 AREA_CODE_UNAVAILABLE lists the area codes that are in error.details[0].available_area_codes.

See a customer’s numbers

curl
Each number shows whether it can send right now, its limits and its health. See Phone numbers and limits.

Release a number

The response is the number with released_at and quiet_until. Until quiet_until the customer keeps the history and still receives texts on the number, but can’t send from it. Then the number retires for good. Full reference: Release a phone number.

Limits

Over a daily or monthly limit, assigning returns 429 with error.details[0].scope partner. Need more? Ask Blujay support.

Confirm with webhooks

See the payloads on Webhook events.

Good to know

  • Retry safely. Send an Idempotency-Key on assign; a repeat returns the number it assigned first.
  • Queued texts wait. Scheduled and queued texts on a released number don’t send.
  • Releasing twice is safe. A number that’s already released comes back unchanged.
  • No numbers free? Assigning returns 409 NO_PHONE_NUMBERS_AVAILABLE; try again later or ask support.

Next steps

Partner webhooks

One endpoint for every customer’s events.

Phone numbers and limits

Sending limits and health for each number.