A failed brand can be updated by API and not in the console

The requirementstatement

Remediating a failed brand differs by interface: the API permits an update in place, while the console requires delete and recreate.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: the remediation path
Where it liveslayer: BrandBRAND
How Ekas settles itdetectability: DeterministicDETERMINISTIC; Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass: Wait on someone elseTERMINAL_EXTERNAL; Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities: Twilio
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

The same brand, the same fix, and two different procedures depending on where you are standing — so a team that reads the API documentation and works in the console concludes the update is broken. Deleting and recreating is also the more expensive of the two, because a new brand starts its verification from the beginning and takes its campaigns with it.

How to fix itremediation

Fix a failed brand through the API, where an update in place is accepted, rather than deleting and recreating it in the console. Note that the update is accepted only while the brand is in a failed state — a brand that has not failed cannot be updated this way at all.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twilio	30793	Yes

Check this yourselfattestation

Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.

If this brand has failed, are you fixing it through the API rather than deleting and recreating it in the console?

1Use the API update in place — the console path requires delete and recreate, which restarts verification and takes the campaigns with it.
2Note the update is accepted only while the brand is in a failed state; a brand that has not failed cannot be updated this way at all.

What wrong looks like: A team reads the API documentation, works in the console, and concludes the update is broken — then rebuilds a brand that could have been edited.

Notesnotes

Absorbs OPS-345, which states which brand states accept an update at all. Conditional on the interface rather than on the provider, so it is not `providers`-tagged. What the user has to know is that the console path is not the only one available: an API update avoids the rebuild entirely.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

BRD-001A legal company name is required for every entity but a sole proprietorBlockingBLOCKING BRD-002Legal name must match the IRS record for the EINBlockingBLOCKING BRD-003Legal name must carry its exact entity suffix as filedBlockingBLOCKING BRD-008Legal name must not carry an appended personal name or roleBlockingBLOCKING BRD-009The legal name field takes the legal name, not the trading nameBlockingBLOCKING BRD-011A legal business name may back only one brand across the whole registryBlockingBLOCKING

All brand rules

BRD-189 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.