This collection covers the complete API workflow for the Expense Tracker application. It is organized into three functional groups:
\nHandles user identity and access. Includes endpoints for:
\nSIGNUP – Register a new user account.
\nLOGIN – Authenticate an existing user and retrieve a JWT for use in subsequent requests.
\nManages the core expense data for an authenticated user. Includes endpoints for:
\nADD EXPENSES – Create and record a new expense entry.
\nFETCH ALL EXPENSES – Retrieve the full list of expenses associated with the user.
\nDELETE EXPENSE – Remove a specific expense record by its identifier.
\nProvides supporting product data used within the application. Includes:
\nAuthentication is JWT-based. Use the LOGIN endpoint to obtain a token, then include it in the Authorization header for all protected requests. A collection-level variable json_web_token_094c is available to store and reuse the token across requests.
Registers a new user account in the Expense Tracker application. Sends a POST request to /auth/signup with a JSON body containing the user's name, email, and password. On success, the account is created and the user can proceed to login. No authentication is required for this endpoint.
Authenticates an existing user and returns a JWT token. Sends a POST request to /auth/login with a JSON body containing the user's email and password. The returned JWT should be stored and passed as the Authorization header value (using the {{json_web_token_094c}} variable) for all protected endpoints. No authentication is required for this endpoint.
This folder handles user identity and access management for the Expense Tracker application.
\nSIGNUP – Register a new user account by providing the required credentials.
\nLOGIN – Authenticate an existing user and retrieve a JWT token. Use this token in the Authorization header for all protected endpoints across the API.
Creates and records a new expense entry for the authenticated user. Sends a POST request to /expenses with a JSON body containing the amount and a text description of the expense. Requires a valid JWT passed in the Authorization header via the {{json_web_token_094c}} variable.
Retrieves the complete list of expense records associated with the authenticated user. Sends a GET request to /expenses with no request body. Requires a valid JWT passed in the Authorization header via the {{json_web_token_094c}} variable.
Permanently removes a specific expense record by its unique identifier. Sends a DELETE request to /expenses/:id, where the expense ID is included in the URL path (e.g., 6a7fe81bb2c751086cbc9b2e). Requires a valid JWT passed in the Authorization header via the {{json_web_token_094c}} variable.
Manages the core expense data for authenticated users.
\nThis folder contains the endpoints for creating, retrieving, and deleting expense records:
\nADD EXPENSES – Creates and records a new expense entry for the authenticated user.
\nFETCH ALL EXPENSES – Retrieves the complete list of expense records associated with the authenticated user.
\nDELETE EXPENSE – Removes a specific expense record from the system using its unique identifier.
\nAll endpoints in this folder require a valid JWT in the Authorization header.
Fetches the list of available products used within the Expense Tracker application. Sends a GET request to /products with no request body or query parameters. This endpoint provides supporting product data that can be referenced when categorizing or recording expenses.
Provides supporting product data used within the Expense Tracker application.
\nThis folder contains:
\n