Pin Twilio API and helper-library versions; re-check compliance yearly

TL;DR

Keep it explicit in your code and config rather than relying on SDK defaults you have not read. Twilio ships new SDK majors rarely, but when it does (the v1 to v2 Lookup behavior change is the template: 404 became 200 with valid=false), unpinned upgrades break validation logic silently.

Steps

1. The API version is in the URL path: 2010-04-01. Keep it explicit in your code and config rather than relying on SDK defaults you have not read.
2. Pin helper library versions in your lockfile. Twilio ships new SDK majors rarely, but when it does (the v1 to v2 Lookup behavior change is the template: 404 became 200 with valid=false), unpinned upgrades break validation logic silently.
3. Re-check messaging compliance once a year: 10DLC registration rules, toll-free verification requirements, and per-country sender ID rules all tighten over time. Code written against last year's rules can become non-compliant without any code change.
4. When Twilio announces a deprecation or behavior change, treat it as a skill update: write the migration as a checklist (old behavior, new behavior, verification step), not as a code comment.

When to use

You are seeing this: Twilio's API surface is unusually stable, which makes agents complacent. Use this skill when you run into "Pin Twilio API and helper-library versions; re-check compliance yearly".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

An agent's training data freezes at some point in the past.

Twilio's API version 2010-04-01 is embedded in request paths (e.g. api.twilio.com/2010-04-01/Accounts/...), a long-standing stable surface documented across the API reference. Regulatory requirements for 10DLC brand/campaign registration and toll-free verification have tightened over time per Twilio's compliance docs: https://www.twilio.com/docs/messaging/compliance/a2p-10dlc