Ensure your API integrations support 64-bit records

• In October 2026, we'll upgrade Aconex database fields to 64-bit across all Aconex instances. If your organization integrates with Aconex APIs, you'll need to review your integrations and ensure they support 64-bit data types. 
• The EA1 instance has been upgraded to 64-bit and is ready for you to test your integration(s). Learn how to review your API integrations.

Migrate to OAuth for enhanced security

• Towards the beginning of 2027 we're planning to retire all Integration IDs. This means that Basic Auth will soon no longer be accepted for API access.
• From November 2026, you'll no longer be able to create new Integration IDs. Existing Integration IDs will continue to work until they are retired in early 2027.
• We're providing early notice so you can start planning to migrate to OAuth to avoid additional effort later.
• If you're not already subscribed to receive updates, we encourage you to subscribe to API News for important information regarding Basic Auth retirement.

Update your API integrations to support Renditions

• Before you enable Renditions on a project, you'll need to update your API integrations to support secondary files for documents. Existing integrations will continue to work for projects that are not enabled with Renditions. Learn more.

Manage OAuth public certificates

• You can now upload and manage your own public certificates for OAuth clients used in Non-Interactive Integrations.
• When creating a new OAuth client, upload your public certificate as part of the setup. For existing Non-Interactive Integrations, you can replace the certificate yourself whenever needed.
• You no longer need to raise a Service Request (SR) for this.

Get supplementary files from workflows

• Retrieve workflow supplementary file metadata without accessing the app. The files can be downloaded individually or in bulk.
• This helps you collect supporting evidence together with workflow details using automated processes.
• View the Workflows API Developer Guide.

Close, reopen, or mark packages as no longer in use

• The Packages API has a new package-state endpoint allowing you to close, reopen, or mark a package as no longer in use.

Rename files on download

• The Download Document File and Download Mail Attachment APIs now support the project preference to Rename files on download to include Document Number and Revision. 
• With the preference enabled, registered documents downloaded with these APIs will be renamed with the document number and revision. This matches the current behavior in the app.