POST
/
oauth2
/
{auth}
/
v1
/
token
Request Access Token
curl --request POST \
  --url https://identity.lucidworks.com/oauth2/{auth}/v1/token \
  --header 'Accept: <accept>' \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Cache-Control: <cache-control>' \
  --header 'Content-Type: <content-type>'
{
  "token_type": "Bearer",
  "expires_in": 3600,
  "access_token": "eyJraW...",
  "scope": "machinelearning.predict"
}

Authorizations

​
Authorization
string
header
required

The Authentication API is used by multiple Lucidworks products such as Lucidworks AI. The scope value in the request is unique to the product accessing the API.

The Client ID is used for the Username value, and the Client Secret is used for the Password value.

How do I regenerate my client secret?

Contact support if you need to regenerate your client secret.

Headers

​
Cache-Control
enum<string>
required

The no-cache request directive asks caches to validate the response with the origin server before reuse.

Available options:
no-cache
​
Accept
enum<string>
required

The Accept request HTTP header indicates which content types the client can understand.

Available options:
application/json
​
Content-Type
enum<string>
required

The Content-Type header indicates the original media type of the resource.

Available options:
application/x-www-form-urlencoded

Path Parameters

​
auth
enum<string>
required

The authorization code used to generate an access token.

Available options:
ausao8uveaPmyhv0v357

Query Parameters

​
scope
enum<string>
required

The value defines the scope of access requested. For the token used by the Lucidworks AI API usecase, prediction, async-prediction, and async-chunking endpoints, use "scope": "machinelearning.predict". For the token used by the Lucidworks AI API model endpoint, use "scope": "machinelearning.model".

Available options:
machinelearning.predict,
machinelearning.model
​
grant_type
enum<string>
required

The client_credentials grant type is used by clients to obtain an access token in the context of the client itself, not the user.

Available options:
client_credentials

Response

200
application/json

OK

The token response object, which contains the ACCESS_TOKEN required by operation APIs.