400-level errors

Bad Request responses occur when the customer sends an invalid or improperly formatted request to Rapid Transit, or if the implementer has not yet configured, or misconfigured, the setup. These errors can usually be resolved by altering the request.

Table 1. Rapid Transit 400-level error codes
Status code Error type Error message Resolution
400 Conflicting parameters

URL parameter conflict with HTTP headers / {conflict} / {URL value} / {header value} /

Description:

{conflict}: The name of the conflicting element

{URL value}: The URL parameter value

{header value}: The header value

 Either make the URL parameter and the HTTP header's value match, or remove one of the values when making the request
400 Missing value

Quick decision / Missing required value for {missing} /

Description:

{missing}: The value that is required, but no URL parameter or HTTP header was provided

 Provide the missing value as either an HTTP header or a URL parameter
400 Empty payload Payload cannot be size 0 / Provide a non-empty payload
400 No mode lookup Quick decision / Warning: Could not find quick decision configuration matching given criteria Either provide HTTP headers or URL parameters that match existing decision criteria, or configure a decision criteria for the values that are being passed
400 Missing required header

Missing required header: {missing} /

Description:

{missing}: The value that is provided, but no URL parameter or HTTP header was provided

 Provide the missing value as either an HTTP header or a URL parameter
401 Unauthorized Failed to authenticate / Provide credentials that match an existing user, or create a user with credentials that match the request
413 Payload too large Payload too large / Provide a payload that is smaller than the 100Kb threshold