Pagination and Errors
Pagination
Section titled “Pagination”List endpoints use offset pagination:
curl "https://sshverify.com/api/v1/ssh/collect/sessions/?offset=0&limit=50" \ -H "x-api-key: <api-key>"List responses include:
| Field | Description |
|---|---|
items | Items for the current page. |
total | Total number of matching items. |
offset | Offset used for this page. |
limit | Limit used for this page. |
has_more | Whether more items are available. |
If limit is omitted, the API uses 100. Values above 100 are capped to 100.
Error shape
Section titled “Error shape”Errors use an application/problem+json response body:
{ "title": "Bad Request", "status": 400, "detail": "Cannot use both timeout and expired_at", "errors": [ { "location": "body.expired_at", "message": "Cannot be used with timeout" } ]}The errors array is optional and is used when the API can point to a specific field or value.
Common status codes
Section titled “Common status codes”| Status | Meaning |
|---|---|
400 | Invalid request, such as using timeout and expired_at together. |
404 | Session or webhook was not found in the API key’s project. |
409 | The requested action conflicts with the session state, such as completing a single-connection session. |
429 | Project rate limit exceeded. |