Changelog

Stability

The Access SDK API is served under /api/v1 and is not versioned beyond that prefix: changes ship in place rather than under a new version. Additive changes (new response fields, new optional parameters, new endpoints) are backward compatible and ship without notice, so read response fields by name and ignore any field you do not recognize. Breaking changes are avoided; when one becomes unavoidable, it is announced here before it ships.

Notable changes are listed below, newest first.

July 2026

• DAM login takes provider parameters. The initiate call accepts serverUrl, which answers up front the instance prompt CI HUB would otherwise show the end user. Six providers read it. Omit it and the flow is unchanged. See Provider parameters.
• Email in the request body is documented. Token exchange has always accepted email in the JSON body when the partner JWT carries no email claim, which is how partners who anonymize the address integrate. The behavior is unchanged; it now has examples and the two constraints written down.

Phase 1 (June 2026)

First release of the Access SDK: read-only access to a connected DAM.

• Authentication. Token exchange: a partner backend signs a JWT and exchanges it for a CI HUB access token and refresh token (POST /auth/exchangeToken). Server to server, no browser redirect.
• DAM connection. List available providers, initiate and poll a provider login, and read provider capabilities.
• Content. Browse folders, keyword and similarity search, read asset detail and version history. Read-only.
• Errors. One standard error envelope across every endpoint, with a source field that separates CI HUB errors from provider errors.