Home
Home
  1. πŸ“‘ Endpoints
  • πŸš€ Getting Started
  • πŸ”Ž Screening API
    • Overview
    • Blacklist Matching Logic
    • πŸ“‘ Endpoints
      • Blockchain Analysis
      • Individuals Analysis
      • Organizations Analysis
      • Screening Entities Summary Analysis
      • Create BlackList
      • Get All BlackList Records
      • Get Blacklist Record by ID
      • Delete Blacklist Record by ID
      • Update Blacklist Record by ID
      • Update Blacklist Settings Account
  • 🌊 Flow API
    • Overview
    • Flow Step: Identity Verification
    • Flow Step: Onboarding Individual
    • Flow Step: Onboarding Organization
    • πŸ“‘ Endpoints
      • Authentication token
        POST
      • Get Flow Instances
        GET
      • Get Flow Instance By Id
        GET
      • Get File from Flow Instance
        GET
      • Identity: Get Details
        GET
      • Identity: Get Files
        GET
      • Identity: Update Status
        PUT
      • Onboarding: Get Details
        GET
      • Onboarding: Get File
        GET
      • Onboarding: Get Multiple Files
        GET
      • Onboarding: Update Status
        PUT
      • Onboarding: Get Entity by document number
        GET
      • Onboarding: Get Entity List by document number
        GET
    • πŸ“€ Webhooks
      • Overview
      • Flow
      • Identity Verification
      • Onboarding Individual
      • Onboarding Organizations
      • Identity Verification by Onboarding
  • πŸ’ΈTransaction Screening API
    • πŸ”‘ Authentication
    • Overview
    • Transaction Analysis
    • Monitoring & History
    • Document Types
    • Supported Currencies
    • Diagram
    • πŸ“€ Webhooks
    • πŸ“‘ Endpoints
      • Submit Transaction
      • List Transactions
      • List Document types
      • List Cryptocurrencies
      • Register remitter
      • Register Beneficiary
  • πŸ“‚ Resources
    • Concept Details
    • Enum Validation
Home
Home
  1. πŸ“‘ Endpoints

Authentication token

POST
https://verification-id.rillis.io/api/v1/auth/token
This endpoint generates an access token that is required to authenticate all subsequent API requests in the Flow API.
You must provide your clientId and clientSecret in the request body to receive a valid access_token.
Once you obtain the access_token, you must include it in the Authorization header as a Bearer Token when making API requests to other endpoints.

Request

Body Params application/json

Examples

Responses

🟒200OK
application/json
Body

🟠401Unauthorized
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://verification-id.rillis.io/api/v1/auth/token' \
--header 'Content-Type: application/json' \
--data-raw '{
  "clientId": "string",
  "clientSecret": "string"
}'
Response Response Example
200 - Success
{
  "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY0MjA0ZGQ3NTkyOTBhOTQwM2ZlZjQ0ZSIsImVtYWlsIjoiY2xpZW50QGdtYWlsLmNvbSIsInJvbGVzIjpbImNsaWVudCJdLCJpc19hY3RpdmUiOnRydWUsImVtYWlsX3ZlcmlmaWVkX2F0IjoiMjAyMy0wMy0yNlQxMzo0ODo1Ni4xMDJaIiwic2NvcGUiOiJBUEkiLCJpYXQiOjE3NDQyMzE0MDksImV4cCI6MTc0NDI0NTgwOX0.jvOkQw9XhDhRhrz9SfAZAjO4ye_d0V26ni8wx-xlk9A3PHMEdmlF31VUYJXmTV8kal8dq81xKaT5gt6DTcCjb4GvrwZ8zA-eRUFRAyAGcq-CG6cB9AMtYbbRXi2YbK0I-4zweHu1amN0by8BtoOvZMt0BNKwHNqGyg6umSUE3sA0MFhtMJeeY5x6Up6rJLs6b3gXh987tPZ610ZhVvdDtDeeWCkb2TV2mW6-vYzPmgQSe85in--QyCKauZ10AvCpCha2L567SaddBavtJ_5KsQs8RQ4P07oeoXEN2ypk_jKAiQJCmw53Cxwe-D0L-fZ6l-R528aWdIY1EKG3LY9JveGiXnBGMHEn4G1DtFwpl8-W-qyItfAClr4zEBQHUfbQVwzXqr3MwEN5M6AHzJ3Qp4ZrjxP165J08kD1Ncsm7BUxKKuOIQTTxDyIyKni8iJp7L2KswQ_jpwl8P2IfJUf5HFI1sKyhCQ2DJ-_qHNYv-xMEvuyLvxZ5AwO4aa9Ubb321xHq096Yq6ZGjtFkvDv546W-oo5FtpODC6b2MFjpl3S_3biNEjRzY6mf3Ocd40FcY3wJ1xSJmmqeo6WmNNA9YnIJbRwWTburtX-lVhw1D_Pj_6QAX3btEWUNyzGi2xyhRm7f2IMS62mqFhaSbfZxijZzVnwAAsTX3MaYrEXljs"
}
Modified atΒ 2026-02-03 19:22:50
Previous
Flow Step: Onboarding Organization
Next
Get Flow Instances
Built with