Merge Excel Files in Cloud – Combine Spreadsheets Online with Aspose.Cells Cloud API

Quickly merge Excel files stored in the cloud with other spreadsheets using Aspose.Cells Cloud API, and specify the output data format and storage location.

Merge Remote Spreadsheet API

Before calling this operation, ensure you have:

  • A valid JWT access token (see the authentication guide).
  • The source workbook and all files to be merged uploaded to your cloud storage.
  • Appropriate permissions to read from the source folder and write to the target folder.

Web API

PUT https://api.aspose.cloud/v4.0/cells/{name}/merge/spreadsheet

Security and Authentication

The Aspose.Cells Cloud APIs are secure and require JWT token-based authentication.

Request Parameters:

Parameter Name Type Path/Query String/HTTPBody Description
name String Path The name of the source workbook file to be merged.
mergedSpreadsheet String Query A comma‑separated list of spreadsheet file names to merge into the source workbook.
folder String Query The folder path in cloud storage containing the source workbook.
outFormat String Query The desired format for the merged output file (e.g., XLSX, PDF, CSV).
mergeInOneSheet Boolean Query Set to true to merge all source data into a single worksheet; false creates separate worksheets for each file.
storageName String Query (Optional) The name of the cloud storage where the source workbook resides. If omitted, the default storage is used.
outPath String Query (Optional) The target folder path in cloud storage for saving the merged file. If omitted, the file is saved in the source folder.
outStorageName String Query The name of the cloud storage for saving the output file.
fontsLocation String Query (Optional) Custom folder path for font files used during conversion to image/PDF formats.
region String Query (Optional) Locale/region for date, number, and currency formatting in the output file (e.g., en-US, de-DE).
password String Query (Optional) Password required to open the source workbook if it is protected.

Response

Status: 200 OK

[
  {
    "Name": "ResponseFile",
    "DataType": {
      "Identifier": "File",
      "Reference": "Stream"
    }
  }
]

The file can be downloaded directly from or saved to the location specified by outPath.

Success response details

Status Code Content‑Type Description
200 OK application/octet-stream Binary stream of the merged workbook file.

HTTP Status Codes

Code Meaning Description
200 OK Filter applied successfully; response contains operation details.
400 Bad Request Missing or invalid parameters (e.g., unsupported file type).
401 Unauthorized Invalid or missing JWT token.
413 Payload Too Large Uploaded file exceeds size limit.
500 Internal Server Error Unexpected server error.

Where should we use the Merge Remote Spreadsheet API?

Enterprise‑grade data integration

  • Multi‑department report consolidation – Consolidate separate Excel reports submitted by sales, marketing, finance, and other teams.
  • Branch data summary – Summarize performance data from each branch worldwide.
  • Partner data consolidation – Merge data submissions from multiple partners into a single workbook.

Cloud document processing workflow

  • Cloud storage file processing: Directly merge Excel files stored in AWS S3, Azure Blob, or Google Cloud Storage.
  • Multi‑source data consolidation – Combine files from different cloud locations into one workbook.
  • Automated data pipelines – Integrate the API into ETL processes to automate file merging.

Document‑management automation

  • Version‑control consolidation – Merge different versions of a project plan or budget workbook.
  • Template data population – Insert data files into standardized reporting templates.
  • Regular report generation – Automate weekly, monthly, and quarterly summary reports.

Cross‑platform collaboration

  • Remote‑team collaboration – Consolidate work submitted by dispersed team members.
  • Customer data organization – Merge order or feedback data from multiple customers.
  • Supplier information summary – Combine quotes or product information from several suppliers.

Why should you use the Merge Remote Spreadsheet API?

  • Developer‑friendly – Aspose.Cells Cloud provides SDKs for many languages, shortening development time and offering comprehensive documentation. Compared with building a custom solution, this reduces workload dramatically.
  • Reduced labor costs – Decreases the need for staff dedicated to manual document consolidation.
  • Pay‑per‑use – No upfront investment; you only pay for the API calls you actually use.
  • Zero maintenance costs – No servers to maintain, no software updates, and no compatibility concerns.

How to Use the Merge Remote Spreadsheet API with SDKs

Merge Remote Spreadsheet API Specification

The Merge Remote Spreadsheet API Specification describes the REST interface that can be called directly from any HTTP client.

You can use the cURL command‑line tool to access Aspose.Cells web services easily. The following example shows how to make calls to the Cloud API with cURL.

Use Aspose.Cells Cloud SDKs

Using an SDK is the fastest way to develop, as it abstracts low‑level details and lets you merge a spreadsheet into another spreadsheet with a short code snippet.
Please check out the GitHub repository for a complete list of Aspose.Cells Cloud SDKs.

The following code examples demonstrate how to interact with Aspose.Cells web services using various SDKs:

Split Table Import XML Data Into Spreadsheet