Business verification (KYC)

Submit your business details, what verification is needed for, how review works, and how the Verification Needed account state blocks outbound calling.

Business verification, also called KYC (know your customer), records who is behind a workspace. Carriers and regulators expect it before a platform sells phone numbers or places calls and messages on your behalf. In Tried it is a short form on the Billing page.

The Business verification and Concurrency cards on the Billing page

Submit your details#

Open Business verification#

On Billing, find the Business verification card and click Verify business (or Update details if you have submitted before). Only admins can submit.

Fill in the form#

Enter the details below and click Submit for review.

Check the status#

The card shows the status badge, your business name and country, and when it was submitted and reviewed.

Field	API field	Rules
Legal business name	`business_name`	Required, 2 to 200 characters
Country	`country`	Required, two-letter code such as `AU` or `NZ`
Registration number	`business_registration_number`	Optional, for example an ABN, EIN or company number
Website	`website`	Optional, a full URL starting with `http://` or `https://`
Contact email	`contact_email`	Optional
How you'll use calling	`use_case`	Optional, up to 1,000 characters

curl -X POST https://api.tried.com.au/kyc \
  -H "Authorization: Bearer $TRIED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "business_name": "Harbour Physio Pty Ltd",
    "country": "AU",
    "business_registration_number": "12 345 678 901",
    "website": "https://harbourphysio.example",
    "use_case": "Inbound reception and appointment reminders"
  }'

GET /kyc returns the current profile:

{
  "status": "pending",
  "business_name": "Harbour Physio Pty Ltd",
  "country": "AU",
  "website": "https://harbourphysio.example",
  "submitted_timestamp": 1760668800000,
  "reviewed_timestamp": null
}

Before anything is submitted, the response is { "status": "not_submitted" }. Submissions are recorded in the audit log as kyc.submit.

Review#

Status	Badge	Meaning
`not_submitted`	Not submitted	No details yet
`pending`	Pending	Waiting for review
`approved`	Approved	Verified

How review happens depends on the deployment:

Without a Telnyx key (mock telephony), a complete submission is approved immediately.
With TELNYX_API_KEY set Needs keys, the profile stays pending until the carrier's review is recorded by an operator.

Submitting again replaces the stored details and restarts review.

When verification is required#

Verification is enforced only when the API runs with TRIED_KYC_REQUIRED=1. Then, for workspaces created on or after TRIED_KYC_SINCE (an ISO date; without it, every workspace), these actions need an approved profile:

Action	Error without approval
Buying a phone number	`403`
Placing an outbound call (`POST /v2/create-phone-call`, and each batch call dial)	`403`
Sending an SMS	`403`

The error says, for example, Business verification (KYC) is pending: it must be approved before you can place outbound calls. Submit it with POST /kyc.

Inbound calls, web calls and chats never need verification.

Verification Needed account state#

Separately from the KYC form, the operations team can put a workspace in the Verification Needed account state. While it is set:

Outbound phone calls and batch calls return 402 with error_code: "verification_needed".
A banner across the dashboard says Verify your business to place outbound and batch calls. with a Verify business link.

The state is cleared by operations once the business is verified.