Update your API integrations to support Renditions

We’ve updated our APIs to support projects enabled with 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.

In this article you'll find a summary of changes for Documents and Mail APIs followed by the details for each updated endpoint.

What's changing in Documents APIs?

You must use a new request model when registering or updating documents using APIs.

When searching, the following response fields continue to represent the primary file: FilenameFileType, and FileSize.

Two new response fields have been introduced:

  • FileCount: The total number of files linked to the document.
  • SecondaryFiles: A collection of secondary file entries associated with the document.

Users integrating with Renditions should update their implementations to:

  • Detect whether Renditions is enabled through the document schema.
  • Handle FileCount and SecondaryFiles in document search and metadata responses.
  • Continue treating existing file fields as the primary file only.
  • Use the Renditions request model when registering or superseding multi-file documents.
  • Use either Temporary File Upload plus TempDocumentIds, or direct multipart file upload with up to 5 base64-encoded file contents, when submitting multi-file documents.
  • Update download flows to request a specific file when a non-primary file is needed.

What's changing in Mail APIs?

There's a new includeSecondary flag when sending or saving a Transmittal or Tender Transmittal. This flag determines if secondary files should be included with a document:

  • includeSecondary: true includes secondary files for that attached document.
  • includeSecondary: false excludes secondary files for that attached document.
    • If includeSecondary is omitted, behavior follows the project preference “Include Secondary Files".

When viewing or listing mail, a new SecondaryFiles block is returned for secondary files. Existing FileName and FileSize fields continue to represent the primary file.  AttachmentFileSize is the total size of the primary file size plus all included secondary files.

Users integrating with Renditions should update their implementations to:

  • Apply Renditions logic only for transmittal mail types.
  • Send 'includeSecondary' per attached document when they need to override the project preference.
  • Expect no change for non-transmittal mail types.
  • Handle SecondaryFiles in View Mail Metadata responses.
  • Interpret attachment-size fields in List Mail as the sum of all included files, not just the primary file.
 

View Document Schema

The document registration schema is enhanced to support new Renditions-related fields.

Changes:

  • RegisterSchema now includes a 'renditionsEnabled' boolean attribute. Users can detect whether the project has Renditions enabled from this.
  • SearchSchemaFields now include 'fileCount'.
  • SearchSchemaFields now include 'secondaryFiles' as a complex field.
  • EntityCreationSchemaFields now include TempDocumentIds so previously uploaded temporary files can be linked to one document.
  • EntityCreationSchemaFields now include a boolean 'Renditions' field. This must be set to true when registering or superseding documents in projects where Renditions is enabled.

Sample Response:



    
        ........
        
            
                
            
            COMPLEX
            TempDocumentIds
            TempDocumentIds
            
                
                    TempDocument
                    
                        
                            
                                
                            
                            STRING
                            Id
                            id
                        
                        
                            
                                
                            
                            STRING
                            Type
                            type
                        
                    
                    tempDocument
                
            
        
        
            
                
            
            BOOLEAN
            Renditions
            Renditions
        
        ........
    
    
     ...........
        
            
                
            
            COMPLEX
            Secondary Files
            secondaryFiles
            
                
                    File
                    
                        
                            
                                
                            
                            STRING
                            FileSize
                            fileSize
                        
                        
                            
                                
                            
                            STRING
                            FileType
                            fileType
                        
                        
                            
                                
                            
                            STRING
                            Filename
                            filename
                        
                    
                    file
                
            
        
        
            
                
            
            INTEGER
            File Count
            fileCount
        
       ...........
    

View Document Metadata

Metadata responses for Renditions documents now expose file-set information.

Changes:

  • Adds 'FileCount'.
  • Adds 'SecondaryFiles'.
  • Primary file metadata continues to be returned through existing file fields.

Sample Response:




  CONT_12345
  CONT_12345
  Manual
  1
  2
  50869
  pdf
  EP01.pdf
  
    
      83456
      doc
      EP01.doc
    
  

List Documents

Document search responses can now return Renditions file-set information.

