Past deliverability checks
Past checks for this account, newest first, within what was scanned. Each request reads a bounded part of the account's history, in storage order rather than by date, and sorts only what it read, so on an account with a long history these are not necessarily the newest checks overall. truncated: true says that happened.
Request
- Base URL: https://api.kawaa.com
- URL: https://api.kawaa.com/v1/deliverability/checks
- Auth: one of:
- API key in header X-Api-Key
- HTTP bearer
- OAuth 2 (authorization code, authorization URL https://api.kawaa.com/oauth/authorize, token URL https://api.kawaa.com/oauth/token, scopes: deliverability:read)
Query parameters
Page size: 1 to 100, defaulting to 20. Unlike the strict limit on other list routes, this one CLAMPS rather than refusing: it reads the raw query value as a number (so 1e2 is 100, not 1), truncates a fraction, caps anything above 100 at 100, and falls back to 20 for a malformed, zero or negative value.
Typed as a plain string with no numeric constraint for that reason: limit=abc is a request this route accepts and normalizes, and type: number made a generated client refuse it locally. Compare GET /v1/jobs/{id}, which also accepts numeric notation such as 1e2 but refuses malformed, zero, fractional, negative, or out-of-range values instead of clamping. The two routes differ and the schemas say so.
Response
Previous checks, newest first.
Changes
No recorded changes to this operation across all 1 revision of this API.