Export coverage as CSV

GET/workspaces/{workspace}/evidence/export

Downloads a CSV an auditor can open: every requirement of every framework you follow, whether it’s met, and the evidence, dates, policies and owner behind it.

Authentication

Send an API token as a bearer token. This endpoint needs a read token, made by any member of the workspace. Create one in My account → API tokens; see scopes and roles.

Authorization: Bearer 42|bynh_pat_•••••••Header

Path parameters

workspacestringRequired
Your workspace slug, e.g. dokan.

Response

200 OK

text/csv; charset=UTF-8 with a UTF-8 BOM, filename {workspace-name-slug}-evidence-YYYY-MM-DD.csv. Columns (English): Framework, Requirement, Title, Status, Evidence, Last collected, Next review, Policies, Owner, What’s missing. Status is “Met” or “Needs evidence”. Header and values follow the reader’s language. Cells starting with = + - @ are prefixed to stop formula injection.

Rate limits

This endpoint counts toward your general limit of 120 requests a minute and its own limit of 10 a minute. Its own limit answers 429 without Retry-After; wait and try again.

Errors

401The token is missing, wrong, revoked or expired.

404The token belongs to another workspace, or its owner is no longer a member.

429More than 10 exports a minute (“Too many requests. Wait a minute, then try again.”).

Every error is JSON with a message. See Errors.

Next →List requirements you can map

curl -OJ "https://api.bynh.io/api/v1/workspaces/dokan/evidence/export" \
  -H "Authorization: Bearer $BYNH_TOKEN" \
  -H "Accept: application/json"

Response200 OK

File

The file itself, with its name in Content-Disposition.

Examples use Dokan, a sample workspace. Responses are shortened where lists are long.