Approved Sender IDs API (get-sender)

The get-sender endpoint returns the list of sender IDs (headers) registered and approved on your account. The order.sender field of send-sms only accepts values from this list; using anything else is rejected. The call has no side effects and consumes no credits.

Prerequisite: enable API access in the panel

Before calling this endpoint, the Allow API access toggle must be on in your iletiMerkezi panel.
Location: panel.iletimerkezi.com → Settings → Security → Access Permissions
If it is off, every request returns 401 — Üyelik bilgileri hatalı ("Authentication failed"). See authentication.md.

Endpoint

| Field | Value | |---|---| | Method | POST | | URL | https://api.iletimerkezi.com/v1/get-sender/json | | Content-Type | application/json | | Auth | API Key + Hash (request.authentication) |

Request

Schema

request
└─ authentication
   ├─ key (string, required)
   └─ hash (string, required)

get-sender takes no extra fields beyond the auth block.

Full example

{
  "request": {
    "authentication": {
      "key": "API_KEY",
      "hash": "API_HASH"
    }
  }
}

Response

Success (200)

{
  "response": {
    "status": {
      "code": 200,
      "message": "İşlem başarılı"
    },
    "senders": {
      "sender": [
        "eMarka Test"
      ]
    }
  }
}

İşlem başarılı means "Request successful" in Turkish.

Fields:

response.senders.sender (string[]): Array of approved sender IDs. Single-sender accounts return a one-element array; multi-sender accounts return more. Each ID is at most 11 characters, alphanumeric (spaces count).

New accounts may receive an empty array. Sender ID applications are submitted from the panel and reviewed by iletiMerkezi within 1-2 business days; once approved, the ID appears here automatically.

Error responses

401 — Üyelik bilgileri hatalı ("Authentication failed")

API Key / Hash invalid, or the panel toggle is off. See authentication.md.

Other error codes

For 400, 404: see error-codes.md.

Code samples

cURL

curl -X POST 'https://api.iletimerkezi.com/v1/get-sender/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "request": {
      "authentication": {
        "key": "'"$ILETIMERKEZI_API_KEY"'",
        "hash": "'"$ILETIMERKEZI_API_HASH"'"
      }
    }
  }'

Common pitfalls

Empty list means approval is pending. New accounts get an empty array ([]). Submit your sender ID application from the panel; iletiMerkezi reviews it within 1-2 business days. While approval is pending, you can pass "APITEST" as the sender in send-sms to test the HTTP flow end-to-end. See test-mode.
Validate the sender at runtime. In production, check that order.sender is in this list before calling send-sms. A bad sender ID floods your error logs in production.
11-character cap. Maximum 11 alphanumeric characters; spaces count (eMarka Test = 11 chars).
The list rarely changes. Approvals are infrequent. You don't need to call get-sender before every send-sms. Cache the list at application start or refresh on a panel-driven event.
Sender ID is case-sensitive. If the panel approved eMarka Test, send eMarka Test exactly; emarka test or EMARKA TEST may be rejected.

Last updated: 2026-04-29 · Türkçe