Missing body data

Request / missing-body-property

The request is missing messages to send or price, or a description of the sender name’s intended use.

HTTP 400

How to resolve the problem

1. For sending and pricing, submit a message object or a nonempty array of message objects.
2. When registering a sender, fill in description with its intended use.
3. Empty arrays and other missing required fields can be rejected earlier by OpenAPI validation.

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-body-property/",
    "status": 400,
    "title": "Missing Body Property",
    "detail": "At least one message is required.",
    "code": "400-2",
    "instance": "/rest/messages/mms"
}

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 ↗

At least one message is required.

Provide at least one message in the request body for sending or pricing.

POST /rest/messages/mmsPOST /rest/messages/smsPOST /rest/messages/mms/pricePOST /rest/messages/sms/price

HTTP 400Whole request failureLink ↗

A description of the intended use of the sender name is required.

Fill in description with the intended use of the sender name.

POST /rest/senders

Problem type identifier

Problem type URI and documentation URL

https://api.szybkisms.pl/problems/missing-body-property/

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.