> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/updates-and-releases/cerby-api/2026.md).

# 2026

## August 21, 2026

### New features and enhancements

* Integrations
  * [List the unmatched users of an integration asset](https://developer.cerby.com/#list-the-unmatched-users-of-an-integration-asset)
  * [Remove an unmatched user from an integration](https://developer.cerby.com/#remove-an-unmatched-user-from-an-integration)
  * [Remove an unmatched user from an integration asset](https://developer.cerby.com/#remove-an-unmatched-user-from-an-integration-asset)
  * `POST /api/v1/integrations/{id}/users` now returns `409 Conflict` when any user in the request is already a member of the integration. The response identifies the duplicate user IDs. Previously, duplicate invites were silently accepted and created unnecessary automation jobs. If any user in the batch is a duplicate, the entire request is rejected.
  * `PATCH /api/v1/integrations/{id}/users/{userId}/entitlements` now returns a typed `400` error when the user's invite is still pending propagation, preventing automation jobs from being dispatched against an unclaimed grant.
  * `PATCH /api/v1/integrations/{id}/users/{userId}/entitlements` now returns `409 Conflict` when the requested role change nets to no change. Previously, a no-op patch dispatched a full automation job that changed nothing.
  * `POST /api/v1/integrations/{id}/assets/{assetId}/users/{userId}` pending-invite and active-access duplicate grants now both return `409 Conflict`. Previously, a pending-invite conflict returned `400`.
* SCIM
  * SCIM user read responses now include the workspace role field, completing SCIM role parity with the write provisioning added in July.

***

## July 21, 2026

### New features and enhancements

* Integrations
  * `DELETE /api/v1/integrations/{id}/users/{userId}` now returns the deprovisioning job object rather than an empty `204` response, consistent with the provisioning API. Existing clients that check only the HTTP status code are unaffected; clients that read the response body should update to handle the returned job.
  * `PATCH /api/v1/integrations/{id}/users/{userId}`, `PATCH /api/v1/integrations/{id}/users/{userId}/entitlements`, and `DELETE /api/v1/integrations/{id}/users/{userId}` now return typed `403` or `400` errors when the calling user lacks permission, instead of `500 Internal Server Error`.
* SCIM
  * SCIM gateway user records now serialize `created` and `updated` timestamps in ISO 8601 format. Previously, the date format was inconsistent across environments.
  * Workspace role can now be set via SCIM provisioning.

***

## July 8, 2026

### New features and enhancements

* Accounts
  * [Remove a user from an account](https://developer.cerby.com/#remove-a-user-from-an-account)
  * [Remove a team from an account](https://developer.cerby.com/#remove-a-team-from-an-account)
* Secrets
  * [Delete a secret](https://developer.cerby.com/#delete-a-secret)
  * [Remove a user from a secret](https://developer.cerby.com/#remove-a-user-from-a-secret)
* Users
  * [Delete a user](https://developer.cerby.com/#delete-a-user)
  * [Re-enable a guest user](https://developer.cerby.com/#re-enable-a-guest-user)
* Teams
  * [Remove a user from a team](https://developer.cerby.com/#remove-a-member-from-a-team)
  * [Remove an account from a team](https://developer.cerby.com/#remove-an-account-from-a-team)
  * [Remove a secret from a team](https://developer.cerby.com/#remove-a-secret-from-a-team)
  * [Remove a collection from a team](https://developer.cerby.com/#remove-a-collection-from-a-team)
* Integrations
  * [List the users in an integration asset](https://developer.cerby.com/#list-the-users-in-an-integration-asset)
  * [Retrieve a user of an integration asset](https://developer.cerby.com/#retrieve-a-user-of-an-integration-asset)
  * [Add or remove a user's entitlements in an integration asset](https://developer.cerby.com/#add-or-remove-a-users-entitlements-in-an-integration-asset)
  * [Grant a user access to an integration asset](https://developer.cerby.com/#grant-a-user-access-to-an-integration-asset)
  * [Remove a user from an integration asset](https://developer.cerby.com/#remove-a-user-from-an-integration-asset)

### Fixes

* Requests to delete a secret that has already been deleted now return `404 Not Found` instead of a server error.
* Inviting a user to a business hub who already has direct access through an asset is now blocked at the API level, preventing conflicting access states.

***

## June 5, 2026

### New features and enhancements

* The `GET /api/v1/users` endpoint now accepts `filter[status]` (accepted values: `live`, `disabled`, `pending`) and `filter[isGuest]` (`true` or `false`) query parameters. Both filters can be combined with each other and with the existing free-text `filter` parameter. Omitting either filter preserves existing behavior

***

## May 25, 2026

### New features and enhancements

* The `/v1/search` endpoint now accepts filter-only requests with an empty `query` field. This enables the extension popup to fetch accounts matching the current browser tab's domain without providing a search term
* The `last_used: week` and `last_used: month` filter buckets on `/v1/search` now use cumulative rolling ranges (for example, "month" returns accounts used in the last 30 days including today) rather than mutually exclusive date bands. External integrators using these filters should verify their expected result sets
* A new `GET /v1/chaos/application-workflow-type/` endpoint lists all workflow types registered for a given application, optionally filtered by execution platform

***

## May 20, 2026

### New features and enhancements

* Accounts
  * [List the users in an account](https://developer.cerby.com/#list-the-users-in-an-account)
  * [Share an account with a user](https://developer.cerby.com/#share-an-account-with-a-user)
  * [Share an account with a team](https://developer.cerby.com/#share-an-account-with-a-team)
* Collections
  * [Add an account to a collection](https://developer.cerby.com/#add-an-account-to-a-collection)
  * [Add a secret to a collection](https://developer.cerby.com/#add-a-secret-to-a-collection)
  * [Share a collection with a user](https://developer.cerby.com/#share-a-collection-with-a-user)
  * [Share a collection with a team](https://developer.cerby.com/#share-a-collection-with-a-team)
  * [Update a collection](https://developer.cerby.com/#update-a-collection)
  * [Delete a collection](https://developer.cerby.com/#delete-a-collection)
* Users
  * [The user collection schema](https://developer.cerby.com/#the-user-collection-schema)
  * [The user account schema](https://developer.cerby.com/#the-user-account-schema)
  * [Add a user](https://developer.cerby.com/#add-a-user)
  * [List the accounts for a user](https://developer.cerby.com/#list-the-accounts-for-a-user)
  * [List the collections for a user](https://developer.cerby.com/#list-the-collections-for-a-user)
  * [Update a user](https://developer.cerby.com/#update-a-user)
* Integrations
  * Users can now be invited to a Business Hub with specific assets in a single call across TikTok, Google Ads, and Pinterest. Asset shares and role assignments are applied automatically when the invited user accepts and Cerby runs a sync.

***

## March 31, 2026

### New features and enhancements

* Accounts
  * [The account schema](https://developer.cerby.com/#the-account-schema) now has the following attributes:
    * `autofillMfa`
    * `avatarUrl`
    * `createdByEmail`
    * `domain`
    * `email`
    * `meta`
    * `passwordSet`
    * `passwordVisible`
    * `phone`
    * `rotatedAt`
    * `rotatedBy`
    * `rotatedById`
    * `status`
    * `syncedAt`
    * `url`
* Collections
  * [The subcollection schema](https://developer.cerby.com/#the-subcollection-schema)
  * [List the accounts in a collection](https://developer.cerby.com/#list-the-accounts-in-a-collection)
  * [List the secrets in a collection](https://developer.cerby.com/#list-the-secrets-in-a-collection)
  * [List the subcollections in a collection](https://developer.cerby.com/#list-the-subcollections-in-a-collection)
  * [List the users in a collection](https://developer.cerby.com/#list-the-users-in-a-collection)
  * [List the teams in a collection](https://developer.cerby.com/#list-the-teams-in-a-collection)
  * [Remove an account from a collection](https://developer.cerby.com/#remove-an-account-from-a-collection)
  * [Remove a secret from a collection](https://developer.cerby.com/#remove-a-secret-from-a-collection)
  * [Remove a user's access to a collection](https://developer.cerby.com/#remove-a-users-access-to-a-collection)
  * [Remove a team's access to a collection](https://developer.cerby.com/#remove-a-teams-access-to-a-collection)
* Users
  * [The user team schema](https://developer.cerby.com/#the-user-team-schema)
  * [The user secret schema](https://developer.cerby.com/#the-user-secret-schema)
  * [List the teams for a user](https://developer.cerby.com/#list-the-teams-for-a-user)
  * [List the secrets for a user](https://developer.cerby.com/#list-the-secrets-for-a-user)
* Integrations
  * [The integration asset schema](https://developer.cerby.com/#the-integration-asset-schema)
  * [The unmatched user schema](https://developer.cerby.com/#the-unmatched-user-schema)
  * [List the assets of an integration](https://developer.cerby.com/#list-the-assets-of-an-integration)
  * [List the unmatched users of an integration](https://developer.cerby.com/#list-the-unmatched-users-of-an-integration)

***

## February 13, 2026

### New features and enhancements

* Accounts
  * The account schema now has the following attributes:
    * `businessId`
    * `cerbyManagedEmail`
    * `cerbyManagedPhone`
    * `hasBackupCode`
    * `hasPasskey`
    * `hasTotp`
    * `lastLoginBy`
    * `lastPasswordChange`
    * `mfaEnabled`
    * `mfaTypes`
  * The account TOTP schema now includes information about the account’s time-based one-time password (TOTP) codes.
  * [Retrieve the TOTP code of an account](https://developer.cerby.com/#retrieve-the-totp-code-of-an-account)
* Collections
  * Create a collection
* Users
  * The user schema now includes an `mfaStatus` attribute that indicates whether MFA is turned on for guest and local users and the date when it was turned on.
* Teams
  * [The team account schema](https://developer.cerby.com/#the-team-account-schema)
  * [The team secret schema](https://developer.cerby.com/#the-team-secret-schema)
  * [The team collection schema](https://developer.cerby.com/#the-team-collection-schema)
  * [The team member schema](https://developer.cerby.com/#the-team-member-schema)
  * [List the accounts of a team](https://developer.cerby.com/#list-the-accounts-of-a-team)
  * [List the secrets of a team](https://developer.cerby.com/#list-the-secrets-of-a-team)
  * [List the collections of a team](https://developer.cerby.com/#list-the-collections-of-a-team)
  * [List the members of a team](https://developer.cerby.com/#list-the-members-of-a-team)
  * [Create a self-managed team](https://developer.cerby.com/#create-a-self-managed-team)
  * [Update a team](https://developer.cerby.com/#update-a-team)
  * [Delete a self-managed team](https://developer.cerby.com/#delete-a-self-managed-team)
  * [Add members to a self-managed team](https://developer.cerby.com/#add-a-member-to-a-self-managed-team)
* Integrations
  * [The integration user schema](https://developer.cerby.com/#the-integration-user-schema) now includes a `dynamicFields` attribute with additional user attributes in the external app, which represent custom fields or properties specific to the integration.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.cerby.com/updates-and-releases/cerby-api/2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.