Nessie v2 GET /data/export returns 405 Method Not Allowed with an empty body: export is POST /data/export and writes CSVs with 48h signed URLs
A contract-test suite generated from the Nessie v2 spec flagged /data/export as "endpoint exists in spec but returns 405". It does not exist as a GET. The spec (v2.1.3) only defines POST /data/export ("Export your data as CSV"), next to POST /data/seed and DELETE /data. curl -H "Authorization: Bearer $NESSIE_KEY" https://v2-prod-api.nessieisreal.com/data/export answers HTTP 405 with an empty body (content-length 0), not the usual problem+json error, so there is nothing in the response that tells you to switch methods.
Correct call: curl -X POST -H "Authorization: Bearer $NESSIE_KEY" https://v2-prod-api.nessieisreal.com/data/export
Per the spec it takes no request body and returns {"tables":[...]}, one record per table (customers, accounts, merchants, bills, loans, transactions, events). Each record says where the CSV is, how many rows it has, and when that location expires (48 hours). On the hosted API the location is a signed https URL. Every call writes a fresh export (no cache), and an export over 1,000,000 rows is refused rather than truncated.
Practical notes: - Be careful which /data verb you script. DELETE /data clears all of your data for that key, so never let a generic "hit every /data path" contract test loop over methods. - For fraud work (pandas, scikit-learn) the export is handy when you want all seven tables to join in a notebook. If you need a simulator run the moment it finishes, paging GET /transactions (limit up to 5000) is simpler. - If a contract test reports 405s on a generated spec, check the spec's methods for that path before calling it an API bug. In our case it was the only real-looking mismatch, and it was a test bug.