Documentation Index
Fetch the complete documentation index at: https://docs.smartcp.org/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
All REST API endpoints are available at:Rate Limits
| Scope | Limit | Period |
|---|---|---|
| /v1/* | 100 requests | 60 sec |
How requests are counted
Requests are effectively limited per source IP address. This means:- Multiple API keys sent from the same public IP still share the same rate-limit bucket.
- A single integration sending traffic through one outbound IP can hit the limit across all
v1endpoints combined. - The limit is not currently partitioned by bearer token or
directoryheader.
Success-response headers
For requests that are accepted, we add standard rate-limit headers to the response:429 Too Many Requests
When the limit is exceeded, the API returns HTTP 429:
Rate-limit headers
Successful responses may include standard rate-limit headers such as:Retry-AfterX-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-Reset
429 responses.
Response Schema
All API responses use a consistent top-level JSON envelope:data to error:
Successful responses
statusis the HTTP status code.datacontains the endpoint payload. It can be a number, string, object, array, ornull.
Error responses
statusis the HTTP status code.errorcontains the error payload. In most cases it is a string.
HTTP Status Codes
- 200 OK for successful reads.
- 201 Created when at least one file was attached successfully.
- 401 Unauthorized when authentication fails.
- 404 Not Found when a route or requested order does not exist.
- 405 Method Not Allowed when the route exists but the HTTP method is wrong.
- 422 Unprocessable Entity for validation failures and for upload requests where no file could be attached.
- 429 Too Many Requests when the shared API limiter is exceeded.
- 500 Internal Server Error for unexpected server-side failures.