Export data and answer GDPR requests

Export people for an audit or another system, answer a person's access request, and erase a former employee's personal data, all through the API.

Export people as CSV#

org.people.export_csv returns a CSV file as text: names, work email and phone, status, start date, the current job (title, team, manager, location, legal entity, employment type, FTE, contract terms) and active custom fields, as of a day.

curl https://api.bizisy.com/v1/org/people.export_csv \
  -H "Authorization: Bearer $BIZISY_API_KEY" -H "Content-Type: application/json" \
  -d '{"status": "all", "delimiter": ";"}' | jq -r .data.csv > people.csv

delimiter: ";" suits Excel in most of Europe. Private details (include_private) are added only in the app by owners, admins and HR, never through a key. Pay is never in this file.

For the org chart as a list (reporting order, levels, report counts), use org.chart.export; for monthly headcount, joiners, leavers and turnover, org.reports.headcount.

Answer an access request#

Under the GDPR, a person may ask for a copy of the data you hold about them.

• Your own data: org.me.export_data with a Me key returns everything Bizisy holds about you as JSON: profile, photo, documents shared with you (with 5-minute download links), job and pay history, invites, logins, API keys (names and dates, never secrets), Activity, checklists, approvals and recent webhook deliveries about you.
• Someone else's: org.people.export_data is the same for any person, for owners, admins and HR. It contains private data, so it runs in the web app (People → the person → Download personal data); through a key it works only for yourself.

Erase a former employee#

When someone has left and you no longer need their data, org.people.erase anonymises them: names, contact, private and custom fields, payroll identifiers, photo, documents, pay history, checklists and approval requests are removed or cleared; job rows are kept, anonymised, for history; any login is disabled. It's irreversible, for owners and admins only, and only once every job row has ended.

curl "https://api.bizisy.com/v1/org/people.erase?dry_run=true" \
  -H "Authorization: Bearer $BIZISY_API_KEY" -H "Content-Type: application/json" \
  -d '{"person_id": "p9"}'

Preview first, then commit. Bizisy sends person.erased to your webhooks: delete what your systems keep about them too.

The whole company#

The full company export (Settings → Data & privacy → Download all company data, owners and admins) and closing the company (Settings → Close account, owners) happen in the web app. They aren't in the API.