FAST LOGIN API

Additional Web Services on Service Provider Side

Web Services in this section are implemented by Service Providers in the case of Service Provider should know customer consents' change and e-mail verification.

Verified Email Web Service

  • Turkcell Fast Login platform will notify the related Service Provider when customer verifies the email address.
  • Service Provider should implement this service if the Service Provider asks users for emails. In other words the Service Provider uses "email" scope.
  • Service Provider should provide a listener web service to get customer email verification event.
Request Parameters:
Parameter Description
*requestHeader Details given in further
Type: Header (Complex type)
*clientId Service Provider's clientId is used in authentication and token end-points
Type: String
*sub PCR (Pseudo Customer Reference), customer unique id
Type: String
*email Type: String
Request Header Parameters:
Parameter Description
*transactionID Unique identifier of the transaction
Type: String
*Application Application making the request
Type: String
*userId User initiating the transaction
Type: String
*operationName Operation or the transaction for which the transaction is initiated
Type: String
*transactionDate Date of transaction (Day, month, year, hour, min, sec)
Format: YYYY-MM-DD HH24:MI:SS
Type: String
Response Parameters:
Parameter Description
*returnCode 0: SUCCESS
others FAIL
Type: Integer

Consent Management Web Service

  • User can take back for attribute sharing consents and after that time Service Provider must remove consent from its own system.
  • Also, user can give consent as well and Service Provider should implement the same procedure.
Request Parameters:
Parameter Description
*requestHeader Details given in further
Type: Header (Complex type)
*clientId Service Provider's clientId is used in authentication and token end-points
Type: String
*sub PCR (Pseudo Customer Reference), customer unique id
Type: String
*attribute Array of scopes (profile, email, phone)
Type: Array
*consentType 0: cancel consent
1: give consent
Type: Integer
Request Header Parameters:
Parameter Description
*transactionID Unique identifier of the transaction
Type: String
*Application Application making the request
Type: String
*userId User initiating the transaction
Type: String
*operationName Operation or the transaction for which the transaction is initiated
Type: String
*transactionDate Date of transaction (Day, month, year, hour, min, sec)
Format: YYYY-MM-DD HH24:MI:SS
Type: String
Response Parameters:
Parameter Description
*returnCode 0: SUCCESS
others FAIL
Type: Integer