BigDataCloud, Google Maps, and LocationIq each require an API key before photo-cli can send reverse geocode requests. You can provide the key in three ways: as a command-line argument each time you run a command, as an environment variable for your current session or CI environment, or saved persistently in photo-cli settings so you never have to pass it again.Documentation Index
Fetch the complete documentation index at: https://photocli.com/llms.txt
Use this file to discover all available pages before exploring further.
OpenStreetMap Foundation (Nominatim) does not require an API key. If you selected OpenStreetMap as your provider, you can skip this page.
Three ways to provide a key
1. Command-line argument
Pass the key directly each time you run a command. Use this approach for one-off runs or when you want to be explicit.2. Environment variable
Set the environment variable in your shell session or CI pipeline. photo-cli reads it automatically — no argument needed in the command.3. Saved in settings
Save the key to photo-cli’s persistent settings. Once saved, you never need to pass the key on the command line or export an environment variable again.Reference: arguments and environment variables
| Provider | Argument | Environment variable | Settings key |
|---|---|---|---|
| BigDataCloud | -b / --bigdatacloud-key | PHOTO_CLI_BIG_DATA_CLOUD_API_KEY | BigDataCloudApiKey |
| Google Maps | -k / --googlemaps-key | PHOTO_CLI_GOOGLE_MAPS_API_KEY | GoogleMapsApiKey |
| LocationIq | -q / --locationiq-key | PHOTO_CLI_LOCATIONIQ_API_KEY | LocationIqApiKey |
| OpenStreetMap Foundation | — | — | — |