Authentication failed

Access / unauthorized

The API token is missing or cannot be used to authenticate the request.

HTTP 401

How to resolve the problem

1. Send the current API account token in Authorization: Bearer <token>.
2. Check whether the token has been replaced and whether you are using the correct API account.
3. Retry after updating the credentials. Do not repeatedly submit the same invalid token.

About this problem type

The Bearer scheme name is case-insensitive: bearer and BEARER are also accepted. Keep the token unchanged and send one Authorization header with one token. HTTP 401 includes WWW-Authenticate: Bearer. Different authentication failures can have the same public description. Replacing the token alone does not resolve HTTP 403 permission failures.

Response example

Response headers

HTTP/1.1 401
Content-Type: application/problem+json
Content-Language: en-US
WWW-Authenticate: Bearer

Example API response

{
    "type": "https://api.szybkisms.pl/problems/unauthorized/",
    "status": 401,
    "title": "Unauthorized",
    "detail": "Authorization token is missing or invalid.",
    "code": "401-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

Filter messages and causesClear1 situations

HTTP 401Whole request failureLink ↗

Authorization token is missing or invalid.

Send the current token for the correct API account in one Authorization: Bearer <token> header, without extra prefixes or a list of tokens.

Authenticated REST endpointsAny REST endpoint

Problem type identifier

Problem type URI and documentation URL

https://api.szybkisms.pl/problems/unauthorized/

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.