SMS Compliance
Endpoints
SMS Compliance
Register NearIQ phone numbers for carrier SMS compliance before sending texts.
GET
SMS Compliance
Phone Compliance covers the required carrier registration flow for NearIQ-owned SMS numbers. The customer flow is:
- Provision a business phone number.
- Register the number or business for SMS compliance.
- Wait for carrier approval.
- Send SMS only after the number is approved.
sms_compliance_pending until the relevant toll-free verification or 10DLC campaign is approved.
GET /api/businesses/me/phone-compliance
Returns compliance records for the active business, including status, rejection details, submitted dates, and the matching phone number.POST /api/businesses/me/phone-compliance
Submits compliance for the active business phone number. Toll-free numbers use carrier toll-free verification. Local US numbers use A2P 10DLC brand registration and campaign registration through the configured Messaging Service.PATCH /api/businesses/me/phone-compliance/
Updates and resubmits a rejected or draft registration. The body accepts the same fields asPOST, but all fields are optional.
POST /api/compliance/status-callback
Signed communications-provider callback endpoint for compliance status changes. It updates verification and linked phone-number records. If callbacks are missed, NearIQ checks pending registrations on a regular schedule. When the status changes, NearIQ sends branded transactional email to the account notification email, profile email, or registration contact email:- Approved: “Your SMS number is ready!”
- Rejected/action required/expired: “SMS verification needs attention”
- Pending after three days: “Your SMS number is being reviewed”
- Pending after seven days: “We’ve escalated your verification - no action needed from you”