twilio

Postconditions — what we check

• create · messages-create-no-try-catch

  error
  Whenmessages.create() called without try-catch or .catch() handler
  ThrowsRestException with error.code, error.status, and error.message
  Required handlingMUST wrap await client.messages.create() in try-catch block. Catch block should check error instanceof RestException and handle specific error codes (14107 for rate limiting, 20003 for invalid credentials, 21211 for invalid phone numbers) appropriately.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[1]
• create · messages-create-generic-catch

  warning
  Whenmessages.create() in try-catch but doesn't check RestException
  Required handlingSHOULD check error type using instanceof RestException and inspect error.code. Handle rate limiting (14107) with retry logic, authentication errors (20003/20005) by validating credentials, and validation errors (21211/21212) with user feedback.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[2]
• create · messages-create-rate-limit-not-handled

  warning
  WhenBulk SMS operations without rate limit handling
  Required handlingSHOULD check for error.code === 14107 and implement exponential backoff retry logic. Consider using retry-after information if available.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[1]
• create · calls-create-no-try-catch

  error
  Whencalls.create() called without try-catch or .catch() handler
  ThrowsRestException with error.code, error.status, and error.message
  Required handlingMUST wrap await client.calls.create() in try-catch block. Catch block should check error instanceof RestException for detailed error information.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[1]
• create · verifications-create-no-try-catch

  error
  Whenverifications.create() called without try-catch
  ThrowsRestException with error.code, error.status, and error.message
  Required handlingMUST wrap verification create call in try-catch block. Handle specific error codes for better user experience.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[3]
• twilio · hardcoded-credentials

  error
  WhenTwilio client initialized with hardcoded credentials
  Required handlingMUST use environment variables for credentials. Use process.env.TWILIO_ACCOUNT_SID and process.env.TWILIO_AUTH_TOKEN. Never commit credentials to version control.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[4]
• twilio · missing-auth-error-early-detection

  warning
  WhenInitial API call doesn't check for authentication errors
  Required handlingSHOULD validate credentials with test API call during initialization. Check for error codes 20003 and 20005 to fail fast with clear error messages.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[1]
• validateRequest · webhook-no-signature-validation

  error
  WhenWebhook endpoint doesn't validate request signature
  Required handlingMUST validate webhook signatures using twilio.validateRequest() or twilio.validateExpressRequest(). Reject requests with invalid signatures (return 403).
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[5]
• create · verification-check-no-try-catch

  error
  WhenverificationCheck.create() called without try-catch or .catch() handler
  ThrowsRestException with error.code, error.status, and error.message
  Required handlingMUST wrap await verificationCheck.create() in try-catch. Handle error.code 60202 (max attempts — tell user to request a new code), 404 status (code expired — prompt re-send), and error.code 20003 (auth failure — alert ops).
  costhighin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[6][7]
• create · verification-check-expired-not-handled

  error
  WhenverificationCheck.create() does not handle 404 for expired verifications
  ThrowsRestException with status 404
  Required handlingSHOULD check error.status === 404 in the catch block and direct the user to request a new verification code via verifications.create().
  costmediumin prodimmediate exceptionusers seedegraded performancevisibilityvisible
  Sources[6]
• create · verification-check-max-attempts-not-handled

  warning
  WhenverificationCheck.create() does not handle error code 60202 (max check attempts)
  ThrowsRestException with error.code 60202
  Required handlingSHOULD check error.code === 60202 and show a user-friendly message explaining that the code has expired and they must request a new verification code. Automatically trigger verifications.create() to send a fresh code.
  costmediumin prodimmediate exceptionusers seedegraded performancevisibilityvisible
  Sources[7][6]
• fetch · lookups-fetch-no-try-catch

  error
  Whenlookups.v2.phoneNumbers().fetch() called without try-catch
  ThrowsRestException with error.code, error.status, and error.message
  Required handlingMUST wrap await phoneNumbers(number).fetch() in try-catch. For user-submitted numbers, handle 21421 (invalid format) with a user-facing validation message. Handle 20003 (auth failure) with ops alerting.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[8][9]
• fetch · lookups-invalid-number-result-not-checked

  warning
  Whenlookups.v2.phoneNumbers().fetch() result valid field not checked
  Required handlingSHOULD check phoneNumber.valid === true after fetch(). If false, inspect phoneNumber.validationErrors array and return appropriate user feedback before attempting to send SMS or make calls.
  costlowin prodsilent failureusers seedegraded performancevisibilitysilent
  Sources[8]
