Skip to main content

Endpoint

Authentication

Requires a Personal API Access Token.

Request

Headers

Path Parameters

Request Body

Full JSON Body Example - Basic Credential

Full JSON Body Example - Credential with IP Restrictions

Full JSON Body Example - Credential with Expiration Date

Full JSON Body Example - Disabled Credential

Request Body Fields

Notes

  • username must be unique across all credentials
  • password must not be empty
  • email must be a valid email address format
  • fullName must not be empty
  • roleNameList must contain valid role names that exist in the system
  • ipList can contain individual IP addresses (e.g., “192.168.1.100”) or CIDR ranges (e.g., “10.0.0.0/8”)
  • expireDate is in ISO 8601 format (UTC). Use null for no expiration
  • enabled defaults to true if not specified
  • Credential is automatically deployed to all environments in the project

Response

Success Response (200 OK)

Response Fields

Deployment Result Object

Environment Result Object

Error Response (400 Bad Request)

or
or
or
or

Common Causes

  • Missing required fields (username, password, fullName, email)
  • Username already exists
  • Invalid email format
  • Invalid role names in roleNameList
  • Invalid date format for expireDate

Error Response (401 Unauthorized)

Error Response (404 Not Found)

cURL Example

Example 1: Create Basic Credential

Example 2: Create Credential with IP Restrictions

Example 3: Create Credential with Expiration

Notes and Warnings

  • Username Uniqueness:
    • Username must be unique across all credentials
    • If username already exists, creation will fail
  • Password Requirements:
    • Password must not be empty
    • Use strong passwords for security
    • Passwords are stored securely (hashed)
  • Email Validation:
    • Email must be provided and not empty
    • Email format should be valid
  • Full Name:
    • Full name must be provided and not empty
    • Used for identification purposes
  • Role Names:
    • Role names must exist in the system
    • Invalid role names will cause validation errors
    • Empty role list is allowed (no roles assigned)
  • IP Restrictions:
    • IP list can contain individual IPs or CIDR ranges
    • Empty IP list means no IP restrictions
    • Invalid IP formats may cause errors
  • Expiration Date:
    • Use ISO 8601 format (UTC): “YYYY-MM-DDTHH:mm:ss.sssZ”
    • Use null for no expiration
    • Expired credentials cannot be used for authentication
  • Enabled Status:
    • Defaults to true if not specified
    • Disabled credentials cannot be used for authentication
  • Automatic Deployment:
    • Credential is automatically deployed to all environments
    • Deployment results are returned in the response
    • Failed deployments are included in environmentResults

Permissions

  • User must have IDENTITY + MANAGE permission in the project
  • For automatic deployment, user must also have IDENTITY + DEPLOY_UNDEPLOY permission