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
Split the schema from appended JSON before compilation; the complete API output is not directly compilable or protobuf binary data.
Before you integrate
Database or worksheet types are not recovered as schema types; generated message/record fields are strings.
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 Protocol Buffers schema API · cURL
curl --fail-with-body --max-time 40 \
'https://api.tableconvert.com/v2/convert/excel-to-protobuf' \
--header "Authorization: Bearer $TABLECONVERT_API_KEY" \
--form 'file=@excel-to-protobuf-input.xlsx' \
--output 'excel-to-protobuf.protobuf.txt'Requires cURL. Download the sample input first when this example uploads a file.
Excel to Protocol Buffers schema API · Python
import os
from pathlib import Path
import requests
endpoint = "https://api.tableconvert.com/v2/convert/excel-to-protobuf"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
}
with open("excel-to-protobuf-input.xlsx", "rb") as source:
files = {**fields, "file": ("excel-to-protobuf-input.xlsx", source)}
response = requests.post(endpoint, headers=headers, files=files, timeout=40)
response.raise_for_status()
Path("excel-to-protobuf.protobuf.txt").write_bytes(response.content)Requires Python 3 and requests. Install it with pip install requests.
Excel to Protocol Buffers schema API · Node.js
import { readFile, writeFile } from "node:fs/promises";
const form = new FormData();
form.set("file", new Blob([await readFile("excel-to-protobuf-input.xlsx")]), "excel-to-protobuf-input.xlsx");
const response = await fetch("https://api.tableconvert.com/v2/convert/excel-to-protobuf", {
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-protobuf.protobuf.txt", 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 proto3 message definition followed by a JSON representation of row data. The combined text is neither protobuf wire encoding nor a standalone compilable .proto file.
This output format does not expose additional options.
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 | Headers become numbered string fields, while data rows are appended as a separate JSON illustration. |
| Mapping rule 3 | Worksheet display values do not provide a complete schema: review field names and types instead of transferring Excel formatting as type metadata. |
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
- Header names become string fields numbered from one.
- Separate the message definition from the appended JSON before using protoc or a protobuf library.
- Validate field identifiers, reserved words and long-term field numbering before using the draft schema.
When to use this API
This conversion in practice
Use a worksheet export as the starting dataset for a protobuf message-schema prototype. Place the intended sheet first, or upload it as a separate workbook; inspect dates and leading-zero identifiers in the extracted values.
Protocol Buffers schema text
Draft a flat string-field message with sample records for an integration prototype.
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.