> For the complete documentation index, see [llms.txt](https://docs.keyshade.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyshade.io/contributing-to-keyshade/running-things-locally/running-the-api.md). # Running the API Get to know how you can develop the API! The API resides in the `apps/api` directory. It is a NestJS project. To run the API locally, do the following: * Generate the prisma types: ```bash pnpm run db:generate-types ``` * Deploy the migrations: ```bash pnpm run db:deploy-migrations ``` * Start the server in development mode: ```bash pnpm run dev:api ``` * There might be a case when you would like to create a completely fresh copy of the database. In that case, you might use the reset command: ```bash pnpm run db:reset ``` ## Testing your code We currently perform two kinds of tests: **unit tests** and **integration tests.** After you make sure that you have added your unit tests, or you have made some changes to the existing functionality, you can run them using: ```bash pnpm run unit:api ``` After this is complete, you can run end-to-end tests to validate your entire application from start to finish. Use this command: ```bash pnpm run e2e:api ``` You can also skip these first two commands and perform the unit and e2e tests at the same time with: ```bash pnpm run test:api ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keyshade.io/contributing-to-keyshade/running-things-locally/running-the-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.