Prepare a Short URL consent form using your IYS Panel. Once the form is ready, submit it to IYS for approval.
2
Obtain IYS Approval
After IYS approves the form, it will be available for use in API calls. The form ID provided by IYS will serve as the formId value in your requests.
3
Send the Consent Form to the User
Send the consent form link to your users via email or SMS. Use the API endpoint https://restapi.netmera.com/via/consent to share the link with your users.
4
User Submits Their Consent
When the user receives the link, they can open the form, select their SMS or email permissions, and submit their approval.
5
Confirmation Information Sent to the User
After the user submits their consent, they will receive a confirmation via email or SMS informing them of the permissions they selected and their submission status.
6
Consent Data Saved in Netmera
Netmera saves the user permissions in the Netmera Panel. This synchronization occurs every 10 minutes to ensure the latest user preferences are reflected.
Consent Requests with Short URL
1
Start Consent Process
The consent method initiates the process of obtaining ETK (Electronic Communication Permission) and/or KVKK (Personal Data Protection Law) consent. A short URL linking to a webpage where recipients can complete the approval process, along with an explanation text, is sent to the recipient. The method returns a requestId value as a response.
2
Access Consent Form
The recipient clicks on the short URL, which redirects them to a webpage where they can provide their ETK and/or KVKK consent.
3
Consent Given
Once the recipient provides consent:
ETK consent is recorded on behalf of the brand(s).
KVKK consent is recorded on behalf of the service provider.
4
Netmera Consent Update
After consent is received, recipient's ETK consent (EMAIL/SMS notification preferences) is saved in the Netmera system in every 10 minutes.
ETK Short URL Parameters
Below are the required parameters for requesting ETK using short URL verification methods, either through SMS or email.
Fields in the Request Body
Field
Type
Description
Required
Notes
consentTypes
Array of Objects
Details of the consent request.
Yes
Each object must include title, types, and recipientType.
title
String
The type of consent being requested.
Yes
Example value: "ETK"
types
Array of Strings
Communication channels for which consent is being requested.
Yes
Possible values: ["ARAMA"], ["MESAJ"], ["ARAMA", "MESAJ"], ["MESAJ", "ARAMA"], ["EPOSTA"].
{
"message": "verificationType alanı için gereken değerler: [SMS_OTP, EPOSTA_OTP, SMS_SHORTURL, EPOSTA_SHORTURL, SMS_APPROVALURL, EPOSTA_APPROVALURL, SMS_CEVAP, SMS_RED, URL_RED] olmalıdır.",
"code": "H1012",
"value": "EPOSTA_SHORTLINK"
}
KVK Short URL Parameters
Below are the required parameters for requesting KVK using short URL verification methods, either through SMS or email.
Fields in the Request Body
Field Name
Type
Required
Description
consentTypes
Array of Objects
Yes
Contains details about the type of consent requested.
title
String
Yes
Type of form sent to the recipient. For KVK consent, this field must be set as "KVK".
types
Array of Strings
Yes
Consent types for KVK. Possible values: "AYDINLATMA_METNI", "ACIK_RIZA_METNI", "YURTDISI_AKTARIM".
formId
String
Yes
ID of the form sent to the recipient. The corresponding consent form will be sent to the recipient based on this ID. Obtainable via the İYS Web.
verificationType
String
Yes
Method of obtaining consent via ViA. Use "SMS_SHORTURL" for SMS-based short link verification or "EPOSTA_SHORTURL" for email-based short link verification.
recipient
String
Yes
Contact information of the recipient. Either a phone number or email address where the consent request will be sent.
referenceID
String
Yes
Identifies the users in Netmera system. This identifier is used to create or update user records for VIA.
personData
Object
Yes (personal data)
Contains recipient details if KVK consent requires personal information.
name
String
Yes (personal data)
Recipient's full name.
recipientIdNumber
String
Yes (personal data)
Recipient's Turkish ID number.
address
String
Yes (personal data)
Recipient's address information.
Additional Information
Fields in personData (e.g., name, recipientIdNumber, and address) become mandatory if required by the KVK process.
The formId uniquely identifies the consent form and ensures it is correctly delivered to the recipient.
In case of a failed request, the response will include the following fields:
message (String): The error message that describes the issue with the request.
code (String): The error code from the IYS system indicating the specific issue.
value (String) (This field may return the invalid value depending on the type of error, or it may be omitted): The invalid value that caused the error.
Invalid SMS Short URL Request
Case: verificationType is set to SMS_SHORTURL but the types array contains an EPOSTA value, which is incompatible with SMS verification.
In case of a failed request, the response will include the following fields:
message (String): The error message that describes the issue with the request.
code (String): The error code from the IYS system indicating the specific issue.
value (String) (This field may return the invalid value depending on the type of error, or it may be omitted): The invalid value that caused the error.
Invalid ETK & KVK SMS Short URL Request
Case: The recipient field is provided in an invalid format when verificationType is SMS_SHORTURL.