Changelog
Access Dev CenterSuggest a FeatureContact SupportCreate SandboxRequest a Demo
Back to All
Added

API Changelog 7.26.0

May 12th, 2026

Added

  • Added endpoint to change a workspace member's role, allowing you to programmatically assign built-in roles (Admin, Manager, Member, Collaborator) or custom workspace roles without removing and re-adding the member

PATCH /public/v1/workspaces/{workspace_id}/members/{member_id}/role

  • endpoint added
  • Enhanced document recipient management by introducing new properties for RecipientGroup objects. You can now define and update recipient groups with specific IDs, members, and types when modifying a document, providing more granular control over document distribution.

PATCH /public/v1/documents/{id}

  • added the new optional request property recipients/items/anyOf[subschema #2: RecipientGroup]/id
  • added the new optional request property recipients/items/anyOf[subschema #2: RecipientGroup]/members
  • added the new optional request property recipients/items/anyOf[subschema #2: RecipientGroup]/type

Changed

  • Updated the definition of RecipientGroup objects. The name property is now required for recipient groups, and the overall structure has been refined, including changes to its type/format and the removal of BaseActor from its inheritance chain, ensuring a more distinct and robust group definition.

PATCH /public/v1/documents/{id}

  • ⚠️ added the new required request property recipients/items/anyOf[subschema #2: RecipientGroup]/name
  • ⚠️ the recipients/items/anyOf[subschema #2: RecipientGroup]/ request property type/format changed from / to object/``
  • ⚠️ removed #/components/schemas/BaseActor from the recipients/items/anyOf[subschema #1: Recipient]/ request property allOf list
  • ⚠️ removed #/components/schemas/BaseActor, subschema #2 from the recipients/items/anyOf[subschema #2: RecipientGroup]/ request property allOf list

Update docs to reflect current implementation

  • The POST /public/v1/documents/{id}/linked-objects endpoint now returns a 201 Created status for successful operations, aligning with standard REST API practices for resource creation and providing clearer feedback when objects are successfully linked.

POST /public/v1/documents/{id}/linked-objects

  • ⚠️ removed the success response with the status 200
  • added the success response with the status 201