> ## Documentation Index > Fetch the complete documentation index at: https://docs.1eye.ai/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve Destination Console > Retrieve Buyers and their latest delivery outcomes for a Destination. Retrieve Buyer records and their latest delivery outcomes for one Destination. The response combines the existing canonical Buyer object with Destination-specific delivery information. ```text theme={null} GET /v1/destinations/{destination_id}/console ``` ## Authentication All requests require a workspace API key: ```http theme={null} Authorization: Bearer 1eye_live_xxxxxxxxx ``` The examples use `$API_KEY` for your API key. The key determines the workspace; you do not supply a workspace ID. See [Authentication](https://docs.1eye.ai/api-reference/auth.md). ## Path parameter | Parameter | Type | Description | | - | - | - | | `destination_id` | string | Public Destination ID (`des_`). | ## Query parameters | Parameter | Type | Description | | - | - | - | | `status` | string | Optional filter: `pushed`, `pending`, or `failed`. Omit for all states. | | `limit` | integer | Results per page. Default: `100`. Range: `1–1000`. | | `cursor` | string | Opaque cursor returned by the previous page. | `status=all`, `sort_by`, and `sort_order` are not supported. ## Request Retrieve failed deliveries: ```bash theme={null} curl "https://api.1eye.ai/v1/destinations/des_123456789012345678/console?status=failed&limit=100" \ -H "Authorization: Bearer $API_KEY" ``` ## Response **200 OK** This fictional example has one failed Buyer among 20 Buyers in the complete Console. The filter restricts `data`; the counts still describe the whole Console. ```json theme={null} { "total": 20, "pushed": 18, "pending": 1, "failed": 1, "data": [ { "buyer": { "id": "buy_123456789012345678", "client_id": "wor_123456789012345678", "contact_info": { "name": { "first": "Jane", "middle": "", "last": "Doe" }, "role": { "title": "VP of Sales", "function": "sales", "seniority": "vp", "start_date": "" }, "email": { "work": "jane@example.com", "is_valid": true }, "phone": { "mobile": "+14155550123", "is_valid": true }, "social": { "linkedin": "https://www.linkedin.com/in/janedoe", "twitter": "", "github": "", "facebook": "", "linkedin_followers": 0, "is_linkedin_valid": true }, "location": { "city": "San Francisco", "state": "California", "country": "United States", "postal_code": "" }, "photo_url": "https://example.com/photo.jpg", "is_persona": true, "persona_id": "per_123456789012345678", "persona_name": "Sales", "persona_reasoning": "The contact's role and seniority align with the Sales persona." }, "company_info": { "name": "Acme", "website": "acme.com", "logo": "https://example.com/logo.png", "industries": [ "computer software" ], "employee_count": 250, "founded_year": 2018, "annual_revenue": 50000000, "company_type": "private", "social": { "linkedin": "https://www.linkedin.com/company/acme", "twitter": "", "facebook": "" }, "location": { "street_address": "123 Market St", "city": "San Francisco", "state": "California", "postal_code": "94105", "country": "United States" }, "total_funding": 25000000, "latest_funding_stage": "", "latest_funding_round_date": "", "is_icp": true, "icp_id": "icp_123456789012345678", "icp_name": "B2B-SCALEUP", "icp_reasoning": "The company matches the workspace's B2B Scaleup ICP." }, "hems": [], "target_lists": [ { "id": "lis_123456789012345678", "name": "High-Intent Data Buyers" } ], "signal_count": { "total": 3, "website": 2, "market": 1, "linkedin": 0 }, "attribution": { "type": "paid", "source": "google_ads", "source_name": "Google Ads", "source_logo": "https://example.com/google-ads.png" }, "first_signal_id": "sig_123456789012345678", "first_signal_type": "website", "first_signal_trigger": "visited_page", "last_signal_id": "sig_987654321098765432", "last_signal_type": "market", "last_signal_trigger": "evaluated_competitor", "created_at": "2026-09-20T18:27:36Z", "updated_at": "2026-09-25T19:03:28Z" }, "delivery": { "status": "failed", "reason": "Salesforce rejected the record: required field missing.", "executed_at": "2026-10-20T18:00:00Z" } } ], "pagination": { "next_cursor": null } } ``` All names, domains, identifiers, amounts, URLs, and timestamps in these examples are illustrative. ## Response fields | Field | Type | Description | | - | - | - | | `total` | integer | Unique Buyers represented in the complete Console. | | `pushed` | integer | Buyers whose latest recorded delivery succeeded. | | `pending` | integer | Buyers whose latest delivery state is pending. | | `failed` | integer | Buyers whose latest delivery attempt failed. | | `data` | array | Current page of Buyer and delivery records. | | `pagination.next_cursor` | string or null | Continuation cursor, or `null` at the end. | ### Console record Each `data` item contains `buyer` and `delivery`: * `buyer` preserves the same canonical public object returned by [Retrieve a Buyer](https://docs.1eye.ai/api-reference/retrieve-a-buyer.md). * `delivery` contains `status`, `reason`, and `executed_at` for that Buyer at this Destination. | Delivery field | Type | Description | | - | - | - | | `status` | string | `pushed`, `pending`, or `failed`. | | `reason` | string or null | Sanitized explanation from the underlying delivery record. | | `executed_at` | datetime or null | UTC execution timestamp, or `null` when not executed. | ### Delivery states A successful delivery may have no reason: ```json theme={null} { "status": "pushed", "reason": null, "executed_at": "2026-10-20T18:00:00Z" } ``` A queued delivery can include a pending explanation: ```json theme={null} { "status": "pending", "reason": "Queued for HubSpot push", "executed_at": null } ``` Failure messages vary by provider. A generic message may not contain enough information to diagnose the cause; inspect the Destination in the 1eye Console for further context. ## Counts and latest state The Console returns one row per unique Buyer using its latest recorded delivery state. Multiple attempts or retries do not produce separate public rows for the same Buyer. Counts remain unchanged when applying a `status` filter or moving between pages. If the selected filter has no matches, `data` is empty even when the overall counts are nonzero. If the entire Console is empty, all counts are zero. ## Pagination Keep the Destination ID and status filter unchanged when passing a cursor. The cursor is also bound to the workspace, endpoint, and fixed ordering. `limit` may change between pages. A mismatched or malformed cursor returns `400 invalid_cursor`. ```bash theme={null} curl "https://api.1eye.ai/v1/destinations/des_123456789012345678/console?status=failed&limit=100&cursor=YOUR_CURSOR" \ -H "Authorization: Bearer $API_KEY" ``` Continue until `pagination.next_cursor` is `null`. Delivery processing is continuous, so counts can change between requests. ## Resource access An inaccessible, missing, or deleted Destination returns 404. This endpoint does not retry deliveries, start workflows, or expose provider credentials and raw execution logs. ## Errors | Status | Error code | Description | | - | - | - | | 400 | `invalid_parameter` | A request field or query parameter is invalid. | | 400 | `invalid_cursor` | The cursor is invalid or belongs to a different query. | | 404 | `not_found` | The Destination does not exist or is inaccessible. | | 401 | `authentication_error` | The API key is missing, invalid, or revoked. | | 403 | `permission_denied` | The key does not have permission for this operation. | | 429 | `rate_limit_exceeded` | The workspace API rate limit was exceeded. | | 500 | `internal_error` | An unexpected server error occurred. | | 503 | `service_unavailable` | The service is temporarily unavailable. | Errors use the standard [error envelope](https://docs.1eye.ai/api-reference/errors.md). Use `request_id` when contacting support. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.