APIs Reference
Note: This is the APIs reference entry point, and the technical drop-off cliff edge begins here. If you'd like to start from a simpler point, go check out the main docs page!
Zoo provides APIs for building hardware design tools and automations. You can use them to create or edit geometry, convert CAD files, run AI-assisted workflows, and manage the account objects around those systems.
Two of the biggest advantages to Zoo's API offering is offloading remote work and a complementary API ecosystem, where instead of going to use 3 or more different API services from different companies, you can find them all under us, all designed with the same principles and care.
The API documentation is generated through various OpenAPI specification consumers. This specification is produced by our Rust source code as a central source of truth. It enables us to deliver more accurate API documenation to our clients.
Zoo's APIs are organized around REST and Zoo-specific WebSocket application protocols. The REST endpoints use predictable URLs, standard HTTP methods, bearer-token authentication, and JSON request and response bodies.
The root endpoint / returns the OpenAPI specification, which is useful if you want to inspect the schema or generate tooling from it.