The Credential object represents a set of SIP authentication credentials (username and password) that can be used to authenticate calls on a specific trunk. Multiple credentials can exist for a single trunk, enabling different users, devices, or applications to connect with unique authentication details.Documentation Index
Fetch the complete documentation index at: https://docs.vobiz.ai/llms.txt
Use this file to discover all available pages before exploring further.
Password Security: The
password field is write-only and is never returned in API responses. Once created, passwords cannot be retrieved - only updated.Username Immutability: The username cannot be changed after credential creation. To use a different username, create a new credential and delete the old one.Attributes
| Field | Type | Description |
|---|---|---|
id | string (UUID) | Unique identifier for the credential. Automatically generated upon creation. |
trunk_id | string (UUID) | ID of the trunk this credential belongs to. |
username | string | SIP username for authentication. Required. Must be unique within the trunk. Cannot be changed after creation. |
password | string | SIP password for authentication. Required (minimum 8 characters). Write-only - never returned in responses. |
enabled | boolean | Whether the credential is active and can be used for authentication. Default: true. |
description | string | Optional description with context about the credential’s purpose or the device/user it belongs to. |
created_at | string (ISO 8601) | Timestamp when the credential was created. Format: YYYY-MM-DDTHH:mm:ssZ (UTC). |
updated_at | string (ISO 8601) | Timestamp of the last update to the credential. Format: YYYY-MM-DDTHH:mm:ssZ (UTC). |
Example
Credential Object Response
A typical credential object returned by the API (password is not included):Credential Object
Security Best Practices:
- Use strong passwords with at least 12 characters
- Include uppercase, lowercase, numbers, and special characters
- Rotate credentials regularly (quarterly recommended)
- Disable unused credentials immediately rather than deleting them
- Use descriptive usernames that identify the device or user