Things to check before integrating
Before you integrate
Place the intended sheet first, or upload it as a separate workbook; inspect dates and leading-zero identifiers in the extracted values.
Before you integrate
Visual character width and multiline values can disrupt grid syntax; validate with the destination document renderer.
Code examples
These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.
Excel to reStructuredText grid table API · cURL
curl --fail-with-body --max-time 40 \
'https://api.tableconvert.com/v2/convert/excel-to-restructuredtext' \
--header "Authorization: Bearer $TABLECONVERT_API_KEY" \
--form 'file=@excel-to-restructuredtext-input.xlsx' \
--form-string 'output[style]=+++-,+++=,+++-,+++-,|' \
--form-string 'output[forceSep]=false' \
--form-string 'output[align]=l' \
--output 'excel-to-restructuredtext.rst'Requires cURL. Download the sample input first when this example uploads a file.
Excel to reStructuredText grid table API · Python
import os
from pathlib import Path
import requests
endpoint = "https://api.tableconvert.com/v2/convert/excel-to-restructuredtext"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
"output[style]": (None, "+++-,+++=,+++-,+++-,|"),
"output[forceSep]": (None, "false"),
"output[align]": (None, "l"),
}
with open("excel-to-restructuredtext-input.xlsx", "rb") as source:
files = {**fields, "file": ("excel-to-restructuredtext-input.xlsx", source)}
response = requests.post(endpoint, headers=headers, files=files, timeout=40)
response.raise_for_status()
Path("excel-to-restructuredtext.rst").write_bytes(response.content)Requires Python 3 and requests. Install it with pip install requests.
Excel to reStructuredText grid table API · Node.js
import { readFile, writeFile } from "node:fs/promises";
const form = new FormData();
form.set("file", new Blob([await readFile("excel-to-restructuredtext-input.xlsx")]), "excel-to-restructuredtext-input.xlsx");
form.set("output[style]", "+++-,+++=,+++-,+++-,|");
form.set("output[forceSep]", "false");
form.set("output[align]", "l");
const response = await fetch("https://api.tableconvert.com/v2/convert/excel-to-restructuredtext", {
method: "POST",
headers: { Authorization: "Bearer " + process.env.TABLECONVERT_API_KEY },
body: form,
signal: AbortSignal.timeout(40_000),
});
if (!response.ok) {
throw new Error("HTTP " + response.status + ": " + await response.text());
}
await writeFile("excel-to-restructuredtext.rst", Buffer.from(await response.arrayBuffer()));Requires Node.js 20 or later with built-in fetch, FormData and Blob.
Authentication
Send Authorization: Bearer YOUR_API_KEY. Let the HTTP client set the multipart boundary; do not set Content-Type manually.
Keep production API keys in server-side environment variables.
Request parameters
The API reads the first worksheet of an uploaded workbook as cell values and normalizes it into table rows. It does not preserve the workbook’s formulas, charts or visual design.
| Parameter | Type | Default | Description |
|---|---|---|---|
data | string | — | For workbook input, use file or url. The example uploads a real .xlsx workbook. |
file | binary | — | Upload a xlsx file using multipart/form-data. |
url | string | — | A supported publicly accessible HTTP or HTTPS file URL. |
Send one source: data, file, or url. The examples below use the source mode appropriate for this format.
Output options
Generate a reStructuredText-style grid table for Sphinx or Docutils source. The table is plain text with width-sensitive borders.
| Parameter | Type | Default | Description |
|---|---|---|---|
output[style] | string | +++-,+++=,+++-,+++-,| | Set the border-character pattern used to draw the plain-text grid. |
output[forceSep] | boolean | false | Draw a separator between each body row of the text table. |
output[align] | string | l | Choose left, center or right alignment for generated table cells. |
Conversion rules
| Case | Behavior |
|---|---|
| Mapping rule 1 | The first worksheet’s values become rows and columns, with the first extracted row available as the destination header. |
| Mapping rule 2 | The header and records are padded into a grid with a distinct header separator. |
| Mapping rule 3 | Translate worksheet values into document table syntax; Excel colors, merged regions and charts do not become equivalent markup. |
How the input is read
- Place the intended data in the first worksheet, using a simple rectangular range with a deliberate first-row header.
- The conversion uses extracted cell values, not the spreadsheet as an executable calculation model.
- Only the first extracted worksheet is converted. There is no input sheet-selection parameter, and workbook sheets are not merged.
- Review date displays, leading zeros and large identifiers after extraction; original Excel types and formatting do not transfer to every target.
How the output is written
- A header separator distinguishes the first row from body rows.
- Use a monospaced source editor and inspect multiline or wide Unicode cells.
- Test the grid with the actual Docutils/Sphinx renderer before publishing.
When to use this API
This conversion in practice
Use a worksheet export as the starting dataset for a Sphinx or Docutils reference page. Place the intended sheet first, or upload it as a separate workbook; inspect dates and leading-zero identifiers in the extracted values.
reStructuredText grid table
Keep an extracted data table in Sphinx reference documentation.
Responses and errors
| HTTP status | Description |
|---|---|
200 | text/plain; charset=utf-8 |
400 | Invalid input or conversion parameters. |
402 | Insufficient credits for this request. |
403 | Missing or invalid API key. |
413 | The input exceeds the configured request limit. |
415 | Unsupported input media type. |
429 | Rate limit exceeded. |
500 | The conversion could not be completed. |
503 | The renderer is unavailable or the request timed out. |
Check the response before retrying. A new HTTP request is a new conversion and may use credits again.
Limits, billing and versions
Local previews accept up to 200 KB. The current API implementation allows one uploaded file up to 50 MiB, limits each multipart text field to 1 MiB, and gives v2 conversion tasks a 30-second deadline. Deployment limits may be stricter. Read the returned error before retrying; some parser or renderer failures return HTTP 500.
Live calls follow the API credit policy. Failed conversions are refunded; a completed conversion is not undone if the download connection later fails.
View API pricing and creditsUsing API v1?
This page documents v2, which returns the output directly. API v1 wraps the result in a JSON envelope. Check the overview before changing an existing integration.
API overviewReferences and format specifications
Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.