80701: Parameter Validation Failed
PROXY
WARNING
Twilio returns this warning when a request to a Proxy resource includes a parameter that does not match the expected schema, format, or allowed value for that endpoint. The warning can appear as <parameter name> is invalid. <parameter is invalid>.
- A required parameter for the resource you are creating was omitted or sent under the wrong field. For example, creating a Service requires
uniqueName, and creating a Participant requiresidentifier. - An enum parameter contains a value outside the supported set, such as
mode,status,geoMatchLevel, ornumberSelectionBehavior. - A SID, URI, or date-time field does not match the required format, such as an invalid
ServiceSid,SessionSid,ProxyIdentifierSid, callback URL, ordateExpiry. - A string or numeric value exceeds Proxy limits, such as
UniqueName,FriendlyName,Identifier,ProxyIdentifier, orttl. - A
proxyIdentifierwas provided for a Participant, but that Twilio number was not already added to the Proxy number pool for the service.
- Review the exact parameter named in the warning and compare it with the schema for the Service, Session, or Participant resource you are calling.
- Send only documented values for enum fields. For example, use one of the supported values for
mode,status,geoMatchLevel, andnumberSelectionBehavior. - Validate identifiers before you send the request. Ensure SIDs use the correct prefix and length, callback fields are valid URIs, and
dateExpiryis a valid ISO 8601 date-time value. - Keep request values within documented limits.
UniqueNamemust be 191 characters or fewer,FriendlyNamemust be 255 characters or fewer,Identifiermust be 191 characters or fewer,ProxyIdentifiermust be 255 characters or fewer, andttlmust be greater than 0 and less than 2147483647. - If you set
proxyIdentifierorproxyIdentifierSidon a Participant, use a Twilio number that is already assigned to the Proxy service's number pool.