> ## Documentation Index
> Fetch the complete documentation index at: https://offergrid.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Find available offers for an address

> Given a service address, returns every offer your reseller team can sell at that location. Coverage is evaluated against each offer’s availability rules — postal codes and active market areas (including state-wide and city-level coverage) — and provider visibility settings (all resellers, preferred resellers, or selected resellers). This is the same availability logic used by shareable checkout links, exposed as a dedicated address-driven endpoint. Results are returned both as a flat list and grouped by category for checkout UIs.



## OpenAPI

````yaml https://api.offergrid.io/openapi-reseller post /reseller/availability
openapi: 3.0.0
info:
  title: OfferGrid API
  description: >-
    **Reseller API** - Browse service catalog and place orders on behalf of
    customers.


    As a reseller, you can:

    - Browse available service offerings from providers

    - Filter offers by category, price, location, and search terms

    - View detailed offer information including pricing and features

    - Place orders for customers (single or multi-provider orders)

    - Track order status and fulfillment progress

    - Cancel pending orders
  version: '1.0'
  contact: {}
servers:
  - url: https://api.offergrid.io
    description: Production
  - url: http://localhost:3000
    description: Local development
security: []
tags:
  - name: reseller-catalog
    description: 'Reseller: Browse available service offerings'
  - name: reseller-availability
    description: 'Reseller: Find offers available at a service address'
  - name: reseller-orders
    description: 'Reseller: Place and manage orders'
  - name: reseller-customers
    description: 'Reseller: Manage customers and leads'
  - name: reseller-links
    description: 'Reseller: Manage shareable customer links'
paths:
  /reseller/availability:
    post:
      tags:
        - reseller-availability
      summary: Find available offers for an address
      description: >-
        Given a service address, returns every offer your reseller team can sell
        at that location. Coverage is evaluated against each offer’s
        availability rules — postal codes and active market areas (including
        state-wide and city-level coverage) — and provider visibility settings
        (all resellers, preferred resellers, or selected resellers). This is the
        same availability logic used by shareable checkout links, exposed as a
        dedicated address-driven endpoint. Results are returned both as a flat
        list and grouped by category for checkout UIs.
      operationId: ResellerAvailabilityController_findAvailable
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CheckAvailabilityDto'
      responses:
        '200':
          description: Offers available at the given address
      security:
        - api-key: []
components:
  schemas:
    CheckAvailabilityDto:
      type: object
      properties:
        address:
          description: Service address to check availability for
          allOf:
            - $ref: '#/components/schemas/AddressDto'
        category:
          type: string
          enum:
            - internet
            - television
            - security
            - energy
            - insurance
            - other
          description: Only return offers in this service category
          example: internet
        minPrice:
          type: number
          description: Minimum monthly price
          example: 0
        maxPrice:
          type: number
          description: Maximum monthly price
          example: 100
      required:
        - address
      title: Find Available Offers Request
    AddressDto:
      type: object
      properties:
        street:
          type: string
          example: 123 Main Street
        unit:
          type: string
          example: Unit 205
        city:
          type: string
          example: Austin
        state:
          type: string
          example: TX
        zipCode:
          type: string
          example: '78701'
        country:
          type: string
          example: US
          default: US
      required:
        - street
        - city
        - state
        - zipCode
        - country
      title: Address
  securitySchemes:
    api-key:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Team API key for authentication. Your team role
        (provider/reseller/hybrid) determines which endpoints you can access.

````