Invalid parameter format

Request / invalid-request-parameter-format

The ID list contains a value that is not a numeric message ID.

HTTP 400

How to resolve the problem

1. Use numeric IDs returned by the API.
2. A valid list looks like /messages/123,456. Do not add spaces or a trailing comma.
3. Check path encoding and remove empty entries from the list.

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/invalid-request-parameter-format/",
    "status": 400,
    "title": "Invalid Request Parameter Format",
    "detail": "Outgoing message IDs must be numbers separated by commas.",
    "code": "400-4",
    "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 ↗

Outgoing message IDs must be numbers separated by commas.

Use a comma-separated list of numeric outgoing message IDs.

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

HTTP 400Whole request failureLink ↗

Incoming message IDs must be numbers separated by commas.

Use comma-separated numeric incoming message IDs without spaces or empty entries.

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

Problem type identifier

Problem type URI and documentation URL

https://api.szybkisms.pl/problems/invalid-request-parameter-format/

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.