The APIs that power majority of the content you see on internet!!!!

Hello people,
We are very glad to start the REST APIs made easy course with the very first video on fundamentals of REST APIs, HTTP Methods, taxonomy around REST APIs etc. We hope that you get some value out of this course and these concepts help you thrive in your jobs, interviews and help you become better software engineers every day. Here are few links that you might want to refer before or during the course:
More on the topic:
✒developer.mozilla.org/en-US/d...
✒github.com/microsoft/api-guid...
------------------------------------------------------------------
Recommendations
------------------------------------------------------------------
Our full courses on youtube:
✒ System Design Primer Course: • System Design Primer C...
✒ REST APIs made easy: • REST APIs MADE EASY
Some paid courses that we recommend:
✒Educative.io: bit.ly/3qnW5ku
✒Interviewready.io: get.interviewready.io/ (Use coupon code SUDOCODE for extra discount)
------------------------------------------------------------------
About Us
------------------------------------------------------------------
Created and Instructed by:
Yogita Sharma
✒ LinkedIn - / yogita-sharma-83400b55
✒ Instagram - / sudo.code1
✒ Facebook - / sudo.code
✒ Medium - / yogita088
Post-production(editing, thumbnail etc) managed by:
CiKi
✒ Website: www.ciki.co.in
✒ LinkedIn: / 74735937
Colors and design by:
Naini Todi
✒ LinkedIn - / nainitodi
Both Arpit and Yogita are software engineers and want to help other software engineers become better by providing high quality and well researched content by adding their creativity and teaching twist.
------------------------------------------------------------------
Join Us
------------------------------------------------------------------
Hangout with sudoCode:
✒Discord Server: / discord
For business:
✒Email: [e-mail]

[@abhinav.sharma]

Landed on this channel from GKCS' video with you. Thought what new would you teach about GET...since it's simple API stuff.
You did not disappoint. Gotta learn a lot about API design.
More power to you Yogita. 💯

[@Uzair_Anwar2299]

The way you explain the stuff in incredible

[@Rakeshkumar-tw1ez]

Thanks for the wonderful video. It has everything what is required to write a Get API

[@sakshiaggarwal6199]

Thank you so much for sharing!!

[@shivam3467]

Nice Video. Looking forward to filtering and pagination video :)

[@rinagood]

Finely, something understandable!

[@rinkukumar4257]

Loving REST API series...👍👍

[@janetkalu3064]

Thank you Yogita, I learnt so much

[@anshikabhatnagar5036]

THANK YOU for existing.

[@punyabikash3624]

Excellent very useful videos keep going :)

[@auroshisray9140]

This was concise, please make a video on standards for DELETE request.

[@TheGhumanz]

As you mentioned in the video API will only respond to the designed commands. I would like to see how you designed those commands on back-end? I mean if you can show how to design an API on back-end? BTW, great video again!

[@subee128]

Thank you very much

[@SunShine-ge3yj]

Thanks for the content

[@gsanjeevkumar]

Great work so far, do you have any videos done/upcoming which can cover the overall feature to manage secure interfaces with underlying REST APIs?

[@hobbies.central]

Thanks Yogita for your detailed videos on Design. When Low Level Design Videos will be uploaded? I am eagerly waiting for LLD series.

[@mohitshrivastava1158]

Yogita, I have a doubt here regarding the naming of the resources being singular and plural, we used /app/customer to return all the customers, and to get all orders of a specific customer we are using /app/coustmer/1/orders I guess we should be using /app/coustmer/1/order
Or is there any concept of naming resources one after the other

[@sraynitjsr]

Thanks Ma'am 🙂

[@rohitaich4257]

really good

[@cresloga]

How many query params at most can a GET API accept? Are there limitations in the length of URL and does that pose a constraint on the number of query params and the length that the query param values can take?

[@bedtime_RL]

Hi, may I know what tools did you use to test the API in your video?

[@funnyvideorocks]

Please make video on springboot annotation. Your video is so basic and it's good for us

[@MrAymenmatador]

Hello, Does getting current date from server make the GET not idempotent ?

[@shaivaljava401]

you inspire me to prep for interview.

[@sudocode]

Thanks but your current employer is gonna be mad at me 🙈

[@hamsaganesh7675]

But lets say the query parameter sent in the GET request exceeds the limit on the length of the query string, then can we use POST method and pass the query as payload instead

[@anuragb12]

Hello Yogita , I am confused why is it best practice to have /customer?id=1 rather than /customer/1

[@ankitbhosale2445]

Wating from long time

[@akhila.sakhila9018]

Old way of presenting is nice , follow that only

[@myLifeSk98]

#50k soon ❤️ thanks

[@lavkushtiwari2799]

Hi Yogita, I'm following your system design playlist since past month, can you please make a detailed tutorial for consistent hashing with examples of adding and deleting nodes

[@sudocode]

I think I already did.

[@lavkushtiwari2799]

@@sudocode yes, i have completed that one, didn't check the links. I was confused with replicas(i understood the importance of it). Many questions like,
Are replicas physical or just reference to the original server,,,If they are physical means we can do everything what we do with normal server...
I forgot to add appreciation for your efforts. You are the only youtuber who doesn't ask for "like, subscribe and share"

[@AbhishekSharma-xe4cr]

I can be wrong here but usually in URI they use plural not singular although it doesn't matter that much but that make more sense
Like localhost:4000/users will return User list
localhost:4000/users/:id
but having singular noun here can be confusing.
Please Correct me if I'm wrong.

[@sudocode]

You are absolutely right. It’s a miss from my end. I will post errata in comments.

[@akshaysharma2080]

Hey, if we have to find our just one order of a customer using orderid then the uri will be this /customer/1/order/123. Or the orderid will be query param

[@sudocode]

Using query param won’t be a good approach.

[@leslieataembo]

How do you obtain an API key?

[@punyabikash3624]

please make video security of Get request maam

[@funnyvideorocks]

Hi Mam,can you please explain us difference between rest Api and restful api

[@GauravKumar-py5br]

Ma'am if you provide slides it would be very helpful

[@sayanroy9161]

Please make videos on design

[@sudocode]

Which design exactly?

[@sayanroy9161]

@@sudocode mainly lld design

[@sayanroy9161]

there are not good resource available for lld

[@raghavsharma4195]

Need HTTP OPTION, FETCH METHOD