Changes:

  • 'return_fields' supports 'fileCount' and 'secondaryFiles'.
  • 'search_query' supports 'fileCount'.
  • Secondary-file search support is added for 'secondaryfilename' and 'secondaryfiletype' in 'search_query'
  • Responses can include FileCount and SecondaryFiles.
  • Existing file fields continue to return the primary file information only.

Sample Request:


GET /api/projects/1207959554/register?search_query=doctype:%20Drawing&return_fields=docno,filecount,title,secondaryFiles&search_type=NUMBER_LIMITED&search_result_size=75&sort_field=docno&sort_direction=ASC&show_document_history=true 
Sample Response:



  
    
      CONT_12346
      2
      
        
          249344
          doc
          O&T-2006.doc
        
      
      CONT_12346
    
    
      DNN_1034
      0
      
      DNN_1034
    
  

List Drawings

Drawing search responses follow the same Renditions pattern as document search.

Changes:

  • 'return_fields' supports 'fileCount' and 'secondaryFiles'.
  • 'search_query' supports 'fileCount'.
  • Secondary-file search support is added for 'secondaryfilename' and 'secondaryfiletype' in 'search_query'
  • Responses can include FileCount and SecondaryFiles.
  • Existing file fields continue to return the primary file information only.

Sample Request:


GET /api/projects/1207959554/drawings?search_query=doctype:%20Drawing&return_fields=docno,filecount,title,secondaryFiles&search_type=NUMBER_LIMITED&search_result_size=75&sort_field=docno&sort_direction=ASC&show_document_history=true 

Sample Response:




  
    
      CONT_12346
      2
      
        
          249344
          doc
          O&T-2006.doc
        
      
      CONT_12346
    
    
      DNN_1034
      0
      
      DNN_1034
    
  

All Filters List Documents

The All-Filters List Documents API can now return Renditions file-set information.

Changes:

  • returnFields supports 'fileCount' and 'secondaryFiles'.
  • Responses can include 'fileCount' and 'secondaryFiles'.
  • Existing filename continues to represent the primary file.
  • This endpoint does not add secondary filename or secondary file type filters to the search request.

Sample Request:


​POST /api/projects/1207959554/register/search

{
  "orgId": "1879048492",
  "userId": "1879049107",
  "returnFields": [
    "docno",
    "title",
    "doctype",
    "filename",
    "printSize",
    "comments",
    "attribute1",
    "attribute2",
    "fileCount",
    "secondaryFiles"
  ],
  "resultSize": "25",
  "returnTransmittalIds": "false"
}

Sample Response:


{
  "searchResults": [
    {
      "id": 271341877549172398,
      "documentNumber": "CONT_12345",
      "title": "CONT_12345",
      "documentType": "Manual",
      "comments": "",
      "printSize": "1",
      "filename": "EP01.pdf",
      "fileCount": 2,
      "secondaryFiles": [
        {
          "filename": "EP01.doc",
          "fileSize": "83456",
          "fileType": "doc"
        }
      ]
    },
    {
      "id": 271341877549122393,
      "documentNumber": "DNN_1034",
      "title": "DNN_1034",
      "documentType": "Drawing",
      "comments": "",
      "printSize": "1",
      "filename": "",
      "fileCount": 0,
      "secondaryFiles": []
    }
  ],
  "totalResultsCount": 2,
  "totalResultsOnCurrentPage": 2,
  "totalNumberOfPages": 1,
  "currentPageNumber": 1,
  "singlePageSize": 25
}

Register Document

Document registration now supports creating a single document record with a primary file and secondary files.

Changes:

  • A Renditions document can contain up to 5 files in total.
  • Files can be uploaded individually through Temporary File Upload and then referenced using TempDocumentIds in this endpoint. Each temporary document reference identifies whether the file is Primary or Secondary. Use this method when the total file size exceeds 100MB.
  • As an alternative, a single register request can directly include up to 5 base64-encoded file contents in the multipart body. The first file in sequence will be considered primary. Use this method when the total file size is within 100MB. Registration succeeds only when the full file set is uploaded. Partial registration of a Renditions document is not supported.
  • Renditions-enabled projects must send Renditions=true when using the Renditions registration model.

Sample Request using TempDocumentIds:


POST /api/projects/1207959554/register HTTP/1.1

