Connect any third-party API

Supabase, RevenueCat, GitHub... Bloxks has ready-made integrations for the services most apps need. But your app might need something more specific: a maps provider, a weather service, a payment processor for one-off purchases, a translation engine. If it exposes an API key, Bloxks can use it.

How it works, step by step

1. Get an API key from the service you want to use. Create a free account with the provider (most have one) and find the page where they show your API key, often called "API keys" or "Developer settings".
2. Open Connections in Bloxks. In your project, open the Connections panel (also reachable from your account settings).
3. Click "+ Add an API key". It's at the bottom of the "API keys" section, next to the ready-made providers.
4. Name it and paste your key. Give it a short, clear name (for example "Weather API" or "Maps"), paste the key you copied, then validate. Bloxks stores it encrypted; it's never exposed to your users or visible in your app's code.
5. Ask for the feature in the chat. Tell Bloxks what you want: "Show the weather for the user's city using my Weather API key" or "Add a map screen with directions, use my Maps key." Bloxks writes the server-side code that calls the service through your key.

That's it: no code to write yourself, no key to hide manually.

Where the call actually happens: your Supabase project

Third-party keys are never called from the app itself, they run through your Supabase project's Edge Functions, the same server-side layer Bloxks uses for all backend logic. Concretely:

1. When you link a project to Supabase, Bloxks syncs your account's API keys to that project's Edge Function secrets (a one-time, one-click step).
2. When you ask for a feature that needs an API, Bloxks writes an Edge Function that reads the key from those secrets and calls the third-party service.
3. Your app only ever talks to that Edge Function, never directly to the third-party API.

This means Supabase needs to be connected for a third-party API to actually work in your app. If it isn't yet, Bloxks will ask you to connect it first, it only takes a minute.

Examples of APIs you can plug in

• Maps and directions: Google Maps, Mapbox — show a map, calculate a route, find nearby places.
• Weather: OpenWeather, WeatherAPI — display live forecasts for a city or the user's location.
• One-off payments: Stripe — sell a physical product or a single item (subscriptions inside the app go through RevenueCat instead, it's Apple's required path).
• SMS and phone verification: Twilio — send a text message or a verification code.
• Currency conversion: exchange rate APIs — show live prices in different currencies.
• Music and video: Spotify, YouTube Data API — search tracks, show a playlist, embed a video.
• News and content: News API, RSS-to-JSON services — pull live articles into a feed.
• Translation: DeepL, Google Translate — translate user content on the fly.

This list is just a starting point: any API that hands out a key works the same way.

Good to know

• Your key never leaves the server. It lives in your Supabase project's Edge Function secrets, never sent to your users' phones and never appears in your exported code.
• One key per project. If you build several apps, each needs its own Supabase project linked, and the sync step run again.
• Some services need extra setup, like whitelisting a domain or picking a region: check the provider's own dashboard if a call fails.
• Already using OpenAI or Anthropic keys? Those are listed as ready-made integrations too, alongside your custom keys, and go through the same Supabase Edge Function path.