Use the APIVex AirDNA API to retrieve short-term rental market metrics and address-based rental projections for your research tools. A typical workflow resolves a market, retrieves comparable metrics, and evaluates individual addresses separately.
AirDNA analytics and Airbnb listing operations are different jobs. This guide covers APIVex's third-party AirDNA data service; it is not a guide to managing Airbnb reservations or host accounts. AirDNA also offers its own Enterprise API with separate credentials and endpoint definitions.
Choose between a market and a property question
| Question | Starting endpoint | Main input |
|---|---|---|
| Which market matches this city? | GET /suggest_market | location |
| How does a market metric change over time? | GET /market_metric | id, type, metric, currency |
| What is the rental projection for an address? | GET /rentalizer | address |
| What data is available for a known property? | GET /properties/details | property_id |
Use https://api.apivex.com/airdna as the base path. The APIVex AirDNA documentation lists optional inputs and supported values.
Resolve the market first
Set APIVEX_API_KEY in your shell environment and make this Bash/cURL request:
curl --get 'https://api.apivex.com/airdna/suggest_market' \
--header "x-apivex-key: $APIVEX_API_KEY" \
--data-urlencode 'location=Nashville, TN'The endpoint is documented to return a matching market with market and submarket identifiers. Inspect the geographic details before choosing one. A broad market and a neighborhood submarket are different comparison units, even if their names overlap.
Use the market ID for a type=market query; use the corresponding submarket ID with type=submarket. Do not substitute an Airbnb listing ID for either one.
Retrieve a market time series
Replace MARKET_ID_FROM_LOOKUP with your chosen market identifier:
curl --get 'https://api.apivex.com/airdna/market_metric' \
--header "x-apivex-key: $APIVEX_API_KEY" \
--data-urlencode 'id=MARKET_ID_FROM_LOOKUP' \
--data-urlencode 'type=market' \
--data-urlencode 'metric=occupancy' \
--data-urlencode 'currency=usd'The documented metrics include adr, revenue, revpar, listing_count, and occupancy. Choose the metric that answers your question rather than treating these measures as interchangeable.
Keep the returned periods and units with the values. Before displaying occupancy as a percentage, inspect how the response represents it. For comparisons involving money, use the same currency and comparable periods across markets.
Request an address-based projection
The Rentalizer endpoint takes an address and optional property configuration:
curl --get 'https://api.apivex.com/airdna/rentalizer' \
--header "x-apivex-key: $APIVEX_API_KEY" \
--data-urlencode 'address=650 NE 32nd St, Miami, FL 33137' \
--data-urlencode 'bedrooms=3' \
--data-urlencode 'bathrooms=2' \
--data-urlencode 'accommodates=6' \
--data-urlencode 'currency=usd'This uses an example address and configuration from the documentation. Replace both with the property you are studying. The route is documented to provide projections such as nightly rate, occupancy, annual revenue, and comparable properties when available.
Store the submitted configuration alongside the result. A projection for three bedrooms and six guests should not be compared as though it described a two-bedroom property. Treat the output as an estimate, not booked income or a guaranteed outcome.
Build a comparable research dataset
Use one record per market, metric, period, and retrieval time. Keep address projections in a separate dataset with their property assumptions. This makes it possible to explain why two numbers differ instead of presenting a single unlabeled revenue figure.
Start with a small selection of markets. Check that each returned geography matches the intended area, that the time periods align, and that the response contains usable values before expanding the job. Preserve missing observations as missing; do not fill them with zero revenue or zero occupancy.
Common questions
Is this the Airbnb API?
This workflow uses APIVex's AirDNA routes for rental analytics. It does not connect to a host account or create reservations. Choose endpoints by the data task, not just the platform name in a listing.
Can I use my AirDNA Enterprise token here?
APIVex requests use an APIVex key in x-apivex-key. AirDNA's own Enterprise documentation specifies Bearer authentication for its service. Keep the two credential and endpoint systems separate.
Can I export the results to a spreadsheet?
Yes, a spreadsheet can be the destination for your selected fields. The APIVex Sheets tutorial explains the add-on workflow. Keep API IDs, periods, currency, and property assumptions in the export so the numbers remain interpretable.
Next step
Open the AirDNA API reference, resolve one market, and inspect one metric response before building a broader comparison.
