Sender already exists

Resources / already-exists

The sender name is already assigned to the account or matches a system sender.

HTTP 409

How to resolve the problem

1. Retrieve GET /rest/senders and use an existing sender.
2. Do not register the same name or a system sender again.
3. If you need another sender name, choose a different name and describe its intended use.

Response example

Response headers

HTTP/1.1 409
Content-Type: application/problem+json
Content-Language: en-US

Example API response

{
    "type": "https://api.szybkisms.pl/problems/already-exists/",
    "status": 409,
    "title": "Already Exists",
    "detail": "The sender name is already defined on your account.",
    "code": "409-1",
    "instance": "/rest/senders"
}

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 409Whole request failureLink ↗

The sender name is already defined on your account.

Use an existing sender or choose a different name.

POST /rest/senders

Problem type identifier

Problem type URI and documentation URL

https://api.szybkisms.pl/problems/already-exists/

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.