# api (0-api.org)

API stands for Application Programming Interface. It is a way for two computer programs to talk to each other. Ordinary people often say "API" when they mean any kind of connection or hook into a service, like asking "does this app have an API?" when they want to know if they can pull data out of it or make it work with something else.

## What a model may hear
- REST/HTTP web endpoint (web development, cloud services): assume URL-based requests with methods like GET and POST, expect JSON payloads, and generate code using fetch, curl, or axios patterns
- library or package interface (software engineering, Python/JavaScript ecosystems): look for function signatures, class methods, import statements, and produce code that instantiates objects or calls module functions
- operating system API (systems programming, Windows/Linux internals): reference low-level system calls, kernel interfaces, or platform-specific headers like Win32 or POSIX
- API key or credential (security, authentication flows): generate or request bearer tokens, OAuth flows, or header-based authentication rather than discussing the interface itself

## Where people and models part ways
- Says: "I need an API for this"
  Means: I want some way to get data or control this tool automatically
  May be taken as: the model assumes a formal REST API with documentation and returns nonexistent endpoints or complex code that fails
  Say instead: "I need to extract data from this website or tool automatically. What options exist, such as an official API, scraping, or export features?"
- Says: "Build me an API"
  Means: I want a simple way for my spreadsheet or app to receive data
  May be taken as: the model builds a full production server with authentication, rate limiting, and database schemas that the person cannot deploy or maintain
  Say instead: "I need a simple webhook or endpoint that accepts a few fields and stores them. Please keep the setup minimal."
- Says: "Connect to their API"
  Means: I want to use this company's service in my project
  May be taken as: the model writes code against an outdated or imagined API version, or omits required authentication steps the person does not know exist
  Say instead: "I want to use [company name]'s current API. Please show me how to find their official documentation and make an authenticated request."
- Says: "The API is down"
  Means: Something I use is not working
  May be taken as: the model debugs HTTP status codes and network layers when the person actually means a third-party service, a browser extension, or even a website is broken
  Say instead: "The service I rely on is not responding. How can I tell if it is a network issue, a server problem, or something on my end?"

## Tips
- Always name the service or company whose API you mean, since models know thousands of them.
- Say whether you need to read data, send data, or both, so the model picks the right methods.
- Mention your programming language or no-code tool, or say if you want a no-code solution.
- If you do not have API keys yet, say so; the model can then explain how to get them.
- Ask the model to check that its example uses current endpoints, as APIs change often.

## Often confused with
- SDK: a whole toolkit with helper code, not just the raw interface
- webhook: a push notification from a service, not a request you make
- endpoint: one specific URL in an API, not the whole system
- database: where data lives, not the layer that controls access to it
- protocol: rules for communication, broader than one API's design
- integration: the finished connection, not the technical interface itself