Skip to content
SzybkiSMSSzybkiSMSSzybkiSMS · REST API problems

Resource not found

Resources / not-found

The endpoint, message, page or sender is not available for this account.

HTTP 404

How to resolve the problem

Section titled “How to resolve the problem”
  1. Check the endpoint and environment: /rest and /rest-sandbox have separate data.
  2. Use IDs belonging to the current account and accessible to the user associated with the token.
  3. For collections, check the page number. An empty collection returns HTTP 200 with an empty array; a page outside a nonempty collection returns HTTP 404.

Response example

Section titled “Response example”
Response headers
HTTP/1.1 404
Content-Type: application/problem+json
Content-Language: en-US
Example API response
{
    "type": "https://api.szybkisms.pl/problems/not-found/",
    "status": 404,
    "title": "Not Found",
    "detail": "The requested endpoint was not found.",
    "code": "404-1",
    "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”
9 situations
HTTP 404Whole request failureLink ↗

The requested endpoint was not found.

Check the endpoint URL and the /rest or /rest-sandbox prefix.

Any REST endpoint
HTTP 404Whole request failureLink ↗

No subaccount was found with the provided user_login.

Check user_login and whether the user belongs to the current account.

GET /rest/accountGET /rest/account/{user_login}
HTTP 404Whole request failureLink ↗

The requested page was not found in your outgoing message history.

Choose an existing page of outgoing message history.

GET /rest/messagesGET /rest/messages/{ids}
HTTP 404Whole request failureLink ↗

No outgoing messages were found with the provided IDs.

Check the environment and the outgoing message IDs available to the account.

DELETE /rest/messages/{ids}GET /rest/messages/{ids}
HTTP 404Whole request failureLink ↗

The requested page was not found in your incoming message inbox.

Choose an existing page of the incoming message inbox.

GET /rest/incomingGET /rest/incoming/{ids}
HTTP 404Whole request failureLink ↗

No incoming messages were found with the provided IDs.

Check the incoming message IDs and their availability to the account.

GET /rest/incoming/{ids}DELETE /rest/incoming/{ids}
HTTP 404Whole request failureLink ↗

The sender name is not defined on your account.

Retrieve GET /rest/senders and choose a sender name assigned to the account.

DELETE /rest/senders/{sender}PATCH /rest/senders/{sender}
Item status 404Batch item · HTTP 200Link ↗

No incoming message was found with the provided ID.

Check the ID of the incoming message to delete.

DELETE /rest/incoming/{ids}
Item status 404Batch item · HTTP 200Link ↗

No outgoing message was found with the provided ID.

Check the outgoing message ID and its availability to the account before cancellation.

DELETE /rest/messages/{ids}

Problem type identifier

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

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.