Data export format
The JSON returned by Account → Export contains every row scoped to your user. Top-level shape:
{
"schema_version": 1,
"exported_at_unix": 1748383200,
"user": { ... },
"addresses": [ ... ],
"messages": [ ... ],
"attachments": [ ... ],
"api_keys": [ ... ],
"audit_log": [ ... ],
"digest_schedules": [ ... ]
}
Fields
user
The users row, minus internal-only columns (signup_ip, signup_asn, signup_ua). If you need those, request via support@inboxy.net — they are GDPR-personal data we will furnish on request, but rarely useful and we keep them out of the standard download.
addresses
One entry per inboxy_addresses row. Includes retired addresses (status: "retired").
messages
Every message ever received on your aliases. Includes metadata, classification, summary, urgency, and read state.
Raw body bytes are not inline. They live in R2 and can be fetched via the API at GET https://api.inboxy.net/v1/messages/:id/raw using any read-scope API key. We exclude them inline because (a) they can be megabytes each and (b) the JSON would be unwieldy. A future export format may bundle them as .eml files in a tarball — let us know if you would use that.
attachments
One entry per attachments row, scoped to your messages. The r2_key is omitted; fetch the actual blob via the API at GET /v1/attachments/:id.
api_keys
Includes hashes only — never plaintext. Useful for an audit of "which keys exist, when minted, when last used, when revoked."
audit_log
Every administrative action against your account.
digest_schedules
Your daily digest configuration (if any).
Reading the export
Any JSON reader works. For inspection: jq '.messages | length' to count messages, jq '.addresses[] | .local_part' to list aliases.
Schema versioning
The schema_version field will bump when the shape changes. v1 is the v0.3 launch shape and will not be removed — a future v2 will be additive (new fields) until at least the next major migration. Versions before any breaking change get a 90-day deprecation notice via the help → status feed.
Still need help? support@inboxy.net