FACEKI BLAZE 3.0 Documentation
  • Getting Started
  • Older Documentation
  • Quick Guides
    • Image Guidelines
    • Workflow Setup
    • Verification Monitoring
    • API Credentials
    • Webhook Setup
  • Integrations
  • No Integration Option
    • Zero Integration (via a Link)
  • API Integration
    • Verification APIs
      • Authentication
      • Generate KYC Link
      • Perform KYC Verification
      • Fetch Records
      • Face Match API (💲)
      • Fetch PDF Report
  • Data Fields
    • Verification Data
      • EKYC Webhook Structure
    • Error Codes
  • Mobile SDK
    • React Native SDK / Plugin
    • iOS SDK
    • Android SDK
    • Flutter SDK
  • Web SDK
    • React
  • Need Help?
    • Whatsapp
    • Support
    • FAQ's
Powered by GitBook
On this page
  • Token Generation End Point
  1. API Integration
  2. Verification APIs

Authentication

Get an Authroization Bearer Token.

PreviousVerification APIsNextGenerate KYC Link

Last updated 2 months ago

Base URL

sdk.faceki.com

Token Generation End Point

https://sdk.faceki.com/auth/api/generate-token

Authentication for the Faceki API is achieved through token-based authentication. To authenticate requests made to the API, you must include an API token in the Authorization of your requests.

Method: POST

Authorization: Bearer Token

Body:

clientId *(mandatary)

clientSecret *(mandatory)

POST https://sdk.faceki.com/auth/api/access-token

Headers

Name
Type
Description

clientSecret*

String

clientSecret will be found in the integration section.

Example: "clientSecret":"00nl0cuq780ur007spqspa94kq6rkn1fap1e0kdre7gdl97lvspk".

clientId*

String

(string, required) Client Id from integration settings.

Example: "client_id":"0NTS4CBV8MVII02VGVSPICB00".

Content-Type

String

application/json

    "responseCode": 0,
    "data": {
        "access_token": "<Your API Token>",
        "expires_in": 3600,
        "token_type": "Bearer"
    }
}
{
  "status": false,
  "message": "",
  "statusCode": 422,
  "data": {}
}
{
  "clientSecret": ""
}
{
  "status": false,
  "message": "client id is required",
  "statusCode": 422,
  "data": {}
}