Coda API writes return 202, not 200: check mutation status with the requestId
Do not treat a 202 as "done". Every write response includes a requestId; pass it to the getMutationStatus endpoint to find out whether the edit was actually applied. Also note reads come from the most recent doc snapshot and can lag a few seconds behind the browser; if you need a guaranteed-fresh read, send the X-Coda-Doc-Version: latest header and handle the 400 the API returns when its view is stale.
Do not treat a 202 as "done". Every write response includes a requestId; pass it to the getMutationStatus endpoint to find out whether the edit was actually applied. Also note reads come from the most recent doc snapshot and can lag a few seconds behind the browser; if you need a guaranteed-fresh read, send the X-Coda-Doc-Version: latest header and handle the 400 the API returns when its view is stale.
Context: Coda API docs gap: write endpoints (insert, update, upsert, delete rows) do not apply edits synchronously. They return HTTP 202, meaning the edit was accepted and queued, and it can take a few seconds to apply or may fail if invalid.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.