HTTP and REST APIs
Follow a request from URL and method through headers, body, status code, and response before adding higher-level tooling.
Why this matters
People often use 'API' as if it described every part of an integration. Learning the request/response pieces makes debugging and documentation much more concrete.
Learn it
HTTP defines request methods, URLs, headers, status codes, and payload transfer. An API defines operations and meanings on top of those mechanics. REST is an architectural style commonly used for resource-oriented HTTP APIs. A client sends a request to an endpoint; the server evaluates it and returns a response. Authentication and authorization are separate concerns layered onto the request.
Work through an example
GET can retrieve a resource. POST commonly submits or creates data. A 200-series status generally indicates success, while 400-series and 500-series statuses indicate different classes of failure.
POST /observations
Authorization: Bearer …
Content-Type: application/json
{ ...payload... }
→ HTTP status + response bodyPractice
- 1Take one Atlasemoji or other API endpoint and identify method, path, headers, parameters, body, and expected response.
- 2Explain what a 401 tells you compared with a network timeout.
- 3Change one request element at a time when troubleshooting.
Try it
Read and edit GeoJSON
GeoJSON is a JSON format for geographic features. RFC 7946 positions use longitude first, latitude second, with optional altitude as a third value.
What to watch for
REST is not the same thing as HTTP, and an endpoint URL alone is not enough to describe an API operation.
Where this takes you
This is the foundation for OpenAPI, webhooks, connector integrations, AI tools, and programmatic use of Atlasemoji or other platforms.