API Settings

How to Connect Third-Party Services in Sky Addons API Settings

The Sky Addons API Settings tab is the one place where every Elementor API settings credential your site needs lives together. Rather than pasting a Google Maps key into one widget and an Instagram token into another, you enter each credential once in the WordPress admin and every matching widget reads it from there. Secret fields are masked with a show/hide toggle, several integrations carry a step-by-step guide linking straight to the provider’s console, and the page saves in one click. This documentation walks you through finding the tab, obtaining each credential, and putting it to work in a widget.

Features:

1. One card per service: Google Maps, Mailchimp, Instagram, Facebook, Twitter / X, Login CAPTCHA, Google Login, AI Provider and Form Builder.
2. Masked secret fields: keys and tokens render as password inputs with an eye icon to reveal them and a cross to clear them.
3. Built-in setup guides: Google Maps, Instagram and Facebook carry a numbered walkthrough plus buttons to the right provider console.
4. Multi-row endpoints: the Form Builder card holds any number of named webhook endpoints, each with its own URL and signing secret.
5. Save All: one button at the foot of the page commits every card together, with a confirmation toast.
6. Automatic Instagram token refresh: a daily background job renews your long-lived token so you rarely have to paste a new one.

Requirements

• Sky Addons for Elementor active, and an administrator account.
• An account with the service you are connecting: a Google Cloud project, a Meta app, and so on.
• Sky Addons Pro for the integrations marked Pro in the table below. Twitter / X is available on the free plugin.

Where to find the Elementor API settings tab

1. Go to WordPress Dashboard → Sky Addons → API Settings.
2. The page opens with the heading API Settings and the line “Configure API keys and credentials for integrated services.”
3. Below it the integrations are laid out as a grid of cards, each showing the service icon, its name and the fields it needs.
4. Fill in only the cards you use, then press Save All at the bottom right.

What each integration powers

Use this table to work out which card you need and what to fetch before opening it.

Integration	What it powers	Credential needed
Google Maps (Pro)	The Google Maps widget: the map itself, address markers and the search box.	One API Key from a Google Cloud project.
Instagram (Pro)	The Instagram Feed widgets.	A long-lived Access Token and an optional Instagram Account ID.
Facebook (Pro)	The Facebook Feed widgets.	A Page ID and a Page Access Token that can read the page feed.
Mailchimp (Pro)	Sky Addons’ Mailchimp integration.	An API Key and the Audience ID (sometimes called a list ID).
Form Builder (Pro)	The Form Builder widget: where notification emails go and which webhooks may receive submissions.	A Receiver Email, plus one endpoint row per webhook.
Login CAPTCHA (Pro)	Bot protection on the Login and Register forms.	A Provider choice, then the reCAPTCHA v3 or Cloudflare Turnstile key pair.
Google Login (Pro)	Google sign-in on the login form.	An OAuth Client ID from a Google Cloud Web client; the secret is optional.
AI Provider (Pro)	Sky Addons features that call an AI service.	A Provider choice, OpenRouter or OpenAI, and its API Key.
Twitter / X (Free)	Sky Addons’ X integration.	An API Key, API Secret and Bearer Token.

---

Obtaining and pasting a key

Three cards do the hard part for you. Google Maps, Instagram and Facebook each show a highlighted guide box above their fields, with numbered steps and buttons opening the provider’s console in a new tab — the Google Cloud Console, the Meta App Dashboard, and the Graph API Explorer and Token Debugger. Follow the steps, copy the value, come back.

Every credential field then behaves the same way:

• Secret fields are masked. Keys, tokens and secrets render as password inputs, so a screen share never leaks them. An eye icon reveals the value while you check it and hides it on a second click, and a cross next to it clears that one field.
• Public values are plain text. Anything the provider treats as public — a reCAPTCHA or Turnstile site key, a Google OAuth client ID, a Facebook page ID, a Mailchimp audience ID — is a normal visible input.
• A Clear link empties a whole card. Hover over a card and a Clear link appears top right, blanking every field in that integration. Nothing is written until you save, so a mistaken click is undone by reloading.
• Some cards hide a developer section. Where offered, a collapsible Advanced — paste a token manually row sits under the main fields.

Multiple endpoints in one card

Some integrations need more than a single value. The Form Builder card carries a Webhook Endpoints repeater: a list of rows, each holding a Name, a URL and an optional Signing Secret. Its description sums up why — “Pick one by name on the widget — the URL and secret never leave the server.” The widget references only the friendly name, so the endpoint and its secret stay in the admin area rather than in page content.

1. Press + Add Endpoint. A new row opens expanded, ready to type into. An empty list reads “No endpoints yet.”
2. Give the row a name you will recognise on the widget, such as Orders CRM, then paste the URL. Both are required. Add a signing secret if the receiving service uses one; it is masked, with its own eye toggle.
3. Collapse the row. It then shows only the name and the host part of its URL, so a long list stays readable and no secret is on screen. Click the header to reopen it, or the cross to remove it.

