Export copy

KopiMark is where copy is made; your codebase or CMS is where it lives. Exports are how you bridge the two. You can export manually as a download, or — on the right plan — pull live from KopiMark’s read API.

Export formats

KopiMark exports in three formats. Pick whichever your codebase already speaks:

• JSON — best for most product codebases. Keys map to text node ids (or your custom export keys), values are the localised strings.
• CSV — best for handing copy to non-engineers or for spreadsheet review.
• XML — best for some legacy localisation pipelines.

Manual export (every plan)

That’s it for the manual flow. You can filter the export to only include nodes in specific statuses — usually Approved or Shipped — so drafts don’t leak into your codebase.

API export (Team and Business plans)

If you’d rather pull live, every project has a read-only API endpoint that returns the same payload. Your build script can fetch it on every deploy.

Generate a token

The Developer page shows the live endpoint URL with your current filters baked in (format, pretty-print, flat shape, language) — copy that as the base URL for your client.

Use it from a build

The endpoint accepts your token as a bearer header. Hit it the same way you’d hit any read-only JSON API; cache it however your build expects.

We’ve kept the API minimal on purpose. There’s a more detailed write-up in API and developer tokens.

Status-filtered exports

The most common mistake teams make on their first export is shipping copy that’s still in Draft. Two ways to avoid it:

• Filter by status at export time. The download dialog lets you pick which statuses count.
• Only the last status counts as “shipped”. Some teams configure their status list with Shipped (or Approved) as the final state, and export only that one.

Either pattern works. The export defaults to all statuses, so an explicit filter is wise.

See also

• API and developer tokens
• Statuses and approvals
• Plans and limits