Get an SMS sender
/v1/sms/senders/{sender_id}await bird.smsSenders.get("snd_01krdgeqcxet5s7t44vh8rt9mg");client.sms_senders.get("snd_01krdgeqcxet5s7t44vh8rt9mg")result, err := client.SmsSenders.Get(ctx, "snd_01krdgeqcxet5s7t44vh8rt9mg")
if err != nil {
log.Fatal(err)
}
fmt.Println(result)$bird->smsSenders->get('snd_01krdgeqcxet5s7t44vh8rt9mg');bird sms senders get <sender-id>curl -X GET "https://us1.platform.bird.com/v1/sms/senders/{sender_id}" \
-H "Authorization: Bearer $TOKEN"{
"id": "snd_01krdgeqcxet5s7t44vh8rt9mg",
"source_kind": "number",
"sender_type": "long_code",
"country_code": "US",
"number_id": "nda_01krdgeqcxet5s7t44vh8rt9mg",
"status": "active",
"next": [
{
"kind": "operation"
}
],
"destinations": {
"active": [
"US"
],
"pending": [
"US"
],
"needs_attention": [
"US"
]
}
}
Returns one of your workspace's SMS senders with its per-country registration status.
Parameter
sender_idstringID of the SMS sender (snd_ prefix), as returned when the sender was created.
Payload Respons
idIdentifier of this sender.
senderThe value messages are sent from: a number in E.164 format, a shortcode, or an alphanumeric sender string.
source_kindWhat backs an SMS sender: a dedicated number, a shared shortcode, or an alphanumeric sender string.
Possible values (may grow over time): number, shared_number, alpha
sender_typeThe kind of sender identity this is, which decides what each destination country asks of it. It is finer than source_kind: a short code and an ordinary long code are both numbers but follow different rules.
Possible values: long_code, short_code, alphanumeric, toll_free
country_codeThe country of the number this sender sends from. Null for an alphanumeric sender.
number_idThe number this sender sends from, as returned in the id field of GET /v1/numbers. Present only when source_kind is number or shared_number; an alphanumeric sender has no number behind it. Exactly one sender exists per number, so this is also how you go the other way: GET /v1/sms/senders?number_id={id} returns this sender.
statusWhere a sender stands on its own setup: the ownership paperwork its number owes, and whether any destination is active yet.
active: at least one destination is active.pending_number_ownership: the paperwork proving you own this sender's number is not in place, either because it has not been supplied or because the country that issued the number has not accepted it yet. Every send from this sender is refused until it does.pending_registrations: no destination is active yet, whether because the sender has not registered where a registration is required, its registration is under review, or it was refused. Follownextto the requirements read to see which, country by country.
This is not whether a message will be accepted. That is decided per destination country, and
Get sender requirements is the
only read that answers it. A country that requires a registration, where you have not
registered, is in none of the three destinations lists. Read next for where to go from here.
Possible values: active, pending_number_ownership, pending_registrations
nextWhat to do next about this sender, given the state it is in. Present on reads that compute it: an empty list means there is nothing to do, and the field is absent entirely on responses that do not report next actions.
This routes rather than advises. A sender only knows about itself, so where the work is per-country it names the requirements read rather than guessing which country you meant.
destinationsWhere this sender stands with the destinations it is set up for, grouped by whose move is next.
These are not every country the sender could reach. pending and needs_attention cover
only countries you hold a registration for, so a country you could register for but have not,
or one you have simply not switched on, appears in none of the three: there is nothing
outstanding there. To see everything reachable and what each country would take, read
Get sender requirements.
created_atupdated_atSumber daya terkait
Lanjutkan dengan dokumentasi, panduan, dan contoh untuk topik ini.