flightpowers-com Account API

openapi: 3.2.0
info:
  title: FlightPowers Travel Data Account API
  version: 1.1.0
  summary: Real-time Google Flights fares and Booking.com hotel prices as clean JSON.
  description: 'Live flight and hotel prices, and the context to judge them. Two data products behind one host:


    - **Flights**: live Google Flights searches. Every itinerary carries Google''s own historical price band (`price_insights_low`/`price_insights_high`) and a `low | typical | high` verdict when Google shows one, plus a booking deep link.

    - **Hotels**: live Booking.com searches, including `proxy_country` (query from any market''s viewpoint via residential proxies - the basis for rate-parity and geo-pricing monitoring).


    **Auth**: bring your own RapidAPI key; every request is billed to your own subscription. Subscribe at https://rapidapi.com/mtnrabi/api/google-flights-live-api/pricing (flights) or https://rapidapi.com/mtnrabi/api/booking-live-api/pricing (hotels). They are separate subscriptions.


    **Honesty contract**: flight searches report their own outcome in `X-Search-Status` (`ok | empty | partial | degraded`), so an empty array is never ambiguous. No uptime or latency figures are published; a public status probe runs every 15 minutes at https://github.com/mtnrabi/travel-agent-skills.


    The same data is available as hosted MCP servers (https://flightpowers.com/mcp), an n8n community node (`n8n-nodes-flightpowers`), Apify actors, and 8 open-source agent skills.'
  contact:
    name: FlightPowers
    url: https://flightpowers.com/contact
    email: matan@flightpowers.com
  termsOfService: https://flightpowers.com/terms
servers:
- url: https://api.flightpowers.com
  description: Production. The RapidAPI hosts (google-flights-live-api.p.rapidapi.com, booking-live-api.p.rapidapi.com) serve the same engines with RapidAPI-native paths; this host is the canonical REST front.
security:
- ApiKeyHeader: []
- RapidApiKeyHeader: []
- BearerAuth: []
tags:
- name: Account
  description: Key verification.
paths:
  /v1/verify:
    get:
      tags:
      - Account
      operationId: verifyKey
      summary: Check that an API key works, as cheaply as possible
      description: Validates the caller's RapidAPI key against the cheapest possible upstream call. A key subscribed to either API is valid. Built for platform "Test connection" buttons.
      responses:
        '200':
          description: The key is valid.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/VerifyResponse'
        '401':
          description: Missing, malformed, or unsubscribed key.
          content:
            application/json:
              schema:
                anyOf:
                - $ref: '#/components/schemas/Error'
                - $ref: '#/components/schemas/VerifyResponse'
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
              description: e.g. `missing_api_key`, `invalid_api_key`, `invalid_request`, `search_incomplete`.
            reason:
              type: string
              description: Present on `search_incomplete`, e.g. `blocked_page`.
            message:
              type: string
    VerifyResponse:
      type: object
      properties:
        valid:
          type: boolean
        checks:
          type: array
          items:
            type: object
            properties:
              api:
                type: string
                enum:
                - flights
                - hotels
              ok:
                type: boolean
              checked:
                type: string
              reason:
                type: string
        api_usage:
          type: object
          description: Your RapidAPI plan quota counters.
        key_source:
          type: string
          description: Which channel supplied the key (header name or query param). Never the value.
  securitySchemes:
    ApiKeyHeader:
      type: apiKey
      in: header
      name: x-api-key
      description: Your RapidAPI key. The default for Zapier-style custom auth.
    RapidApiKeyHeader:
      type: apiKey
      in: header
      name: x-rapidapi-key
      description: Your RapidAPI key, in the header RapidAPI users already have in hand.
    BearerAuth:
      type: http
      scheme: bearer
      description: '`Authorization: Bearer <RapidAPI key>`. `?api_key=` in the query string also works but is discouraged: keys in URLs end up in logs and history.'
externalDocs:
  description: Human docs with captured example responses
  url: https://flightpowers.com/flights-api