Skip to content
API REFERENCEv2

XML to Protocol Buffers schema API

Prepare proto3 schema and appended JSON sample text from a record-oriented XML export with the TableConvert conversion API. Use direct child-element names as flat fields; XML attributes, namespaces and repeated nested groups are not inferred as equivalent schema types.

REST APIv2 · Direct outputXML → Protocol Buffers schema text1 credits per successful conversion

Try this conversion

Inspect a real sample, preview locally, or send a live request with your own key.

Verified sample
POSThttps://api.tableconvert.com/v2/convert/xml-to-protobuf

Protocol Buffers schema text response

syntax = "proto3";

message MyMessage {
  string id = 1;
  string name = 2;
  string status = 3;
}

[
  {
    "id": "101",
    "name": "Alice",
    "status": "active"
  },
  {
    "id": "102",
    "name": "Bob",
    "status": "inactive"
  }
]

Local previews use no credits and process the first imported table or worksheet.

A successful live request uses 1 credits.

Your key is sent only to the conversion API and is never saved by this page.

Things to check before integrating

Before you integrate

Move required attributes into explicit fields and flatten repeated nested groups before sending XML.

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

Normalize namespace prefixes, quoted identifiers or formatting characters before using headings as destination identifiers.

Code examples

These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.

XML to Protocol Buffers schema API · cURL

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/xml-to-protobuf' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data=<?xml version="1.0" encoding="UTF-8" ?>
<dataset>
  <record><id>101</id><name>Alice</name><status>active</status></record>
  <record><id>102</id><name>Bob</name><status>inactive</status></record>
</dataset>' \
  --output 'xml-to-protobuf.protobuf.txt'

Requires cURL. Download the sample input first when this example uploads a file.

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 importer treats each direct child of the document root as a record and its child elements as fields. It is a record extractor, not a general XML schema or XSLT transformation.

ParameterTypeDefaultDescription
datastring—Inline XML table content. Choose one of data, file or url.
filebinary—Upload a xml file using multipart/form-data.
urlstring—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

CaseBehavior
Mapping rule 1Root-level child records supply rows, and their child element names supply the union of columns.
Mapping rule 2Headers become numbered string fields, while data rows are appended as a separate JSON illustration.
Mapping rule 3Use direct child-element names as flat fields; XML attributes, namespaces and repeated nested groups are not inferred as equivalent schema types.

How the input is read

  • Use a root element containing repeated record elements with child-element fields.
  • Cell values use element textContent; attributes and deep tree structure are not emitted as separate columns.
  • Repeated field names within one record overwrite earlier values; normalize repeating groups first.
  • Review namespace-prefixed names before generating code identifiers or a new schema.

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 record-oriented XML export as the starting dataset for a protobuf message-schema prototype. Move required attributes into explicit fields and flatten repeated nested groups before sending XML.

Protocol Buffers schema text

Draft a flat string-field message with sample records for an integration prototype.

Responses and errors

HTTP statusDescription
200text/plain; charset=utf-8
400Invalid input or conversion parameters.
402Insufficient credits for this request.
403Missing or invalid API key.
413The input exceeds the configured request limit.
415Unsupported input media type.
429Rate limit exceeded.
500The conversion could not be completed.
503The 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 credits

Using 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 overview

References and format specifications

Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.