Stay organized with collections
Save and categorize content based on your preferences.
The Aerial View API supports two general workflows. Your approach depends on
whether the video you're requesting exists or not. If you're unsure whether the
video exists, you should use
lookupVideoMetadata
to determine the video's state.
Workflow to generate or retrieve videos
Use the following workflow to generate or retrieve an aerial view video:
Check if Google has already generated a video for the location using
lookupVideoMetadata.
If no video exists (lookupVideoMetadata returned a 404), call
renderVideo to generate
a new video.
Call lookupVideoMetadata using the videoId or address to poll the
endpoint until the video's state is ACTIVE. Rendering can take several
hours, so use exponential
backoff to space out your
calls.
If the video is active (lookupVideoMetadata returned a state of ACTIVE),
call lookupVideo to fetch
the video's URIs.
This workflow is represented in the diagram below:
Save video IDs for later use
Subject to the Service Specific Terms for Aerial View API, Aerial View API
video IDs are exempt from the caching restrictions stated in Section
3.2.3(b)(No
Caching) of the
Google Maps Platform Terms of Service. You can therefore store video ID values
for later use.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThe Aerial View API offers two workflows: one for retrieving existing videos and another for generating new ones.\u003c/p\u003e\n"],["\u003cp\u003eTo determine if a video exists for a location, utilize the \u003ccode\u003elookupVideoMetadata\u003c/code\u003e function.\u003c/p\u003e\n"],["\u003cp\u003eIf a video doesn't exist, initiate video generation using the \u003ccode\u003erenderVideo\u003c/code\u003e function and monitor its status with \u003ccode\u003elookupVideoMetadata\u003c/code\u003e until it becomes active.\u003c/p\u003e\n"],["\u003cp\u003eOnce the video is active, retrieve its URLs via the \u003ccode\u003elookupVideo\u003c/code\u003e function for access and use.\u003c/p\u003e\n"],["\u003cp\u003eAerial View API video IDs can be stored for future use, unlike other Google Maps Platform content.\u003c/p\u003e\n"]]],[],null,["The Aerial View API supports two general workflows. Your approach depends on\nwhether the video you're requesting exists or not. If you're unsure whether the\nvideo exists, you should use\n[`lookupVideoMetadata`](/maps/documentation/aerial-view/lookup-video-metadata)\nto determine the video's state.\n\nWorkflow to generate or retrieve videos\n\nUse the following workflow to generate or retrieve an aerial view video:\n\n1. Check if Google has already generated a video for the location using [`lookupVideoMetadata`](/maps/documentation/aerial-view/lookup-video-metadata).\n2. If no video exists (`lookupVideoMetadata` returned a 404), call [`renderVideo`](/maps/documentation/aerial-view/generate-video) to generate a new video.\n 1. Call `lookupVideoMetadata` using the `videoId` or address to poll the endpoint until the video's state is `ACTIVE`. Rendering can take several hours, so use [exponential\n backoff](/maps/documentation/aerial-view/web-api-best-practices#exponential-backoff) to space out your calls.\n3. If the video is active (`lookupVideoMetadata` returned a state of `ACTIVE`),\n call [`lookupVideo`](/maps/documentation/aerial-view/lookup-video) to fetch\n the video's URIs.\n\n | **Note:** After Google generates the video for a specific address, that video is available to anyone. That is, a video is not associated with a specific user or account.\n\nThis workflow is represented in the diagram below:\n\nSave video IDs for later use\n\nSubject to the Service Specific Terms for Aerial View API, Aerial View API\nvideo IDs are **exempt from** the caching restrictions stated in [Section\n3.2.3(b)(No\nCaching)](https://cloud.google.com/maps-platform/terms/) of the\nGoogle Maps Platform Terms of Service. You can therefore store video ID values\nfor later use."]]