Skip to content

Password flow ​

The OAuth 2.0 Resource Owner Password Credentials Grant (RFC 6749 §4.3), grant_type: password, exchanges a Salaxy username and password for an access token.

Development only

Enabled in the test environments only. It can be used in production only after manual registration — contact Salaxy. For production integrations, use the impersonation flow.

Examples use test-* hosts — see Environments for demo and production.

Request ​

POST /oauth2/token

ParameterDescription
grant_typepassword
usernameYour Salaxy account username
passwordYour Salaxy account password
http
POST https://test-secure.salaxy.com/oauth2/token
Content-Type: application/json

{
  "grant_type": "password",
  "username": "john.doe@example.com",
  "password": "MySecurePassword"
}

Response ​

json
{
  "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "token_type": "bearer"
}

Send the access_token as a Bearer token on each API call — see Tokens. The response has no expires_in: the token lasts 48 hours.

A wrong username or password returns HTTP 400:

json
{ "error": "access_denied", "error_description": "Incorrect username or password." }

A runnable version, where you type your test account's email and password: API authentication on the current site.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.