The export format configuration determines the structure, encoding, and field selection of mapping result files delivered to your organization. Each organization has a single active format configuration. You can create or replace it using the PUT endpoint at any time, and retrieve the current configuration with GET.Documentation Index
Fetch the complete documentation index at: https://docs.mapping.travel/llms.txt
Use this file to discover all available pages before exploring further.
Both endpoints require authentication. Include your bearer token in the
Authorization header.PUT /api/v1/export-format
Create or replace your organization’s export format configuration. If no configuration exists, one is created. If one already exists, it is fully replaced by the new values.Request body
Output file format. Accepted values:
json, csv, jsonl.List of fields to include in the export. When omitted, all fields are included by default.
Column delimiter for CSV exports. Ignored for JSON and JSONL formats.
Whether to include a header row in CSV exports.
Optional compression for the export file. Accepted values:
gzip, none. Defaults to none.Response
Returns the saved configuration.UUID of the format configuration.
The configured output format.
Fields included in the export.
CSV delimiter character.
Whether CSV exports include a header row.
Compression applied to the export file.
ISO 8601 timestamp of the last update.
Example
GET /api/v1/export-format
Retrieve your organization’s current export format configuration.Response
Returns the current format configuration object if one has been set.UUID of the format configuration.
Output file format (
json, csv, or jsonl).Fields included in the export, if configured.
CSV column delimiter.
Whether CSV exports include a header row.
Compression type applied to export files.
ISO 8601 timestamp of the last configuration update.
Errors
| Status | Description |
|---|---|
404 Not Found | No export format configuration has been set for your organization. Use the PUT endpoint to create one. |