---
title: "Authentication"
slug: "sr-authentication"
description: "Learn how to generate authentication tokens for Knovvu Cloud SR using client credentials via the LDM endpoint, with sample cURL request and response."
tags: ["Cloud "]
updated: 2026-04-15T07:25:37Z
published: 2026-04-15T07:25:37Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.knovvu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

## **Token Generation for SESTEK Cloud SR Service**

SESTEK Cloud **Speech Recognition (SR) service** utilizes **bearer tokens** for authentication and authorization. These tokens are required to securely access API endpoints.

When your subscription is created, a **Client ID** and **Client Secret** are generated from the **License Distribution Manager (LDM)** and sent to you. Use these credentials to generate tokens as described below.

---

## **Authentication Endpoint**

To obtain an authentication token, send a request to the following endpoint:

🔗 **Endpoint:**

```
https://identity.ldm.knovvu.com/connect/token
```

---

## **Token Request Process**

| **REST Service Client Actions** | **REST Service Actions** |
| --- | --- |
| **POST** Get Integration Token (LDM endpoint) | Generates a bearer token for authentication. |
| **Required Parameters (Body):** | `client_id`, `client_secret`, `grant_type=client_credentials`, `scope=Ldm_Integration` |
| **Business Rules:** | Subscription must be valid. |

---

## **Example Token Request (cURL)**

Below is an example of a **cURL request** to generate an authentication token:

```
curl --location 'https://identity.ldm.knovvu.com/connect/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=[your_client_id]' \
--data-urlencode 'client_secret=[your_client_secret]' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'scope=Ldm_Integration'
```

---

## **Example Token Response**

Upon a successful request, the API will return a response similar to the following:

```
{
    "access_token": "[your_token]",
    "expires_in": 31536000,
    "token_type": "Bearer",
    "scope": "Ldm_Integration"
}
```

---

## **Token Validity & Expiry**

📌 **LDM tokens are valid for one year (365 days) from the moment of generation.**

- Once generated, the **same token** can be used for API requests until it expires.
- After one year, the token **must be renewed** by generating a new one using the same process.
- It is recommended to **automate the renewal process** before expiration to avoid service disruptions.