Connectors & APIs
How your app asks another company's app for something.
An API is a service desk with a very strict script. Your app hands over a written request — a method, an address, a key, a body — and gets a structured answer back.
The failure path is as important as the happy path. Timeouts, 401s, and rate limits decide whether your app looks broken or trustworthy when something goes wrong.
Words you will hear
- Endpoint
- The specific address your app sends a request to — one address per action.
- API key
- A secret proving your app is authorized to make requests. Never put it in a page.
- JSON
- The standard text format APIs use to send structured data back and forth.
Interactive demo
Request and response visualizer
A service that returns live weather for any city. Your app sends a city name, the service returns temperature and conditions.
Request leaving your server
GET https://api.example-weather.com/v1/now
Authorization: Bearer ****************
Content-Type: application/json
{
"city": "London"
}Response coming back
Nothing yet. Send a request to see the answer.
These responses are mocked in your browser. The shape is exactly what a real service returns.
What makes this work
The pieces underneath
Try it
15 minAsk your builder to show today's weather for a city you type in, using a public weather API. Then break it on purpose: type a nonsense city name and watch how the app handles the error.
- Store the key as a secret, never pasted into a page.
- Ask for a loading state and an error state by name.
Free account
Save your progress and earn your certificate
Keep reading as long as you like — everything here stays open. Add your email and we will track your completion, sync it across devices, and issue your Vibe Coding micro-credential when you finish.
Just enter your email. We will send you a link — no password needed.