• update · calls-update-no-try-catch

  error
  Whencalls(sid).update() called without try-catch or .catch() handler
  ThrowsRestException with error.status and error.code. Error 21220 (HTTP 400) — call is no longer in-progress (already completed, failed, or cancelled); this is the most common runtime error. Error 20003 (HTTP 401) — authentication failure. Error 20429 (HTTP 429) — rate limit exceeded. NetworkError — connection timeout or DNS failure.
  Required handlingMUST wrap await client.calls(sid).update() in try-catch. Handle error.code === 21220 gracefully — it means the call already ended, which is usually not a fatal condition. Handle error.code === 20003 with ops alerting.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[10][11]
• update · calls-update-stale-call-not-handled

  warning
  Whencalls(sid).update() does not handle error 21220 (call already ended)
  ThrowsRestException with error.code 21220 (HTTP 400)
  Required handlingSHOULD check error.code === 21220 in the catch block and treat it as a no-op (the call is already ended, which was the goal of cancellation) rather than propagating as an unrecoverable error.
  costlowin prodimmediate exceptionusers seedegraded performancevisibilityvisible
  Sources[11]
• fetch · messages-fetch-no-try-catch

  error
  Whenmessages(sid).fetch() called without try-catch or .catch() handler
  ThrowsRestException with error.status and error.code. HTTP 404 (status 404) — message SID not found or belongs to different account. Error 20003 (HTTP 401) — authentication failure. Error 20429 (HTTP 429) — rate limit exceeded on status polling. NetworkError — connection timeout.
  Required handlingMUST wrap await client.messages(sid).fetch() in try-catch. Handle error.status === 404 to detect invalid/foreign message SIDs rather than crashing the status-check loop.
  costlowin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[12]
• fetch · messages-fetch-undelivered-not-checked

  warning
  Whenmessages(sid).fetch() result status not checked for 'undelivered' or 'failed'
  Required handlingSHOULD check message.status after fetch(). If status is 'undelivered' or 'failed', inspect message.errorCode and message.errorMessage for the root cause and implement retry logic or user notification.
  costmediumin prodsilent failureusers seedegraded performancevisibilitysilent
  Sources[12]
• create · recordings-create-no-try-catch

  error
  Whencalls(sid).recordings.create() called without try-catch
  ThrowsRestException with error.status and error.code. Error 21220 (HTTP 400) — call is not in-progress (already ended, ringing, or queued); cannot start recording on an inactive call. Error 20003 (HTTP 401) — authentication failure. Error 20429 (HTTP 429) — rate limit exceeded. NetworkError — connection failure.
  Required handlingMUST wrap await calls(callSid).recordings.create() in try-catch. Handle error.code === 21220 gracefully — log the missed recording but do not propagate as a fatal error when the call already ended.
  costmediumin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[13][11]
• create · verify-services-create-no-try-catch

  error
  Whenverify.v2.services.create() called without try-catch
  ThrowsRestException with error.status and error.code. HTTP 400 — invalid parameters (e.g., friendlyName too long, invalid codeLength). Error 20003 (HTTP 401) — authentication failure, invalid Account SID or Auth Token. Error 20429 (HTTP 429) — rate limit exceeded (too many service creation attempts). NetworkError — connection failure.
  Required handlingMUST wrap await verify.v2.services.create() in try-catch. On error, log with full error.code context and fail the tenant provisioning flow with a clear user-facing error rather than leaving the tenant in a half-initialized state.
  costhighin prodimmediate exceptionusers seeservice unavailablevisibilityvisible
  Sources[14][15]

Sources

Every postcondition cites at least one of these. Numbered to match the footnotes above.

1. [1]twilio.com/docs/apihttps://www.twilio.com/docs/api/errors
2. [2]github.com/twilio/twilio-nodehttps://github.com/twilio/twilio-node
3. [3]twilio.com/docs/verifyhttps://www.twilio.com/docs/verify/api/verification
4. [4]twilio.com/docs/usagehttps://www.twilio.com/docs/usage/secure-credentials
5. [5]twilio.com/docs/usagehttps://www.twilio.com/docs/usage/webhooks/webhooks-security
6. [6]twilio.com/docs/verifyhttps://www.twilio.com/docs/verify/api/verification-check
7. [7]twilio.com/docs/errorshttps://www.twilio.com/docs/errors/60202
8. [8]twilio.com/docs/lookuphttps://www.twilio.com/docs/lookup/api
9. [9]twilio.com/docs/errorshttps://www.twilio.com/docs/errors/21421
10. [10]twilio.com/docs/voicehttps://www.twilio.com/docs/voice/api/call-resource
11. [11]twilio.com/docs/errorshttps://www.twilio.com/docs/errors/21220
12. [12]twilio.com/docs/smshttps://www.twilio.com/docs/sms/api/message-resource
13. [13]twilio.com/docs/voicehttps://www.twilio.com/docs/voice/api/recording-resource
14. [14]twilio.com/docs/verifyhttps://www.twilio.com/docs/verify/api/service
15. [15]twilio.com/docs/errorshttps://www.twilio.com/docs/errors/20003