> ## Documentation Index > Fetch the complete documentation index at: https://docs.apostra.com/llms.txt > Use this file to discover all available pages before exploring further. # List my asks > Everything the authenticated customer is waiting on Scope3 for, in one list. Read-only and scoped to the caller's own account; there is no customer parameter. `statusKey` uses the same customer-safe vocabulary for every kind: `received`, `accepted`, `in_progress`, `done`, or `closed`. Internal workflow states and work-item identifiers never appear. Closing an issue or merging a pull request does not close a support, product, or commercial ask: explicitly linked work must appear in a verified production release. Supply and integration asks may also finish from their own customer-visible live-state evidence. Asks completed through a verified release remain observable for 90 days with their customer-safe resolution. When `hasMore` is true, pass `nextCursor` back as `cursor` to read the next page. When a source cannot be read, its kind appears in `unavailableKinds` so a degraded response is never mistaken for an empty list. ## OpenAPI ````yaml /v2/buyer-api-v2.yaml get /asks openapi: 3.0.0 info: title: Scope3 Buyer API version: 2.0.0 description: |- REST API for advertisers to manage advertisers, campaigns, and reporting. ## Authentication All endpoints require a Bearer token in the Authorization header: ``` Authorization: Bearer your-api-key ``` ## Base URL `https://api.interchange.io/api/v2/buyer` ## For AI Agents AI agents can use the MCP endpoint at `/mcp/v2/buyer` with three tools: - `initialize`: Start an MCP session - `api_call`: Make REST API calls - `ask_about_capability`: Learn about API features servers: - url: https://api.interchange.io/api/v2/buyer description: Production server security: [] tags: - name: Signup description: Request reviewed access to Interchange - name: Account description: Account management, service tokens, and preferences - name: Asks description: >- What you are waiting on Scope3 for — support, product, and supply asks in one list - name: Advertisers description: Manage advertisers - name: Product Discovery description: Discover and select products - name: Campaigns description: Manage advertising campaigns - name: Creatives description: Build, manage, and sync campaign creatives via AdCP Creative Protocol - name: Reporting description: Access performance metrics - name: Event Sources description: >- Manage event source configurations and log conversion/marketing events for attribution - name: Property Lists description: Validate property lists against AAO registry - name: Sales Agents description: View and connect sales agents - name: Measurement description: Measurement sources, records, context, and freshness - name: Syndication description: Syndicate resources to ADCP agents - name: Tasks description: Track async operation status - name: Buyer Billing description: >- Consolidated invoicing for buyers — invoices and pending invoice items issued by Scope3 across the buyer customer. - name: MCP description: Model Context Protocol endpoints for AI agents paths: /asks: servers: - url: https://api.interchange.io/api/v2 description: Production server get: tags: - Asks summary: List my asks description: >- Everything the authenticated customer is waiting on Scope3 for, in one list. Read-only and scoped to the caller's own account; there is no customer parameter. `statusKey` uses the same customer-safe vocabulary for every kind: `received`, `accepted`, `in_progress`, `done`, or `closed`. Internal workflow states and work-item identifiers never appear. Closing an issue or merging a pull request does not close a support, product, or commercial ask: explicitly linked work must appear in a verified production release. Supply and integration asks may also finish from their own customer-visible live-state evidence. Asks completed through a verified release remain observable for 90 days with their customer-safe resolution. When `hasMore` is true, pass `nextCursor` back as `cursor` to read the next page. When a source cannot be read, its kind appears in `unavailableKinds` so a degraded response is never mistaken for an empty list. operationId: listAsks parameters: - in: query name: limit schema: default: 10 description: >- Maximum asks to return, ordered by the most recent customer-visible update. type: integer minimum: 1 maximum: 25 description: >- Maximum asks to return, ordered by the most recent customer-visible update. - in: query name: cursor schema: description: Opaque cursor returned by the previous ask-list response. type: string minLength: 1 maxLength: 512 description: Opaque cursor returned by the previous ask-list response. responses: '200': description: List my asks content: application/json: schema: $ref: '#/components/schemas/AsksResponse' '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearerAuth: [] components: schemas: AsksResponse: type: object properties: generatedAt: type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ totalCount: type: integer minimum: 0 maximum: 9007199254740991 requests: type: array items: type: object properties: id: type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ isActive: type: boolean isResolved: type: boolean kind: nullable: true type: string enum: - support - product - supply - integration - commercial title: type: string blockedCustomerAction: nullable: true type: string statusKey: type: string enum: - received - accepted - in_progress - done - closed statusLabel: type: string statusDescription: type: string nextUpdateAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ isCustomerBlocked: nullable: true type: boolean createdAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ updatedAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ resolvedAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ disposition: type: string enum: - in_flight - awaiting_requester - confirmed_resolved - accepted - disputed - withdrawn requester: type: object properties: state: type: string enum: - none - confirmed_resolved - accepted - still_blocked - withdrawn priority: nullable: true type: string enum: - low - medium - high - urgent note: nullable: true type: string updatedAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ required: - state - priority - note - updatedAt additionalProperties: false resolution: nullable: true type: object properties: releaseVersion: type: string minLength: 1 releasedAt: type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ whatChanged: type: string minLength: 1 requesterAction: nullable: true type: string outcome: type: string enum: - change - no_change delivery: type: object properties: state: type: string enum: - pending - delivered - failed channel: nullable: true type: string receipt: nullable: true type: string attempts: type: integer minimum: 0 maximum: 9007199254740991 deliveredAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ required: - state - channel - receipt - attempts - deliveredAt additionalProperties: false confirmationState: type: string enum: - in_flight - awaiting_requester - confirmed_resolved - accepted - disputed - withdrawn required: - releaseVersion - releasedAt - whatChanged - requesterAction - outcome - delivery - confirmationState additionalProperties: false required: - id - kind - title - blockedCustomerAction - createdAt - updatedAt - resolvedAt additionalProperties: false unavailableKinds: type: array items: type: string enum: - support - product - supply - integration - commercial hasMore: type: boolean nextCursor: type: string minLength: 1 supplyActions: nullable: true type: array items: type: object properties: subjectName: nullable: true type: string classification: type: string status: type: string proposedAt: nullable: true type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ required: - subjectName - classification - status - proposedAt additionalProperties: false required: - generatedAt - totalCount - requests additionalProperties: false ErrorResponse: type: object properties: data: type: string nullable: true enum: - null error: $ref: '#/components/schemas/ApiError' required: - data - error additionalProperties: false description: Standard error response ApiError: type: object properties: code: type: string description: Machine-readable error code message: type: string description: Human-readable error message field: description: Field path associated with the error type: string details: description: Additional error context type: object additionalProperties: {} required: - code - message additionalProperties: false description: Structured error object securitySchemes: bearerAuth: type: http scheme: bearer description: API key or access token ````