Skip to main content
GET
/
api
/
v1
/
forms
/
{formId}
/
export
Export Submissions
curl --request GET \
  --url https://api.example.com/api/v1/forms/{formId}/export \
  --header 'Content-Type: application/json' \
  --data '
{
  "startDate": "<string>",
  "endDate": "<string>"
}
'
{
  "401": {},
  "403": {},
  "429": {},
  "500": {}
}

​
Authentication

This endpoint requires Clerk authentication. You must be authenticated as the form owner to export submissions.

​
Path Parameters

​
formId
string
required
The unique identifier of the form to export submissions from

​
Query Parameters (GET)

​
startDate
string
Filter submissions created on or after this date (ISO 8601 format: YYYY-MM-DD)
​
endDate
string
Filter submissions created on or before this date (ISO 8601 format: YYYY-MM-DD). The full end date is included

​
Request Body (POST)

Alternatively, you can use the POST method with a JSON body:
​
startDate
string
Filter submissions created on or after this date (ISO 8601 format)
​
endDate
string
Filter submissions created on or before this date (ISO 8601 format)

​
Response

Returns a CSV file download with the following characteristics:

​
File Format

  • Content-Type: text/csv;charset=utf-8
  • Encoding: UTF-8 with BOM (Byte Order Mark) for proper Excel compatibility
  • Filename: {form-name}-submissions.csv (form name is normalized to lowercase with hyphens)

​
CSV Structure

The CSV file includes:
  1. Header Section:
    • Form name and title
    • Generation timestamp
    • Total submission count
    • Date range (if filtered)
    • Empty line separator
  2. Data Section:
    • Column headers (field names from form submissions)
    • Submission rows with the following columns:
      • Submission Date: Formatted as “MMM d, yyyy ‘at’ h:mm a”
      • Form field columns (dynamic based on form schema)
      • email: If provided in submission

​
Data Processing

  • Metadata fields (starting with _) are excluded from export
  • Nested objects are JSON-stringified
  • Submissions are ordered by creation date (most recent first)
  • Empty rows are excluded

​
Rate Limiting

This endpoint is rate limited per user and form combination. The rate limit identifier is: 
export_{userId}_{formId}
When rate limited, you’ll receive:
  • Status: 429 Too Many Requests
  • Headers:
    • X-RateLimit-Limit: Maximum requests allowed
    • X-RateLimit-Remaining: Requests remaining in current window
    • X-RateLimit-Reset: Unix timestamp when limit resets
  • Message: “Rate limit exceeded. Please try again in X seconds.”

​
Cache Control

The export response includes headers to prevent caching: 
Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: 0
This ensures you always receive fresh data when exporting. 
curl -X GET "https://api.mantlz.com/api/v1/forms/form_123/export" \
  -H "Authorization: Bearer YOUR_CLERK_TOKEN" \
  --output submissions.csv

​
CSV Output Example

"Contact Form - Form Submissions"
"Generated on: Mar 4, 2026 at 2:30 PM"
"Total Submissions: 3"
"Date Range: Jan 1, 2024 - Jan 31, 2024"

"Submission Date","name","email","message"
"Jan 15, 2024 at 10:30 AM","John Doe","[email protected]","Hello world"
"Jan 14, 2024 at 3:45 PM","Jane Smith","[email protected]","Test message"
"Jan 13, 2024 at 9:15 AM","Bob Johnson","[email protected]","Another submission"

​
Error Responses

​
401
Unauthorized
User is not authenticated with Clerk
​
403
Forbidden
Form not found or user does not own the form
​
429
Rate Limited
Too many export requests. Wait for the rate limit to reset
​
500
Internal Server Error
Error occurred during export processing
Both GET and POST methods are supported for this endpoint. Use GET for simple exports with query parameters, or POST when you need to send complex date filters in the request body.
The export service automatically handles large datasets and formats the CSV for optimal Excel compatibility, including proper character encoding and BOM markers.

Build docs developers (and LLMs) love

Get started for freeTalk to us