Error code

30487: Toll Free rejection: Charity must provide 501(c)(3) verification

Correctable and resubmittable. Stated by: Twilio error page for this code.

What this error means

You're soliciting donations as a charity but didn't prove 501(c)(3) status.

Causes, most likely first

  1. Identified as a charity/nonprofit with no 501(c)(3) tax-exempt verification supplied.
  2. Accreditation URL missing or invalid.
  3. Business details don't confirm nonprofit status.

How to fix it

If your numbers are managed by a platform

If your numbers sit inside a reseller platform, for example LeadConnector numbers inside GoHighLevel, you do not have access to the Twilio Console, and the interface shows the rejection without the code. Ask that platform's support team for the Twilio rejection error code, in writing, before you change anything. You can also read it yourself from your browser, which is faster: see how to get the code.

The substance of the fix is yours to make: the business details, the website, and the opt-in flow described in the Twilio path all belong to you, not to the platform. Make those changes first, confirm they are live, then ask support to resubmit. A resubmission filed before the underlying facts change will fail again on the same reason.

If you own the Twilio account

Confirm the organisation is a registered 501(c)(3). Supply a valid accreditation URL from a recognised source. BBB Wise Giving Alliance, Charity Navigator, or GuideStar. Make the organisation name and other details match official nonprofit records. Update the rejected request with the verification details and resubmit.

Timing and resubmission

Correctable, resubmit within seven days for priority review.

Two ways forward

Have it handled for you

A2P registration is handled for you on Growth at $597/mo and on Scale at $1,197/mo. Registration, resubmissions, and the compliance work behind them are included.

See Growth and Scale

Fix it yourself

Send your email and we will send the fix playbook for registration rejections.

Verified against Twilio documentation on 2026-08-10.