The Showwcase API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
The Showwcase API utilizes
Cache-First approach. In this approach, when a user requests data from the server, the server first checks if the requested data is available in the cache. If the data is available in the cache, the server returns it immediately to the user without making any additional requests to the database.
|GET||Retrieve information about the REST API resource|
|POST||Create a REST API resource|
|PUT||Update a REST API resource|
|DELETE||Delete a REST API resource or related component|
Most of the lists/item collections are paginated. The parameters that control the pagination are
limit, indicating the desired offset and the items per page values.
limit value is 100.
"error": "You cannot request more than 100 items.",
HTTP status codes
Here's a list of the status codes used in Showwcase API:
New resource created
Request not understood
Invalid API token
Request not allowed
|405||Method not allowed|
Incorrect request method
Old resource permanently unavailable
|415||Unsupported Media Type|
Feature is not enabled
|429||Too Many Requests|
Rate limit has been exceeded
|500||Internal Server Error|
Generic server error
We can’t wait to see what you build! And we’d like to encourage you to build it using these recommended best practices.
Avoid unnecessary fetching
If you are frequently fetching the same data from Showwcase API, we recommend moving the data to your own servers.
Know your limits
All of our products have rate limits to ensure that all customers experience a high level of performance when using our platform.
Did we miss something?
Do you have a favorite best practice you’d like to see added to our list? Please let us know!