Skip to content
Hardcount
Run it locally
Pre-1.0 · one maintainer · Stripe and cards only · no SDKs (client libraries) yet · no production users yet. Docs describe v0.9.1 (29 Oct 2026) · What’s new →

Export subscriptions as CSV

GET
/v1/exports/subscriptions.csv
curl --request GET \
--url http://localhost:8080/v1/exports/subscriptions.csv \
--header 'Authorization: Bearer <token>'

Streams every subscription, newest first, from one consistent snapshot. Columns: id, code, display_name, customer_id, status, billing_time, trial_start_at, trial_end_at, started_at, activated_at, canceled_at, current_billing_period_start, current_billing_period_end, next_billing_at, plan_ids (plan IDs joined with |), created_at.

Audit row, EXPORT_INCOMPLETE marker and formula escaping work as in the customers export.

from
string

Lower bound on created_at, inclusive. RFC 3339 or YYYY-MM-DD.

to
string

Upper bound on created_at, inclusive. RFC 3339 or YYYY-MM-DD (end of that day, UTC).

CSV file (sent as an attachment).

Media typetext/csv
string

from or to is malformed, or to is before from.

Media typeapplication/json
object
error
object
type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string
code
string
message
string
request_id
string
param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
"error": {
"type": "invalid_request_error"
}
}

The export’s audit row could not be written; nothing was sent.

Media typeapplication/json
object
error
object
type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string
code
string
message
string
request_id
string
param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
"error": {
"type": "invalid_request_error"
}
}