ApivomApivom
Get Demo

Google Aerial View API Connector

Google's Aerial View API — request a cinematic 3D fly-around video of a US address rendered from Google's photorealistic 3D imagery, then fetch it by address or video id — registered in Apivom Atlas for property, hospitality and real-estate tenants, with your own Maps Platform key.

What you can do

  • Render Video: queue a new aerial video for a supported US address
  • Lookup Video: fetch the processing state and MP4/HLS URIs for an address or video id
  • Landscape and portrait variants delivered from Google's 3D imagery; coverage limited to supported US metros
  • Two routes (one read-only) registered in Atlas with the credential contract and llms.txt guide

Use cases

  • A fly-around on every listing — Queue an aerial video when a US property is added to your catalogue and attach the clip once Google reports it ready.
  • Show the venue in context — Give event or hospitality pages a short orbit of the building and its surroundings without sending a drone crew.

Aerial View on aerialview.googleapis.com turns an address into a short, cinematic fly-around video generated from Google's photorealistic 3D tiles — the kind of clip property listings and venue pages use to show a building in context. The workflow is asynchronous: Render Video queues the job for a US address with coverage, and Lookup Video returns its state and, once ready, the video URIs in landscape and portrait, which you can poll by address or by video id. Apivom Atlas registers both routes with the Maps Platform credential contract, per-tenant logging and the AI integration guide (llms.txt); your key, project and quotas apply, and Google's terms on caching and attribution govern how long you may keep and where you may show the videos. No Apivom product workflow renders aerial videos today — the connector is available for your own listing or venue tooling, and a product flow is scoped per customer.

Authentication

Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Where does Aerial View work?

Only for addresses inside Google's photorealistic 3D coverage, which today means a set of US metropolitan areas. Unsupported addresses return an error at Render Video time, so check coverage before promising a clip.

Which Google Cloud project pays for the calls?

The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.