Skip to main content
POST
/
team.v1.TeamManagementService
/
CreateApiCredential
CreateApiCredential
curl --request POST \
  --url https://api.manus.im/team.v1.TeamManagementService/CreateApiCredential \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "SailPoint Production"
}
'
{
  "clientId": "tm_RRa7dgjD_AFhru6AnZJ8W",
  "clientSecret": "a1b2c3d4e5f6789012345678901234567890abcdef1234567890abcdef123456"
}
Questions or issues? Contact us at api-support@manus.ai.
Auth: Browser session token (Bearer). See Quickstart Step 1 for how to extract it from DevTools.clientSecret is only returned once — store it in a secrets manager immediately. There is no way to retrieve it later; if you lose it, delete the credential and create a new one.Naming: Use a label that identifies the consumer (e.g. “SailPoint Production”, “Okta Sandbox”) — it appears in audit logs and the credential list.v2 alternative: v2 issues credentials as standard enterprise API keys via the Compliance API settings UI, without the DevTools step. See v2 Authentication.

Authorizations

​
Authorization
string
header
required

Browser session token. Open Manus, find any authenticated request in DevTools → Network, and copy the value after Bearer from the Authorization header. Used only for credential management RPCs.

Body

application/json
​
name
string
required

Human-readable label for the credential. Surfaced in the credential list and audit logs.

Example:

"SailPoint Production"

Response

200 - application/json

Credential created successfully.

​
clientId
string

Client identifier. Always prefixed with tm_.

Example:

"tm_RRa7dgjD_AFhru6AnZJ8W"

​
clientSecret
string

Client secret. Returned only in this response — it cannot be retrieved later.

Example:

"a1b2c3d4e5f6789012345678901234567890abcdef1234567890abcdef123456"