API Settings centralises the third-party credentials your blocks need — enter each key once and every block that uses it reads from the same secure store. Keys are encrypted at rest, and each save runs a live connection test so you get an immediate valid or invalid badge.
Where: WP Admin → Tiger Blocks → Settings → API.
Connected services
- Google — a single Google API key powers the Places-based blocks: Google Reviews, the Google Business Badge, Map Pro (when using Google Maps) and the Store Locator. A preferred review language can be set alongside it.
- Instagram — an access token for the Instagram Feed block; a successful test auto-fills the connected username, and you can clear the feed cache here.
- YouTube — a Data API key for YouTube-powered blocks.
- Mailchimp — an API key and audience/list ID for the Newsletter block (the datacenter is read from the key’s own suffix, e.g.
-us21).
The same screen also holds the site-wide Google reCAPTCHA configuration used by the account and form blocks.
Enter once, use everywhere
Because credentials are stored centrally, dropping in a Map, Reviews or Newsletter block just works — there is no per-block key to duplicate. Rotating a key updates every block on the site at once. When a field is empty, consuming blocks treat the service as not configured and skip the API call rather than erroring.
Live validation
Saving a key triggers a real request to the provider (Google Places details, the Instagram me lookup, a YouTube search, or a Mailchimp ping). A valid badge confirms the key works; an invalid badge shows the provider’s own error message so you can fix it fast.
Troubleshooting
My Google key saved but a Map or Reviews block is blank
A single Google key must have the right APIs enabled in the Google Cloud console — Places API for reviews/badges, Maps JavaScript API for Google Maps. Enable the needed API, and if you locked the key by referrer or IP, make sure your site’s domain is allowed. Then re-save so the connection test re-runs.
Mailchimp reports an invalid key
A Mailchimp key must include its datacenter suffix (for example …-us21); without it the connection cannot be built. Copy the full key from Mailchimp and confirm the audience/list ID matches that account.