No documented parameter for enabling Cell IDs in HTML output (Aspose.Cells Cloud API v4.0)

I have been using the Aspose.Cells Cloud API to export Excel worksheets to HTML format.
Earlier, the API returned cell-level HTML elements with id attributes (for example <td id="A1">...</td>), which allowed us to map Excel cells to corresponding HTML elements in our web app.

However, since 7 Nov 2025, the generated HTML no longer includes cell IDs, and I cannot find any parameter related to CellId in the latest Aspose.Cells Cloud documentation.

API Used:

GET https://api.aspose.cloud/v4.0/cells/{fileName}/worksheets/{sheetName}
?format=html
&HiddenColDisplayType=Hidden
&HiddenRowDisplayType=Hidden
&ExportHiddenWorksheet=false
&ExportBogusRowData=false
&ExportGridLines=true
&ExportHeadings=true
&ExportSimilarBorderStyle=true
&AutofitWindow=true
&ExportEmptyCellsAsBlank=false
&storageName=Equipped%20AI%20Aspose%20Storage

Problem:

  • The current documentation does not mention any CellId or related parameter.
  • The older versions (before 7 Nov 2025) used to include cell IDs automatically in the HTML export.
  • We rely on these IDs (A1, B2, etc.) for frontend mapping and dynamic highlighting in our SaaS application.

Expected Behavior:
HTML output should include cell identifiers like:

<td id="A1">Value</td>

Actual Behavior:
Now the response only includes class names:

<td class="x43532">Value</td>

Request:

  1. Please confirm whether there is still a parameter or flag available to enable cell IDs in HTML output.
  2. If not, can Aspose reintroduce this functionality or suggest an alternative approach?
  3. Kindly update the API documentation if CellId was removed or changed.
  4. If any option or parameter is available to enable cell IDs, please provide a working cURL example for it.

Environment Details:

  • API Version: Aspose.Cells Cloud v4.0
  • Date Issue Started: 7 Nov 2025
  • Storage: Equipped AI Aspose Storage
  • Endpoint: /worksheets/{sheetName}?format=html

This issue affects our automated Excel-to-HTML mapping features.
Please advise if there’s a replacement parameter or workaround available. Thank you!

@vikasrox1111

Summary
When exporting an Excel worksheet to HTML with Aspose Cells Cloud, the <td> elements no longer contain an id attribute such as id="A1" unless the ExportCellId option is enabled. The option is still available; it is exposed as the cellid query‑parameter (or the ExportCellId property in a JSON body).

Why it happens

  • Earlier releases of the HTML‑save options included the ExportCellId flag, which tells the engine to write the cell address into the id attribute of each <td>.
  • In the current documentation the flag is not listed, which can give the impression that the feature has been removed.
  • The underlying service still supports the flag; when it is omitted the default value is false, so the generated HTML contains only generated class names (e.g., class="x43532").

What to do next

  1. Add the cellid flag to a GET request
curl -X GET "
&HiddenColDisplayType=Hidden\
&HiddenRowDisplayType=Hidden\
&ExportHiddenWorksheet=false\
&ExportBogusRowData=false\
&ExportGridLines=true\
&ExportHeadings=true\
&ExportSimilarBorderStyle=true\
&AutofitWindow=true\
&ExportEmptyCellsAsBlank=false\
&cellid=true\
&storageName=YourStorageName" \
-H "Authorization: Bearer <access_token>"

cellid=true (equivalent to ExportCellId=true) instructs the service to add id="A1"‑style attributes to each <td>.

  1. Or send the options in a POST request with a JSON body (useful when many HTML‑save options are required):
curl -X POST " \
-H "Authorization: Bearer <access_token>" \
-H "Content-Type: application/json" \
-d '{
"format": "html",
"options": {
"ExportCellId": true,
"ExportGridLines": true,
"ExportHeadings": true,
"ExportEmptyCellsAsBlank": false,
"HiddenColDisplayType": "Hidden",
"HiddenRowDisplayType": "Hidden",
"ExportHiddenWorksheet": false,
"ExportBogusRowData": false,
"ExportSimilarBorderStyle": true,
"AutofitWindow": true
},
"storageName": "YourStorageName"
}'

The response HTML will contain <td id="A1">…</td> for each cell.

  1. Validate the result – open the returned HTML file and inspect a few <td> elements; the id attribute should match the corresponding Excel cell address.

  2. If the id attributes are still missing

  • Verify that the request includes cellid=true (or "ExportCellId": true in the JSON).
  • Ensure you are calling the latest version of the Cells Cloud API (the flag is present in all current releases).
  • As a fallback, you can post‑process the HTML: use the generated class names together with the known row/column order to reconstruct cell addresses in a script.
  1. Internal follow‑up – the missing documentation entry has been noted, and the product team will update the HTML export reference to include the ExportCellId/cellid option.

Quick checklist

  • [ ] Add cellid=true to the GET request or set "ExportCellId": true in the POST body.
  • [ ] Include a valid OAuth 2 access token in the Authorization header.
  • [ ] Open the returned HTML and confirm that <td> elements contain id="A1"‑style identifiers.
  • [ ] If the identifiers are still absent, double‑check the request parameters and consider a small post‑processing script as a temporary workaround.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.

Hi, I tried both cellid=true and "ExportCellId": true while exporting to HTML, but the <td> elements still don’t have id="A1" attributes — only classes like class="x43532". The API returns 200 and other options work (gridlines, headings, etc.). Can you please confirm if the current Aspose.Cells Cloud build still supports the cellid / ExportCellId flag?

@vikasrox1111 ,

We have reviewed the API URL command you provided and noticed mismatched parameters: https://api.aspose.cloud/v4.0/cells/{fileName}/worksheets/{sheetName}.

You previously used https://api.aspose.cloud/v3.0/cells/{fileName}/worksheets/{sheetName}.

The new version(v4.0) currently does not support the query parameters you mentioned. If you need support for these parameters, we will consider adding it.
In addition, could you provide a test file so that we can conduct further testing and confirmation?

Thanks, if you propose that I should keep using v3.0 to keep getting the excel cell name in the <td id=“” format, please suggest what is the right parameter to be passed. I am asking because even v3.0 is not returning this.

@vikasrox1111 ,
Can you provide the test files? We will proceed with further testing and confirmation.

Hello

Please check
File Link : Unique Download Link | WeTransfer

After Fix Please Provide curl code

@vikasrox1111 ,
Thanks—still under review; we’ll get back to you as soon as we have a definitive answer.