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

# team.credential.create

> Creates a new API credential for the authenticated user's team. The `clientSecret` is returned **only once** in this response — store it immediately in a secrets manager.

<sup>Questions or issues? Contact us at [api-support@manus.ai](mailto:api-support@manus.ai).</sup>

<Tip>
  **Auth:** Browser session token (Bearer). See [Quickstart Step 1](/enterprise/v1/user-management-quickstart#step-1-%E2%80%94-create-an-api-credential) 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](/enterprise/v1/team.credential.delete) 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](/enterprise/v2/authentication).
</Tip>


## OpenAPI

````yaml POST /team.v1.TeamManagementService/CreateApiCredential
openapi: 3.1.0
info:
  title: Manus Team User Management OpenAPI v1
  description: >-
    API for enterprise tenant administrators to manage team members
    programmatically (SailPoint, Okta, custom IDP integrations). Two surfaces:
    (1) credential management RPCs at `/team.v1.TeamManagementService/*` use a
    session token; (2) REST endpoints under `/api/user/manage/v1/*` use an OAuth
    2.0 Client Credentials access token issued by the credentials. v2 of this
    API ([User Management v2](/enterprise/v2/user-management-overview))
    consolidates everything behind `X-API-Key` — prefer it for new integrations.
  version: 1.0.0
servers:
  - url: https://api.manus.im
security: []
paths:
  /team.v1.TeamManagementService/CreateApiCredential:
    post:
      summary: CreateApiCredential
      description: >-
        Creates a new API credential for the authenticated user's team. The
        `clientSecret` is returned **only once** in this response — store it
        immediately in a secrets manager.
      operationId: team.v1.TeamManagementService.CreateApiCredential
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - name
              properties:
                name:
                  type: string
                  description: >-
                    Human-readable label for the credential. Surfaced in the
                    credential list and audit logs.
                  example: SailPoint Production
      responses:
        '200':
          description: Credential created successfully.
          content:
            application/json:
              schema:
                type: object
                properties:
                  clientId:
                    type: string
                    description: Client identifier. Always prefixed with `tm_`.
                    example: tm_RRa7dgjD_AFhru6AnZJ8W
                  clientSecret:
                    type: string
                    description: >-
                      Client secret. Returned **only** in this response — it
                      cannot be retrieved later.
                    example: >-
                      a1b2c3d4e5f6789012345678901234567890abcdef1234567890abcdef123456
      security:
        - BearerSessionAuth: []
components:
  securitySchemes:
    BearerSessionAuth:
      type: http
      scheme: bearer
      description: >-
        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.

````