> ## Documentation Index > Fetch the complete documentation index at: https://voyant.travel/docs/llms.txt > Use this file to discover all available pages before exploring further. # Live package offers for a product > Fetch live (Voyant Connect) package offers for a sourced product across a date range and party. ## OpenAPI ````yaml /api-specs/platform-admin.json post /v1/admin/catalog/package-offers openapi: 3.1.0 info: title: Voyant Admin API version: 1.0.0 description: >- The staff-facing /v1/admin/* REST API exposed by the framework modules in your deployed Voyant app. Authenticate with a staff session or API token. The server URL is your own app domain, not api.voyant.travel. servers: - url: https://{operatorDomain} variables: operatorDomain: default: app.example.com description: The domain of your deployed Voyant operator app. security: - bearerAuth: [] tags: - name: Accommodations description: >- Accommodation sourced-content detail authoring. Mounted at /v1/admin/accommodations. - name: Action ledger description: >- Auditable action log with approvals, delegations, reversals and relay outbox. - name: Bookings description: >- Booking lifecycle, travelers, items, notes, documents and per-booking action-ledger. - name: Catalog description: >- Catalog search and the booking engine (quote, book, drafts, holds, orders) plus live sourced package/cruise pricing, mounted at /v1/admin/catalog. - name: Charters description: >- Yacht charter catalog: products, voyages, suites, schedules, yachts, per-suite and whole-yacht quotes/bookings and MYBA contracts. Mounted at /v1/admin/charters. - name: CRM description: >- Relationships domain: people, organizations, contacts, addresses, notes, documents, activities, custom fields and customer signals. Mounted at /v1/admin/relationships. - name: Cruises description: >- Cruise catalog authoring: cruises, voyage groups, sailings, prices, ships/decks/categories/cabins, enrichment programs, search index and bookings. Mounted at /v1/admin/cruises. - name: Distribution description: >- Sales-channel distribution: channels, contracts, commission rules, product mappings, booking links, inventory allotments, and settlement runs, mounted at /v1/admin/distribution. - name: Finance description: >- Invoices, credit notes, payments, payment schedules, guarantees, payment sessions, supplier invoices, tax reference data, and finance reports (admin surface, mounted at /v1/admin/finance). - name: Invitations description: >- Staff/agent identity records: named contacts, contact points and addresses, including entity-scoped variants. Mounted at /v1/admin/identity. - name: Legal description: >- Contracts, contract templates, signatures, policies, policy versions, policy acceptances, and legal terms (admin surface, mounted at /v1/admin/legal). - name: Notifications description: >- Notification templates, deliveries, reminder rules/stages/channels, reminder runs and document dispatch. Mounted at /v1/admin/notifications. - name: Operations description: >- Operational supply: availability rules/slots, resources/pools, ground transport and facilities. - name: Products description: >- Owned product catalog authoring: products, options, itineraries, media, brochures, types, categories, and destinations, mounted at /v1/admin/products. - name: Promotions description: >- Promotional offers with discount, scope, conditions, and validity windows, mounted at /v1/admin/promotions. - name: Quotes description: >- Sales quotes, quote versions, lines, pipelines and stages plus proposal send/snapshot. Mounted at /v1/admin/quotes and /v1/admin/quote-versions. - name: Settings description: >- Operator-tenant settings: profile, payment instructions, payment defaults and combined operator settings. Mounted at /v1/admin/settings. - name: Storefront description: Operator-facing storefront configuration. Mounted at /v1/admin/storefront. - name: Trips description: >- Multi-component trip envelopes: composition, pricing, reservation, checkout and snapshots. - name: Workflow runs description: Read-only workflow run inspection plus trigger, rerun and resume. paths: /v1/admin/catalog/package-offers: post: tags: - Catalog summary: Live package offers for a product description: >- Fetch live (Voyant Connect) package offers for a sourced product across a date range and party. operationId: searchCatalogPackageOffersAdmin requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CatalogPackageOffersRequest' responses: '200': description: Offers content: application/json: schema: $ref: '#/components/schemas/CatalogPackageOffersResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '500': $ref: '#/components/responses/ServerError' x-codeSamples: - lang: bash label: cURL source: |- curl --request POST \ --url https://app.example.com/v1/admin/catalog/package-offers \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --data '{ "productId": "", "departureDateFrom": "2026-07-01", "departureDateTo": "2026-07-31", "nights": { "min": 123, "max": 123 }, "adults": 2, "children": 123, "childrenAges": [ 123 ], "boards": [ "" ], "limit": 123 }' - lang: javascript label: Node source: >- const response = await fetch("https://app.example.com/v1/admin/catalog/package-offers", { method: "POST", headers: { "Content-Type": "application/json", "Authorization": "Bearer " }, body: JSON.stringify({ "productId": "", "departureDateFrom": "2026-07-01", "departureDateTo": "2026-07-31", "nights": { "min": 123, "max": 123 }, "adults": 2, "children": 123, "childrenAges": [ 123 ], "boards": [ "" ], "limit": 123 }), }); const data = await response.json(); - lang: python label: Python source: |- import requests response = requests.post( "https://app.example.com/v1/admin/catalog/package-offers", headers={ "Authorization": "Bearer " }, json={ "productId": "", "departureDateFrom": "2026-07-01", "departureDateTo": "2026-07-31", "nights": { "min": 123, "max": 123 }, "adults": 2, "children": 123, "childrenAges": [ 123 ], "boards": [ "" ], "limit": 123 } ) data = response.json() components: schemas: CatalogPackageOffersRequest: type: object required: - productId - departureDateFrom - departureDateTo properties: productId: type: string minLength: 1 departureDateFrom: type: string example: '2026-07-01' departureDateTo: type: string example: '2026-07-31' nights: $ref: '#/components/schemas/CatalogNights' adults: type: integer default: 2 children: type: integer childrenAges: type: array items: type: integer boards: type: array items: type: string limit: type: integer maximum: 200 CatalogPackageOffersResponse: type: object properties: product: type: object additionalProperties: true offers: type: array items: type: object additionalProperties: true retryable: type: boolean source: type: object properties: connectionId: type: string nullable: true ref: type: string nullable: true CatalogNights: type: object properties: min: type: integer max: type: integer ApiError: type: object required: - error properties: error: type: string description: Human-readable error message. code: type: string description: >- Stable, machine-readable error code (e.g. invalid_request, unauthorized, forbidden). Absent for unmapped 500s. requestId: type: string description: >- Correlation id for this request. Also returned in the X-Request-Id response header. details: type: object additionalProperties: true description: >- Optional structured context. Validation errors (400) include `issues` and `fields` from the failed schema. responses: BadRequest: description: >- The request was malformed or failed schema validation (`code: invalid_request`). headers: X-Request-Id: description: >- Correlation id for this request, echoed on every response including errors. schema: type: string content: application/json: schema: $ref: '#/components/schemas/ApiError' Unauthorized: description: 'Authentication is missing or invalid (`code: unauthorized`).' headers: X-Request-Id: description: >- Correlation id for this request, echoed on every response including errors. schema: type: string content: application/json: schema: $ref: '#/components/schemas/ApiError' Forbidden: description: >- The caller is authenticated but not permitted on this surface or lacks the required scope (`code: forbidden`). headers: X-Request-Id: description: >- Correlation id for this request, echoed on every response including errors. schema: type: string content: application/json: schema: $ref: '#/components/schemas/ApiError' ServerError: description: >- An unexpected error occurred. The `X-Request-Id` header identifies the failed request. headers: X-Request-Id: description: >- Correlation id for this request, echoed on every response including errors. schema: type: string content: application/json: schema: $ref: '#/components/schemas/ApiError' securitySchemes: bearerAuth: type: http scheme: bearer description: Staff session or API token issued by your Voyant app. ````