--myboundary

  DNN_123456121
  1879048197
  1
  Majestic Builders
  Civil
  1879048196
  A4
  false
  2026-03-06T12:00:00.000Z
  false
  true
  
    
      3453453535
      Primary
    
    
      767576
      Secondary
    
  

--myboundary--

Sample Request using direct file content:


POST /api/projects/1207959554/register HTTP/1.1

--myboundary

  doc_reg_multi_1
  1207959557
  1
  Majestic Builders
  Concrete Works
  1207959618
  false
  2026-04-06T12:00:00.000Z
  true
  true

--myboundary
X-Filename: primary.pdf
cHJpbWFyeSBmaWxlIGNvbnRlbnRzCg==
--myboundary
X-Filename: secondary1.doc
Zmlyc3Qgc2Vjb25kYXJ5IGZpbGUgY29udGVudHMK
--myboundary
X-Filename: secondary2.dwg
c2Vjb25kIHNlY29uZGFyeSBmaWxlIGNvbnRlbnRzCg==
--myboundary--

Supersede Document

Document supersede now supports replacing the full Renditions file set.

Changes:

  • A superseded Renditions document can include up to 5 files in total.
  • Files can be uploaded individually through Temporary File Upload and then referenced using TempDocumentIds in this endpoint.  Each temporary document reference identifies whether the file is Primary or Secondary. Use this method when the total file size exceeds 100MB.
  • As an alternative, a single supersede request can directly include up to 5 base64-encoded file contents in the multipart body. Use this method when the total file size is within 100MB.  Supersede succeeds only when the complete new file set is uploaded. 
  • Renditions-enabled projects must send Renditions=true when using the Renditions supersede model.

Sample Request using TempDocumentIds:


POST /api/projects/1207959554/register/271341877549322396/supersede

--myboundary

  1879048197
  2
  Majestic Builders
  Civil
  1879048196
  A4
  false
  2026-04-06T12:00:00.000Z
  false
  true
  
    
      8453453535
      Primary
    
    
      867576
      Secondary
    
  

--myboundary--

Sample Request using direct file content


POST /api/projects/1207959554/register/271341877549322396/supersede

--myboundary

  1207959557
  2
  Majestic Builders
  Concrete Works
  1207959618
  false
  2026-04-06T12:00:00.000Z
  true
  true

--myboundary
X-Filename: primary.pdf
cHJpbWFyeSBmaWxlIGNvbnRlbnRzCg==
--myboundary
X-Filename: secondary1.doc
Zmlyc3Qgc2Vjb25kYXJ5IGZpbGUgY29udGVudHMK
--myboundary
X-Filename: secondary2.dwg
c2Vjb25kIHNlY29uZGFyeSBmaWxlIGNvbnRlbnRzCg==
--myboundary--

Download Document File

File download now supports Renditions documents with multiple files.

Changes:

  • A specific file in the document can be downloaded by supplying a file name in the request.
  • If no file name is supplied, the primary file is downloaded by default.
  • The binary response format remains unchanged.
  • Download activity continues to be recorded in document event history.

Sample Request:


GET /api/projects/1207959554/register/271341877549172398/?fileName=EP01.doc>

Temporary File Upload

  • This endpoint can be used to upload individual files before linking them to a Renditions document through register or supersede.
  • Large File Upload through automated chunking has now been enabled for this endpoint. You can use asyncLargeFile=true as a query param to process it as a background job. The status check API can be called get the status of the background job. Note: This is similar to how you register and supersede large files. For details see the Large File Upload - Option 1 section in the API Documentation

Create Mail With Document Attachments

Create Mail now supports Renditions-aware document attachment behavior for transmittal mail types.

Changes:

  • Each attached document can include an includeSecondary flag in its multipart section.
  • The flag is evaluated per attached document.
  • If the flag is omitted, the existing project preference determines whether secondary files are attached.
  • No response format changes are introduced.
Sample request

​POST /api/projects/1879053193/mail

--myboundary
Content-Type: application/vnd.aconex.mail.v3+xml


  Transmittal with Renditions documents
  23
  1
  1
  2028-11-21T12:00:00.000Z
  true
  1879053295
  false
  2

