Skip to content
SzybkiSMSSzybkiSMSSzybkiSMS · REST API problems

Bad request

Request / bad-request

The request does not match an operation described in the API specification.

HTTP 400

How to resolve the problem

Section titled “How to resolve the problem”
  1. Compare the URL and HTTP method with the OpenAPI documentation.
  2. Check the data required by the operation.
  3. Correct the request according to detail.

Response example

Section titled “Response example”
Response headers
HTTP/1.1 400
Content-Type: application/problem+json
Content-Language: en-US
Example API response
{
    "type": "https://api.szybkisms.pl/problems/bad-request/",
    "status": 400,
    "title": "Bad Request",
    "detail": "{validation_message}",
    "code": "400-15",
    "instance": "/rest/messages/sms"
}

code is a diagnostic code for support. instance provides the request path. The example uses the current API identifiers.

Example situations

Section titled “Example situations”
1 situations
HTTP 400Whole request failureLink ↗

{validation_message}

The description depends on request data; {…} indicates a variable fragment.

Check the path and method in the REST API documentation.

Any REST endpoint

Problem type identifier

Section titled “Problem type identifier”
Problem type URI and documentation URL
https://api.szybkisms.pl/problems/bad-request/

Operation results with HTTP 200

Section titled “Operation results with HTTP 200”
Message sending and statusesQueue acceptance, rejection and subsequent delivery status.
Message pricingPrice calculation results and reasons for unsuccessful pricing.
Cancellation and deletionOperation status and Problem Details for individual failures.