Clarify APIGet CLI sign-in settings
Returns the OAuth 2.0 device flow settings a command-line client uses to sign a user in. The response is plain JSON, not a JSON:API document, and the endpoint needs no authentication.
Response Body
application/json
curl -X GET "https://example.com/auth/cli"{ "client_id": "client_01HXYZACMEEXAMPLE0000000000", "device_authorization_endpoint": "https://api.workos.com/user_management/authorize/device", "token_endpoint": "https://api.workos.com/user_management/authenticate"}List API keys
Returns API keys as a JSON:API list with `links` and `meta`, in one page. Requires a user access token. Admins see every personal and workspace key, and members see only their own personal keys. Secrets are never returned.
List campaign recipients
Returns the people enrolled in a campaign as an offset-paginated JSON:API collection, each with their per-recipient engagement — whether they opened, clicked, replied, or unsubscribed, and when each last happened. Filter by engagement with `filter[event]` (for example `filter[event]=clicked` to build a retargeting audience), by delivery state with `filter[status]`, or by name/email with `filter[q]`. Recipients are collapsed to one row per person, preferring their active run.