Skip to main content
A business profile is the verified legal entity (legal name, tax ID, address, authorized contact) behind your number requests. Before a profile can authorize provisioning, it must clear KYB verification (business-identity and TIN/registry matching). The partner API exposes that whole lifecycle so you can run onboarding inside your own product — no Trackly staff in the loop.

​
The flow

  1. Create a profile. If you supply a complete identity (legal name, tax ID, country, authorized contact), KYB verification starts automatically.
  2. Validate a draft first to get field-level errors back (country allowlist, tax-id format, name length) without saving.
  3. Track the verdict: poll verificationStatus on the profile, read the submission history, or receive status webhooks.
  4. Correct and resubmit: when a profile is rejected or needs a name confirmation, edit the identity fields — an identity change re-runs KYB automatically.

​
Verification statuses

KYB verification spends real money, so write operations require a live API key — sandbox keys are read-only for the compliance control plane. The validate dry-run and all reads work with any key.

​
What you need for verification

A profile is ready to submit once it carries all of: addressCountry, taxId, companyLegalName, businessContactFirstName, and businessContactLastName. Validate returns readyForVerification: true when those are present and valid.

​
Next steps

Create a profile

Create and auto-submit for KYB.

Status webhooks

Receive business_profile.* events on every transition.