Skip to content

Level 4 — APIs, keys & data

When a demo grows into a “real” app, these are the parts that bite. You don’t have to build them — but you must understand them.

What it is. A way for one program to ask another for something. “Add payments” means connecting the Stripe API. “Add maps” means the Google Maps API. The AI knows how; deciding to connect it is your call.

What it is. A password for accessing someone else’s service.

What it is. A file of secrets (keys, database passwords) that is kept out of Git. It’s how you separate code (public) from secrets (private).

What it is. Where user data is stored for the long term. There’s often a local database (for testing) and a cloud database (for production) — they are different databases, and it’s easy to confuse them.

What it is. “Log in with email,” “sign in with Google.” Sounds simple; it’s the most underestimated part of the whole stack.

Look at your project for a .env (or .env.example) file and confirm it’s listed in .gitignore — meaning Git ignores it and it never reaches GitHub. If you can’t find one, ask the AI where secrets are stored and whether any are hard-coded.