--myboundary
X-DocumentId: 271341877555449767
includeSecondary: false

--myboundary
X-DocumentId: 271341877555449768
includeSecondary: true

--myboundary--

Save To Draft With Document Attachments

Save To Draft supports the same Renditions-aware attachment behavior as Create Mail for transmittal mail types.

Changes:

  • Each attached document can include an includeSecondary flag.
  • The flag is evaluated per attached document.
  • If the flag is omitted, the existing project preference determines whether secondary files are attached.
  • No response format changes are introduced.
Sample request:

​POST /api/projects/1879053193/mail?is_draft=true

--myboundary
Content-Type: application/vnd.aconex.mail.v3+xml


  Draft transmittal with Renditions documents
  23
  1
  1
  2028-11-21T12:00:00.000Z
  true
  1879053295
  false
  1

--myboundary
X-DocumentId: 271341877555449767
includeSecondary: true

--myboundary--

Reply Mail With Document Attachments

Reply Mail supports the same Renditions-aware attachment behavior as Create Mail for transmittal mail types.

Changes:

  • Each attached document can include an includeSecondary flag.
  • The flag is evaluated per attached document.
  • If the flag is omitted, the existing project preference determines whether secondary files are attached.
  • No response format changes are introduced.
Sample request:

POST /api/projects/1879053193/mail/1879167861/reply 

--myboundary
Content-Type: application/vnd.aconex.mail.v3+xml


  Reply with Renditions document
  23
  1
  1
  2027-11-21T12:00:00.000Z
  true
  1879053295
  false
  1

--myboundary
X-DocumentId: 271341877555449767
includeSecondary: true

--myboundary--

Forward Mail With Document Attachments

Forward Mail supports Renditions-aware attachment behavior for both newly attached documents and forwarded attachments on transmittal mail types.

Changes:

  • Attached documents can include an includeSecondary flag.
  • Forwarded existing attachments can also include an includeSecondary flag.
  • The flag is evaluated per document or attachment.
  • If the flag is omitted for forwarded attachments, the original forwarded content is preserved.
  • No response format changes are introduced.
Sample request:

POST /api/projects/1879053193/mail/1879167861/forward 

--myboundary
Content-Type: application/vnd.aconex.mail.v3+xml


  Forward with Renditions document and attachment
  23
  1
  1
  2029-11-21T12:00:00.000Z
  true
  1879053295
  false
  2

--myboundary
X-DocumentId: 271341877555449767
includeSecondary: true

--myboundary
X-AttachmentId: 35353535
includeSecondary: false

--myboundary--

Register Mail With Document Attachments

Register Mail supports the same Renditions-aware attachment behavior as Create Mail for transmittal mail types.

Changes:

  • Each attached document can include an includeSecondary flag.
  • The flag is evaluated per attached document.
  • If the flag is omitted, the existing project preference determines whether secondary files are attached.
  • No response format changes are introduced.
Sample request:

​POST /api/projects/1879053193/mail/register 

--myboundary
Content-Type: application/vnd.aconex.mail.v3+xml


  Registered transmittal with Renditions document
  256
  1
  1
  2028-11-21T12:00:00.000Z
  true
  1879053295
  false
  1

--myboundary
X-DocumentId: 271341877555449767
includeSecondary: true

--myboundary--

View Mail Metadata

Mail metadata responses now expose secondary file information when an attached registered document includes secondary files.

Changes:

  • Existing FileName and FileSize fields continue to represent the primary file.
  • A new SecondaryFiles block is returned for secondary files.
  • No request format changes are introduced.

Sample Response:




  TRM-000124
  Renditions transmittal
  Transmittal
  
    
      1879167990
      271341877555449767
      alcala.pdf
      57344
      
        
          79980
          alcala.dwg
        
        
          79980
          alcala.xlsx
        
      
    
  

List Mail

List Mail now reflects the total size of all included files for Renditions document attachments.

Changes:

  • AttachmentFileSize now includes the primary file size plus all included secondary file sizes.
  • For transmittal mail types, whether secondary files are counted depends on includeSecondary flag or, if omitted, the project preference.
  • For non-transmittal mail types, existing behavior remains unchanged.
  • No request format changes are introduced.