On the first save each row is given a stable internal id derived from its name. That id is what a widget stores, and it is never regenerated — which is what makes renaming an endpoint later safe rather than a way to break every form pointing at it.

Saving, and where your keys are stored

There is no per-card save button. One Save All button at the foot of the page commits every card at once and confirms with a toast; the page then reloads its values so ids the server assigned to new repeater rows are picked up immediately.

Everything you enter is written to a single WordPress option in your site’s database. Nothing is stored inside a page, widget or template, which is why one credential serves every widget and why exporting a page never carries a key. Two details are worth knowing:

• An emptied field is removed, not blanked. Clearing a value and saving deletes it from storage entirely.
• Deactivating Pro does not wipe Pro credentials. While Pro is inactive its cards are locked and skipped on save, so saving cannot overwrite or delete keys only Pro understands. Reactivate Pro and they are still there.

Which integrations need Sky Addons Pro

The API Settings tab is part of the free plugin, and the Twitter / X card is open to everyone. The rest belong to Pro. Without a licence they still appear, dimmed, with a gold Pro lock badge beside the service name and every field disabled — so you can see what an integration would ask for before deciding to upgrade.

Example: connecting Google Maps end to end

Say you want a working map with a marker on your contact page. Here is the whole journey.

1. Open Sky Addons → API Settings and find the Google Maps card. Read its guide box, headed “Google Maps API key — quick setup”.
2. Click the Google Cloud Console button. Create or pick a project, then enable billing — Google requires it, and maps stay free within a generous monthly credit.
3. Click Enable Maps APIs and switch on three: Maps JavaScript API draws the map, Geocoding API turns an address into a marker, Places API powers the search box.
4. Go to APIs & Services → Credentials → Create credentials → API key and copy the key.
5. Back in Sky Addons, paste it into the API Key field, click the eye icon to confirm you pasted the whole thing, then press Save All.
6. Return to Google and restrict the key to your own domain with HTTP referrer restrictions, so nobody else can spend your quota.
7. Edit your contact page with Elementor, drag in the Google Maps widget and type your address. The widget reads the key from API Settings automatically — there is no key field on the widget — and the map appears straight away.

Visitors see a live, interactive map centred on your address, and a second map added elsewhere later works immediately — the credential is already stored.

Best Practices

• Restrict every key at the provider. Lock a Google key to your domain and give a Meta token only the permissions it needs — the strongest protection lives on their side.
• Only fill in what you use. An unused card is better left empty than filled with a credential nobody is watching.
• Name webhook endpoints for humans. “Orders CRM” tells the next person what the row is for; a hostname does not.
• Rotate a key you have shared. If a token has been in an email or a support thread, issue a fresh one at the provider and update this tab.

Troubleshooting

• The fields on a card are greyed out and show a Pro badge. That integration requires Sky Addons Pro, which is not active on this site. Activate your licence from the License tab and the card unlocks.
• The map is blank or shows an error overlay. Nearly always a Google-side issue: billing not enabled on the project, one of the three required APIs not switched on, or a referrer restriction that excludes the domain you are testing on.
• An Instagram or Facebook feed stopped loading. Instagram tokens are refreshed for you daily, so the usual cause is a token that was never long-lived, or an account that is no longer a Business or Creator account. Generate a fresh token and paste it in again.
• A value you typed is missing after a reload. Check you pressed Save All; individual fields never save on their own.

Frequently Asked Questions

Where do I enter my API key in Elementor?

Not on the widget. Sky Addons keeps credentials at WordPress Dashboard → Sky Addons → API Settings, and every widget that needs one reads it from there. Enter it once and it applies site-wide.

Do I need Sky Addons Pro to use the Elementor API settings tab?

The tab itself is free and so is the Twitter / X card. Google Maps, Instagram, Facebook, Mailchimp, Form Builder, Login CAPTCHA, Google Login and the AI Provider cards are Pro, and appear locked with a Pro badge until a licence is active.

Will my Instagram token expire?

A long-lived Instagram token lasts around sixty days, but Sky Addons runs a daily job that renews it before it lapses. In practice you paste a token once and leave it alone unless the account itself changes.

Are my keys visible to visitors or stored in page content?

They are stored as a site setting in your WordPress database, not inside pages or templates, and the tab is reachable only by administrators. Values a provider treats as public, such as a reCAPTCHA site key, are necessarily used in the browser; secrets are not.

Can I add more than one webhook endpoint?

Yes. The Form Builder card takes as many named endpoint rows as you need, each with its own URL and signing secret, and the Form Builder widget then picks one by name.

Conclusion

Sky Addons API Settings replaces a scattering of key fields with one predictable Elementor API settings screen: masked inputs, guided setup for the fiddliest providers, named endpoints instead of pasted URLs, and a single Save All. Connect a service once and every widget picks it up. For the rest of the admin area see the Sky Addons dashboard tour, and if a credential refuses to take, reach the team at https://wowdevs.com/support/.