API
The API is what the browser and the plugin both call. Same keys, same quota, same files out.
- Authentication
- Choosing an endpoint: when to use sync, async or batch
- Artifacts: the certificate, DXF and GeoPackage, and the signature that makes them worth having
- Errors: every type the service returns
The exhaustive per-route reference is generated from the
same schema the service publishes, regenerated by task docs:schema so it
documents what the repo holds rather than whatever is deployed.
The sandbox
Section titled “The sandbox”Every account gets an east_test_ key beside its live one. A test key walks
every route and gets a fixture back: no model call, no usage row, no meter
event, no quota and no rate limit.
The fixture ships without a signature and is re-attested when it is served, so certificate post-back works in the sandbox against any deployment. What it returns describes the fixture deed rather than the document you sent: the bytes you upload are read only to compute the SHA-256 on the certificate.