Missing request parameter

Request / missing-request-parameter

Message IDs were not provided for retrieval, cancellation or deletion.

HTTP 400

How to resolve the problem

1. Provide IDs in the /messages/{ids} or /incoming/{ids} endpoint path.
2. Separate multiple IDs with commas and avoid empty entries.
3. Omitting the entire path segment can match a different route and produce a different response.

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/missing-request-parameter/",
    "status": 400,
    "title": "Missing Request Parameter",
    "detail": "No outgoing message IDs were provided.",
    "code": "400-3",
    "instance": "/rest/messages/123"
}

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

Example situations

Filter messages and causesClear2 situations

HTTP 400Whole request failureLink ↗

No outgoing message IDs were provided.

Provide outgoing message IDs in the path.

DELETE /rest/messages/{ids}GET /rest/messages/{ids}

HTTP 400Whole request failureLink ↗

No incoming message IDs were provided.

Provide incoming message IDs in the /rest/incoming/{ids} path.

GET /rest/incoming/{ids}DELETE /rest/incoming/{ids}

Problem type identifier

Problem type URI and documentation URL

https://api.szybkisms.pl/problems/missing-request-parameter/

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.