Skip to main content

JSON Post API

To add a mobile phone number that you do not want to receive SMS to your blocked number list, send it to the server in JSON format using the HTTP POST method. Follow the instructions below.

İstek yapılacak adres​

POSThttps://api.iletimerkezi.com/v1/consent/create/json

Request Body​

{
  "request": {
    "authentication": {
      "key": "",
      "hash": ""
    },
    "consent": {
      "brandCode": 696422,
      "list": [
        {
          "recipient": "+90505xxxxxxx veya [email protected]",
          "recipientType": "BIREYSEL",
          "source": "HS_EORTAM",
          "status": "ONAY",
          "type": "MESAJ",
          "consentDate": "2026-01-07 23:50:00"
        }
      ]
    }
  }
}

Definitions​

The request sent to the server must be wrapped in the request tag. Definitions for its child tags are as follows:

authentication​

Contains information about the transaction status. The values ​​returned with this tag can also be obtained by looking at the header information of the HTTP response. This tag is returned as standard in every request made. Its subtags are as follows

  • key: After logging into your iletimerkezi.com panel, the API Key that you can create from the settings section should be written in this field. It is mandatory to send it when making a request.

  • hash: After logging into your iletimerkezi.com panel, the hash created using the API Key and Secret Key, which you can create from the settings section, should be written in this field. It is mandatory to send it when making a request.

Tag that contains the consent information to be sent to IYS (the Consent Management System).

  • brandCode: The code of the brand to which the consent information will be transmitted.

  • list: Tag containing consent entries. Multiple consent entries can be sent inside the list tag.

    list​

    • recipient: The phone number or email address for which the consent will be transmitted.
    • recipientType: The type of recipient. Can be BIREYSEL or TACIR.
    • source: The source where the consent information was obtained (e.g., HS_EORTAM, HS_FIZIKSEL_ORTAM, etc.).
      SourceDescription
      HS_KARARThe consent status has been set to RET at the service provider's discretion. The service provider cannot use HS_KARAR as the source value when adding the initial consent.
      HS_FIZIKSEL_ORTAMThe consent was obtained in a physical environment by the service provider.
      HS_ISLAK_IMZAThe consent was obtained when the recipient signed a form or survey.
      HS_ETKINLIKThe consent was obtained at an event organized by the service provider.
      HS_ATMThe consent was obtained via an on-site ATM device belonging to the service provider.
      HS_EORTAMThe consent was obtained in an electronic environment belonging to the service provider.
      HS_WEBThe consent was obtained through an action on the service provider's website.
      HS_MOBILThe consent was obtained via the service provider's mobile application.
      HS_MESAJThe consent was obtained via the service provider's short message number.
      HS_EPOSTAThe consent was obtained via the service provider's email.
      HS_CAGRI_MERKEZIThe consent was obtained at a call center associated with the service provider, either by voice or keypad input.
      HS_SOSYAL_MEDYAThe consent was obtained through the service provider's social media channel.
    • status: Consent status. Can be ONAY or RET.
    • type: Consent type. Can be MESAJ, EPOSTA, or ARAMA.
    • consentDate: The date and time when the consent or rejection occurred. Format: YYYY-MM-DD HH:MM:SS, and it cannot be older than 3 days.

Server Response​

{
  "response": {
    "status": {
      "code": 200,
      "message": "İşlem başarılı"
    }
  }
}

Definitions​

The server response is always wrapped in the response tag. Definitions for its child tags are as follows:

status​

Contains information about the transaction status. The values ​​returned with this tag can also be obtained by looking at the header information of the HTTP response. This tag is returned as standard in every request made. Its subtags are as follows

  • code: It is a numeric value indicating the process status.
  • message: Contains information message about the process status.

Error Codes​

The following table lists the error codes that the API can return.

Error CodeMessageDescription
400İstek çözümlenemediPOST ettiğiniz JSON'in yapısındaki hatadan kaynaklanır. Bu hatalar genellikle, yanlış yazılan JSON etiketi, düzgün kapatılmayan XML etiketi veya CDATA kullanılmadan JSON'in yapısını bozabilecek bir karakterin kullanımından kaynaklanır.
401Üyelik bilgileri hatalıPOST ettiğiniz JSON'in authentication etiketi içerisinde göndermiş olduğunuz bilgileri doğrulayamadığımızda bu hatayı veriyoruz, eğer hesabınızda sabit IP tanımladıysanız ve farklı bir IP üzerinden istek yapıyorsanız yine bu hatayı alırsınız.
403Aktif abonelik bulunamadı.Eğer hesabınızda aktif bir abonelik yoksa bu hatayı alırsınız.
404API istek yapılan yönteme sahip değilEğer bu hatayı alıyorsanız istek yaptığınız adresi tekrar kontrol edin yanlış bir adrese istek yapıyor olabilirsiniz.
405Bu işlemi yapmak için, abonelik paketinizde yeterli kota bulunmamaktadır.Abonelik paketinizin limitini aştığınızda bu hata döner.
422İstekte gönderilen bazı değerler doğrulanamadı.Yapmış olduğunuz isteğin içeriğinde doğrulamadan geçemeyen değerler içerdiğini belirtir. İsteğin içeriğini (body) ve gönderilen değerleri tekrar kontrol etmenizi öneririz.
475Alıcı sayısı 5000 kişiyi geçemez.Tek bir istekte en fazla 5000 alıcıya işlem yapabilirsiniz.