GET /sms/lines/{line}/blocked/{number}
Check whether a number is blocked
| Scope | sms:read |
| Role permission | Phone numbers — line must be one of theirs |
| Cost | Free |
Answers "is this number blocked?" If it is, you get a 200 with the
block details; if not, a 404 (a clear "no"). It returns 404 rather
than a 200 with an empty body, which your code could easily confuse with
an error.
Path parameters
| Name | Type | Required | Example | Description |
|---|---|---|---|---|
line | string | yes | 12125550188 | One of your account's numbers. Digits. |
number | string | yes | 13475550123 | The other party's number. Digits. |
Responses
200
The blocked sender.
| Field | Type | Description |
|---|---|---|
line | string | Your account number (the line) the sender is blocked on. |
number | string | The blocked sender's phone number. |
reason | string | Free text for your own records. Never shown to the blocked party. |
blockedAt | string (RFC 3339) | When the block was added, RFC 3339 UTC. |
Errors
| Status | Meaning |
|---|---|
400 | invalid_request — a missing or malformed field, an unknown enum value, or an unknown field in the body. Nothing was charged. |
401 | unauthenticated — no credential, or one that is invalid, revoked or expired. The WWW-Authenticate header names the scope the endpoint wanted. |
403 | Two different failures share this status; the type field tells them apart — insufficient_scope (the credential lacks the scope) or permission_denied (the scope is fine, but the user's role lacks the permission). |
404 | not_found — no such object, or it is not this account's. The two are deliberately indistinguishable. |
500 | internal_error — something failed on our side, not with your request. Safe to retry. |
See Errors for the full catalog and what to do about each.
Example
curl -X GET 'https://api.account.telebroad.com/api/public/v1/sms/lines/12125550188/blocked/13475550123' \
-H "Authorization: Bearer $TB_KEY"