Skip to main content
POST
/
admin
/
api
/
v1
/
Token
Generate Auth token
curl --request POST \
  --url https://admin-api.meshconnect.com/admin/api/v1/Token \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "clientId": "<api-key>",
  "clientSecret": "<api-key>"
}
'
{
  "content": {
    "id_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.KMUFsIDTnFmyG3nMiGM6H9FNFUROf3wh7SmqJp-QV30",
    "expires_in": 3600,
    "status": "available"
  },
  "status": "ok",
  "message": "",
  "errorHash": "e47df370",
  "teamCode": "P4",
  "errorType": ""
}

Authorizations

​
Authorization
string
header
required

Authorization header using the Bearer scheme. Example: "Authorization: Bearer {Value}"

Body

Generate Auth token.

​
clientId
string
required

Contact Mesh to get client Id.

Minimum string length: 1
​
clientSecret
string
required

Contact Mesh to get Client Secret for Account Management API.

Minimum string length: 1

Response

Token created

​
status
enum<string>
Available options:
ok,
serverFailure,
permissionDenied,
badRequest,
notFound,
conflict,
tooManyRequest,
locked,
unavailableForLegalReasons
​
message
string | null

A message generated by the API

​
displayMessage
string | null

User-friendly display message that can be presented to the end user

​
errorHash
string | null

An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping

​
teamCode
string | null

Opaque team code for error routing. Resolved from exception origin or caller file path via CODEOWNERS. Format: 2-character code (e.g., "7K", "M2"). Use for alerting/routing, not display.

​
errorType
string | null

Strictly-typed error type that is explaining the reason of an unsuccessful status of the operation. All possible error types are available in the documentation.

​
errorData
unknown
​
content
object