From the course: Cisco DevNet Associate (200-901) Cert Prep 2: Understanding and Using APIs

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Additional API constraints

Additional API constraints

From the course: Cisco DevNet Associate (200-901) Cert Prep 2: Understanding and Using APIs

Start my 1-month free trial

Additional API constraints

- [Instructor] Let's look at some additional API constraints. Just like UDP, the REST API should be stateless. What does that mean? It means the server will not store anything about the latest HTTP request from the client and will treat each request as new, no prior session and no prior history required. Very similar to the normal HTTP transactions that we're familiar with. This makes sense, as we want each of the requests to contain all the information necessary for the server to understand what we want and respond accordingly. In practice, this might be slightly altered if we want the client not having to be authenticated every single time and only be authenticated in the beginning. What we will still follow is the fact that each of the requests after the initial authentication should contain all the necessary information to identify the credential of the client. We will see more example on this front in the API…

Contents