The expanded Passportal API is now available across all production environments.

This provides additional routes for:

• Passwords
• Folders
• Credential types
• Creating and refreshing Service Account Tokens

The password routes support operations such as creating and updating passwords. Credential types provide required information for these operations, while folder routes give integrations access to the related folder resources.

More granular control with Service Account Tokens

Service Account Tokens are the recommended authentication option for new integrations.

Compared with the legacy client_token, Service Account Tokens provide more granular control over permissions and access levels. This lets customers use a token designed for an integration rather than relying on the legacy authentication model.

Service Account Tokens also provide:

Full API scope: Service Account Tokens accept the everything scope. User Token accept both everything and docs_api scopes.

Dedicated integration credentials: Use an account token intended for API access rather than tying the integration to a user token.

Refresh support: Use the dedicated route to refresh a Service Account Token.

Current documentation: Build against the authentication method covered in the updated Passportal API documentation.

Existing integrations

Existing integrations using the legacy client_token can continue to work. The route remains active and hasn’t been marked as removed or deprecated. No immediate migration is required.

The main benefit of the legacy token is compatibility with existing integrations. For new development, we recommend using a Service Account Token for its dedicated integration credentials and more granular permissions and access controls.

Customers can review the available routes, authentication options, request fields, and response examples in the Passportal developer documentation.