this post was submitted on 14 Sep 2024
12 points (92.9% liked)
CS Career Questions
351 readers
3 users here now
Rules:
- Be welcoming - Not everyone is a 10 YOE senior engineer. Let's all help each other.
- No memes - Refer to the Programmer Humor community.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Restful API is an approach that is very open to interpretations and mistakes. Meaning, there's nothing that forces a given api to be restful unless the devs were able to do it correctly. Even then, most apis are not expected to be used without thorough documentation.
To practice I would suggest:
Go over the principles of RESTful and try to understand http better ( verbs, request and response structure, headers etc...
There are many free to use apis across the web. Pick any of them, read the docs and try creating a programmatic workflow with that api. It can anything - minimal ui to help uaer interact with it or some background service that talks to the api etc.
Be sure to check the ebtitiea docs as well.
Last thing, it is fairly common to see swagger(openapi) and if the api does support it, it'll make it a lot easier-for you to understand it.
Good luck:)
Any suggestions good APIs to interact with? What do you mean by Ebtitiea doc? the documentation for the API is what I assume you meant to refer to? yeah swagger is a great recommendation of something I need to get more familiar with.
You can try this list: https://github.com/public-apis/public-apis?tab=readme-ov-file
You can even use multiple APIs in a single app if the APIs you want to use are too simple(or for any other reason).
Sorry that was a typo. I meant to write 'entities' as in api entities which are crucial to describe the structure of the requests and responses.
Thanks I'll check it out!