#Theoretical Spring boot API Question
1 messages · Page 1 of 1 (latest)
<@&1004656351647117403> please have a look, thanks.
Here is an AI assisted attempt to answer your question 🤖. Maybe it helps! In any case, a human is on the way 👍. To continue talking to the AI, you can use </chatgpt:1108714622413963314>.
Your confusion is understandable. In Spring Boot, the API refers to the set of endpoints your application exposes over HTTP (like /users, /products), which clients (Postman, browsers, apps) interact with.
When you use Postman to send HTTP requests (GET, POST, etc.), you're directly calling these API endpoints defined in your Spring Boot app, usually via @RestController classes with @RequestMapping or similar annotations.
So, the API exists in your Spring Boot app as the HTTP endpoints you create, and Postman is just a tool that makes those HTTP calls easier to manage and test. The web requests you send carry data to or from these endpoints.
In short:
- API = The HTTP interface your Spring Boot app provides
- Postman = A client to test that API by sending HTTP requests
- Using HTTP requests is exactly how APIs work in the web world.
Useful links:
The end-point you called with the GET request is part of their API.
Exposing HTTP endpoints is one form of API (and these days is usually the one they mean when they talk about 'having an API' in their product).
Usually the HTTP endpoints follow a convention. A commonly mentioned one, but usually only very loosely adhered to, is a REST API.
So you're telling me the endpoints are the api
Hmm... I'm not sure about the suit.