find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/flightpowers-com:flightpowers-com-verify-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Flight Powers Travel Data Verify API
  description: Real-time flight fares and hotel prices. Bring your own RapidAPI key; every request is billed to your own subscription.
  version: 1.0.0
tags:
- name: Verify
paths:
  /v1/verify:
    get:
      summary: Verify
      description: 'Check that an API key works, without spending any of it.


        Every platform that consumes this API wants a "Test connection" button,

        and every request that reaches a RapidAPI listing is metered -- a 422

        included. Until 2026-09-28 this handler tried the hotels listing''s

        `GET /isalive` (metered) and, for a flights-only key, ran a real one-way

        search (metered, and a live Google search); a free subscriber spent 3 of

        his 10 monthly requests on three clicks.


        Now it asks the Hub, once per listing and at the same time, whether it

        accepts the key: `upstream.probe_subscription`, a GET to a path no

        listing configures. The Hub checks key and subscription before it

        routes, so a subscribed key gets the Hub''s own 404 and anything else a

        403. No request is metered, nothing reaches a backend, no search runs.

        The price is `api_usage`: the plan counter only comes back on a metered

        response, so it is `{}` here; every search response carries it in the

        `x-plan-requests-*` headers.


        A key subscribed to any of the three listings (Booking, Google

        Flights, Airbnb) is valid (200), and `checks` says which ones cover it;

        401 when none does, same body as before. The Airbnb check was added

        2026-10-23 (n8n node 0.3.0 ships an Airbnb resource, and a key

        subscribed only to the Airbnb Live API failed "Test connection"); it is

        appended, so `checks[0]` and `checks[1]` still name hotels and flights.


        Known gap, unchanged: a key subscribed *only* to the bulk hotels listing

        verifies as invalid, because this check does not ask that listing.'
      operationId: verify_v1_verify_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                title: Response Verify V1 Verify Get
      tags:
      - Verify