From bab15a612010c7a086521b66741758ef6213d273 Mon Sep 17 00:00:00 2001 From: Jessica Williams Date: Fri, 26 Jan 2024 10:45:11 -0500 Subject: [PATCH] Update README.md to avoid confusion --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e67685333..cdb089e02 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ This module explored the clients-side authentication using auth-tokens. During t In this project, you will connect to a local server with endpoints allowing you to work with interact with data from the cast of Friends. Using this data as a base, you will build functioning login, display and add component pages to your application. -The included API holds a list of friends and lets you add, edit, or remove friends from that list. All of the API endpoints (except the login endpoint) are considered "protected", meaning you have to make the request with an authentication token in the header or the API will send back a `401` error. Take a look at the endpoints that our API has to offer in `http://localhost:9000`. +The included API holds a list of friends and lets you add, edit, or remove friends from that list. All of the API endpoints (except the login endpoint) are considered "protected", meaning you have to make the request with an authentication token in the header or the API will send back a `401` error. Take a look at the endpoints that our API has to offer in `http://localhost:9000` below. - **[POST]** * to `/api/login`: returns a token to be added to the header of all other requests. Pass in the following credentials as the `body` of the request: `{ username: 'Bloom', password: 'Tech' }` - **[POST]** * to `/api/logout`: removes a token from active use. Returns the inactive token.