GET /public/v1/approvals/responses
Changed onList AI-drafted responses to prospect replies (the "Response Ready" approvals). These are the replies Valley drafts once a prospect answers, and they are NOT returned by /public/v1/approvals/messages on any view, which covers first-touch and follow-up drafts only. Workspace admins and owners see every campaign in the workspace; members see only their own. Note that a pending draft is discarded server-side when the prospect sends a newer message, or when the account owner replies manually in LinkedIn, so an item can disappear between polls; approving an id that is already gone returns 404, and approving one that goes stale mid-request returns 409. Treat this as a live queue, not a ledger.
Request
- Base URLhttps://api.joinvalley.co
- AuthAPI key in header x-api-key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Required. "pending" for drafts awaiting review, "sent" for responses already approved and delivered. There is no "approved" or "scheduled" view: approving a response sends it immediately.
Maximum number of records to return (1–100, default 20).
Number of records to skip. Capped at 1,000.
Required. Scope to a specific workspace.
Comma-separated campaign IDs to filter to.
Comma-separated interest levels (e.g. INTERESTED,MIGHT_BE_INTERESTED).
Filter by prospect first or last name.
Only drafts created on or after this date (YYYY-MM-DD).
Only drafts created on or before this date (YYYY-MM-DD).
Sort order by draft created_at. Defaults to newest.
Admin/Owner only: scope to a specific workspace member by user ID.
Response
Default Response
Changes
- warning
deleted the
queryrequest parameterconversationId - info
removed the non-success response with the status
- warning
- info
added the new optional
queryrequest parameterconversationId - info
added the non-success response with the status
- info