When registration is required
Not every caller-identity feature requires registering a business. The dividing line is whether a feature puts your own legal brand in front of recipients or carriers. That’s what needs a verified enterprise (a Federal EIN + a signed Letter of Authorization). Lighter-weight features work without one.
So: CNAM and baseline reputation monitoring need no EIN. Branded Calling and own-brand
reputation/remediation do. You can ship calls and watch reputation on day one, then register an
enterprise when you want your own brand on the screen.
Registering an enterprise
When you do need it (Branded Calling or own-brand reputation), the flow is:1
Create a draft
POST /v1/caller-trust/enterprise with your legal business details. Starts in DRAFT.2
Generate & sign the LOA
POST /v1/caller-trust/enterprise/generate-loa produces the authorization PDF; sign and submit
with POST /v1/caller-trust/enterprise/sign-and-submit (or …/submit if signed out of band).3
Vetting
Status moves
PENDING_VETTING → APPROVED (or REJECTED → fix and resubmit). Poll
GET /v1/caller-trust/enterprise or subscribe to the enterprise.status.updated webhook.4
Brand your calls
Once
APPROVED, your Display Identity Record becomes eligible. Submit it via
Branded Calling to push your name, logo, and reason to recipients.Working with a specific registration
/v1/caller-trust/enterprise always refers to your primary registration — for almost every
account that’s the only one, and the flow above is all you need. If your account holds more than
one registration (for example a draft created while an earlier one is still vetting), every
operation is also addressable by registration ID:
The
{id} is the id returned when you create the draft (POST /v1/caller-trust/enterprise).
Both spellings hit the same underlying operations — the id-addressed form just pins which
registration they act on.
For the full two-tier model (shared umbrella vs. own-brand) and how reputation and branded calling
relate, see the Caller Trust concept guide.