> For the complete documentation index, see [llms.txt](https://eleven-fifty-academy.gitbook.io/dotnet-201-elevennote/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eleven-fifty-academy.gitbook.io/dotnet-201-elevennote/elevennote-api-parts-13-19/part-17-testing-endpoints/17.0-apidocs.md).

# 17.0: API Documentation

## 17.0: API Documentation

1. Make sure there are some notes in the database for your specific user.  If not add some.
2. We'll need some `NoteId`'s to test with, take a look at the database and make note of a `NoteId` for the specific user as well as the next available Id#
3. Run the API
4. Add **/help** to the URL to see the API docs with the newly constructed endpoints that were auto-generated from the API Controller methods
5. You can also get here by clicking on **API** in the header

   ![Endpoints](https://3258533034-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LAU8YfMZK4G04fkoGGv%2F-LAxr4YmOkylqP4aqyX3%2F-LAxr88WZl7sGAiWcxHB%2F17.0-A.png?generation=1524677515384522\&alt=media)

   It's important to learn how to use this documentation.  If you were to have a more focused career in front-end development, you would need to be able to use these endpoints as an access point into your application database.  If you are a back-end developer, you will need to read these endpoints to test your API before it's live to all.  Notice that the documentation matches the parameters of your APIController methods. 

[Next,](/dotnet-201-elevennote/elevennote-api-parts-13-19/part-17-testing-endpoints/17.1-getbyidtest.md) we'll test the `GetNoteById` method.