Resources
Shapecaster API is organized around discrete resources that are created, retrieved, updated, and deleted. We follow REST semantics. Request bodies are bare JSON — attributes are sent at the top level, with no enveloping wrapper around them. Authorizing a file upload is the single exception, and says so where it appears. Responses are JSON encoded, and we use standard HTTP response codes, authentication, and verbs. Actions to interact with or manipulate that data are detailed on each resource page. To interact with the API, you need a client, which is what a token is issued to.