Phone Numbers

See the List Phone Numbers API reference for the full endpoint specification.

curl https://api.linqapp.com/api/partner/v3/phone_numbers \
  -H "Authorization: Bearer $LINQ_API_KEY"

await client.phoneNumbers.list();

client.phoneNumbers.list()

client.PhoneNumbers.List(context.TODO())

Set a forwarding_number to route inbound calls on a line elsewhere. Pass an empty string (or null) to clear it. See the Update Phone Number API reference for the full endpoint specification.

curl -X PUT https://api.linqapp.com/api/partner/v3/phone_numbers/{phoneNumberId} \
  -H "Authorization: Bearer $LINQ_API_KEY"

await client.phoneNumbers.update({phoneNumberId});

client.phoneNumbers.update({phone_number_id})

client.PhoneNumbers.Update(context.TODO(), {phoneNumberId})

The API does not place or answer voice calls directly, but you can route calls around your Linq line:

• Inbound calls — Forward your Linq line to a number of your choice by setting a forwarding_number via the Update phone number endpoint above. Pass an empty string to clear the forwarding number.
• Outbound calls — If you own another number that supports caller-ID masking (for example, a Twilio number with Verified Caller ID), you can mask your Linq number over it so the Linq number displays on outbound calls.
• AI voice agents — Use a VOIP number (commonly Twilio) with the inbound/outbound setups above to route calls to and from your agent via the Twilio API.

See the FAQ for more.

Numbers are provisioned by your Linq representative — there is no self-serve create or delete endpoint on the V3 API. To add or release a line, contact support with the details of the line you want changed.

Numbers carry two independent fields you can react to:

• status — the line’s current sending state.
  • ACTIVE — sending and receiving normally.
  • FLAGGED — a service flag has degraded the number’s ability to send. New messages on a flagged line may fail with delivery errors.
• reputation — line-level prediction of where the line is heading based on the patterns in its conversations and its overall messaging activity. See the Phone Reputation guide for the HEALTHY / AT_RISK / CRITICAL values, what drives each one, and how to react.

The phone_number.status_updated webhook fires when either field changes, and every payload carries both pairs (previous_status / new_status and previous_reputation / new_reputation), so a single subscription covers both signals.

{
  "phone_number": "+12025551234",
  "previous_status": "ACTIVE",
  "new_status": "FLAGGED",
  "previous_reputation": "AT_RISK",
  "new_reputation": "CRITICAL",
  "changed_at": "2026-02-18T18:35:05.000Z"
}

You can also enable Flagged-number Slack notifications in the API Tooling settings to get a Slack message in your linked partner channel whenever a number’s status changes.

Recommended handling:

• Page on-call when a production line transitions to FLAGGED.
• Pause outbound sends on the affected line until it returns to ACTIVE.
• Contact your Linq representative for remediation.
• For reputation transitions to AT_RISK or CRITICAL, follow the playbook in the Phone Reputation guide — typically slow the line’s pace before the line ends up FLAGGED.

• Key Concepts: Phone Numbers
• Phone Reputation — line-level reputation scoring
• Webhooks: Phone number events
• API Reference: Phone Numbers