Hello,

I’m trying to set an expiration date for a collaborator when inviting them to a folder using the POST /collaborations API.

As stated in the API reference, I included the expires_at parameter in my request.
However, even after adjusting the Enterprise settings, the expiration date I set is always overridden by the Enterprise policy (60 days).

Here is the request body I sent:

{ "item": { "type": "folder", "id": "1234567890" }, "accessible_by": { "type": "user", "login": "user@example.com" }, "role": "editor", "expires_at": "2025-12-30T23:59:59+00:00" }

And here is the response I received:

{ "type": "collaboration", "id": "9876543210", "created_by": { "type": "user", "id": "111111", "name": "USER NAME", "login": "creator@example.com" }, "created_at": "2025-09-04T23:45:04-07:00", "modified_at": "2025-09-04T23:45:04-07:00", "expires_at": "2025-11-03T23:59:00-08:00", "status": "accepted", "accessible_by": { "type": "user", "id": "222222", "name": "INVITED USER", "login": "user@example.com", "is_active": true }, "role": "editor", "item": { "type": "folder", "id": "1234567890", "sequence_id": "0", "etag": "0", "name": "FOLDER NAME" }, "is_access_only": false }

As you can see, the expires_at value is changed to match the Enterprise default (60 days), instead of the date I specified.

Is this expected behavior?
Is there any way to enforce a custom expiration date beyond the Enterprise setting?

Thanks in advance for your support.