An API is a controlled way for one piece of software to communicate with another.
You do not need to begin with programming syntax to understand the idea.
Think:
System A → Request → API → Response → System A Uses the Result
A practical example
Imagine a website that needs weather information.
The website does not need to operate weather stations around the world.
It can request data from a weather service through that service’s API.
The API defines what can be requested, how the request should be made and what information will be returned.
Endpoint
An endpoint is an address representing a particular API resource or operation.
One endpoint might return a user.
Another might return a list of videos.
Another might accept a new order.
HTTP methods
Web APIs commonly use familiar HTTP methods.
GET usually requests information.
POST commonly submits or creates information.
PUT and PATCH are commonly used to update information.
DELETE commonly requests removal.
The exact behavior is defined by the API.
Authentication
Some APIs are public.
Others require credentials.
These can include API keys, access tokens, signed requests or other authentication systems.
A secret API credential should not be placed into ordinary public webpage code where visitors can retrieve it.
JSON
Many APIs return JSON.
JSON is simply a structured way to represent information.
Conceptually, a response might contain:
Name: WRUnity
Type: Education
Status: Active
Software can read those fields without trying to understand a paragraph written for humans.
Rate limits
An API provider may limit how many requests a client can make during a period.
This protects systems from excessive traffic and can also separate service levels.
Good integrations expect rate limits instead of assuming unlimited access.
Polling
Polling means repeatedly asking:
“Has anything changed?”
For example, a scheduled job might request new information every hour.
Webhooks
A webhook reverses the direction.
Instead of repeatedly asking whether something happened, your system provides an endpoint and another system sends a request when an event occurs.
Conceptually:
Event Happens → Remote System → Your Webhook → Your Application Reacts
APIs fail too
A remote API can be slow, unavailable, changed, rate limited or return unexpected information.
Applications should decide what happens when the dependency is unavailable.
Understanding that possibility is part of understanding APIs.
The important first skill is not memorizing code.
It is seeing the information flow.
Put This Lesson to Work
Choose a real website or project you control. Identify where this lesson applies, record who is responsible for that part, and identify one change or check you can safely make.
Worked example
For a domain-email lesson, record the separate website and email providers. Look up the existing MX records without changing them, then confirm which provider receives mail.
Your finished result
A short explanation of the system, its owner, and a checked next action. Keep passwords and recovery codes out of your notes.
Check your understanding
- Can you explain the main idea without repeating a slogan?
- What evidence or example supports your explanation?
- Which decision will you make differently, and why?