This backend service is built using Nest.js and Prisma to handle the core functionalities of an e-commerce platform. It is designed with authentication, scalability, and security in mind. The API is structured into multiple modules, each managing a specific part of the application.
\nAdmin: Handles all administrative actions, including user management, product approvals, and system monitoring.
\nUser: Manages user authentication, profile updates, and orders.
\nProduct: Provides endpoints for vewing product details based on queries and ids, updating.
\nReviews: Allows users to leave reviews and ratings for products.
\nCategories: Handles product categorization and filtering.
\nCart: Manages shopping cart operations like adding, removing, and updating items.
\nOrder: Handles order placement, tracking, and status updates.
\nAddress: Manages user addresses for shipping and billing purposes.
\nEach section of this documentation provides detailed information about the available endpoints, request/response formats, and authentication requirements.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Overview","slug":"overview"}],"owner":"32203863","collectionId":"c02d6b86-d9df-40b3-be4d-66edaf1deabf","publishedId":"2sAYdfoqAT","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2025-02-26T09:48:59.000Z"},"item":[{"name":"Admin Module","item":[{"name":"Create Category","id":"7e561264-5cef-4d25-95fa-07863f07da96","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"T-Shirts\",\n \"description\": \"We offer the best good quality t-shirts for everyday use. We offer t-shirts of all sizes.\",\n \"totalProducts\": 0\n}","options":{"raw":{"language":"json"}}},"url":"http://admin.localhost:3000/category","description":"This endpoint allows the admin to create a Category to map a product to filter and sort by category.
\nname (string): The name of the category.
description (string): The description about the category.
totalProducts (number): The total numbers of poducts under that category.
Status: 201 = This status indicates that the task of the endpoint was successful and a category has been created.
\nStatus: 400 = This status indicates an error about admin's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 409 = This status indicates an error about category name already existing. To solve this use another name or delete the previous category.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to get a list Categories to map products to filter and sort by category.
\nStatus: 201 = This status indicates that the endpoint operation was successfull and will return objects categories.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to update a Category to correct data on the server.
\nname (string): The name of the category.
totalProducts (number): The total numbers of poducts under that category.
Status: 200 = This status indicates that the task of the endpoint was successful and a category has been updated.
\nStatus: 400 = This status indicates an error about admin's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 404 = This status indicates an error about category name not being found through provided id.
\nStatus: 409 = This status indicates an error about category name and total products being the same.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to delete a Category on the server.
\nStatus: 200 = This status indicates that the task of the endpoint was successful and a category has been deleted.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 404 = This status indicates an error about category name not being found through provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to create a Product on the server. Products will belong to a category.
\nname (string): The name of the product.
description (string): A short descriptive description about the quality and size of the product.
price (number): The price of the product that will be added to the server.
categoryId (string): The category id where the product will belong to for easy filtering and sorting.
stock (number): The total stock number of the available quantity of product.
files (img): Images of the product that will be used to display how the product would look like to the public. Min is 1 and at max 4 pictures can be added of the product.
Status: 201 = This status indicates that the task of the endpoint was successful and a product has been created.
\nStatus: 400 = This status indicates an error about admin's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 404 = This status indicates an error about category name not being found through provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to update a Product on the server. Products will belong to a category.
\nname (string): The updated name for the product.
description (string): A short descriptive description about the quality and size of the product.
price (number): The updated price of the product that will be added to the server.
categoryId (string): The updated category id where the product will belong to for easy filtering and sorting.
stock (number): The updated total stock number of the available quantity of product.
files (img): Updated Images of the product that will be used to display how the product would look like to the public. Min is 1 and at max 4 pictures can be added of the product.
Status: 200 = This status indicates that the task of the endpoint was successful and a product has been updated.
\nStatus: 400 = This status indicates an error about admin's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 404 = This status indicates an error about product or category name not being found through provided id.
\nStatus: 409 = This status indicates an error about no changes being found betweent the given data and saved product data.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to delete a Product on the server.
\nThere is no req body on this endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and a product has been deleted.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to get an array of Products from the server. Products will be filtered and sorted based on price.
\nThere is no req body on this endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and an array of product has been recieved.
\nStatus: 400 = This status indicates that there was an error from the client side caused by the queries.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to get a Product from the server based on the id provided.
\nThere is no req body on this endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and data of product has been recieved.
\nStatus: 404 = This status indicates that there was no data about this post.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to get an array of orders from the server.
\nThere is no req body on this endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and data of orders has been recieved.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to get data of an order from the server using the id.
\nThere is no req body on this endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and data of the order has been recieved.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the admin to update an order on the server.
\nstatus (string): The status can be of be either \"COMPLETED\" | \"PENDING\".Status: 200 = This status indicates that the task of the endpoint was successful and an order has been updated.
\nStatus: 400 = This status indicates an error about admin's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the admin being unauthenticated.
\nStatus: 404 = This status indicates an error about the order not being found through provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThe Admin Module provides a set of API endpoints to manage the e-commerce platform. Admins have the authority to oversee users, products, orders, and overall system operations. These endpoints ensure that the platform runs smoothly and securely.
\n","_postman_id":"9550ecc2-7a37-4fba-bd82-aba2550e31fb"},{"name":"User Module","item":[{"name":"Create User","id":"65302703-bcde-4588-a36d-5e4e60008f42","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"firstName\": \"Jhon\",\n \"lastName\": \"Clark\",\n \"userName\": \"JhonClark\",\n \"email\": \"jhonclark12@gmail.com\",\n \"password\": \"password\"\n}","options":{"raw":{"language":"json"}}},"url":"http://localhost:3000/user/","description":"This endpoint allows to create a user in our app and view different products and sort and filter them based on queries.
\nfirstName (string): The first name of the user.
lastName? (string): The description about the category. This field is optional.
userName (number): The username of the user used to display on the profile page.
email (string): The email of the user. Email will be used to create the order.
password (string): Password of the user being created.
Status: 201 = This status indicates that the task of the endpoint was successful and an user has been created.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 409 = This status indicates an error about credentials already existing. To solve this use other value than provided.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to log back in into their accounts that they ceated.
\nUser either email or username. If both are provided email will be used.
\nemail (string): The email of the already created user.
userName (number): The username of the already created user.
password (string): Password of the user.
Status: 200 = This status indicates that the task of the endpoint was successful and will recieve an auth cookie from the server.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 404 = This status indicates an error about user not existing to solve this create an user first or use correct credentials
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to log out from their accounts that they are logged in through.
\nNo req body on this post endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and you will be logged out of your account.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to update their existing profile picture to something of their choice.
\nfile (string): Password of the user being created.Status: 201 = This status indicates that the task of the endpoint was successful and an user has been created.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to update their existing profile picture to something of their choice.
\nNo req data on this delete endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and an user's profile picture has been removed.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 409 = This status indicates that the default profile picture is already being used.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to get data of their profile informations.
\nNo req data on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and an user's profile data has been removed.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are client user operations on the application. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"1d09d32d-17de-48a4-8685-0ff67a9966ae"},{"name":"Product Module","item":[{"name":"Get Products","id":"42b29109-d9f1-4da8-8877-6867f15fc57d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"http://localhost:3000/product/products?category=categoryId&limit=0&offset=0","description":"This endpoint allows to get a array of products based on filtering and sorting through queries.
\nNo req data found on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and have recieved an array of objects.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows to get data of products based on the provided product id.
\nNo req data found on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and have recieved an object of product data.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 404 = This status indicates an error about no product being found with the provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are client get products operations on the application. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"9bf5b0dd-e854-417c-aa43-fa617becdcc6"},{"name":"Reviews Module","item":[{"name":"Add Review","id":"ccabeb92-9e73-408f-a37b-724244640095","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"formdata","formdata":[{"key":"orderItemId","value":"orderItemId","type":"text"},{"key":"rating","value":"4","type":"text"},{"key":"comment","value":"I bought this product a month ago and I belive the color is not as bright as shown in the website.","type":"text"},{"key":"files","type":"file","fileNotInWorkingDirectoryWarning":"This file isn't in your working directory. Teammates you share this request with won't be able to use this file. To make collaboration easier you can setup your working directory in Settings.","filesNotInWorkingDirectory":["/home/niaz/Pictures/Screenshots/Screenshot from 2025-01-31 18-08-22.png"],"src":"/home/niaz/Pictures/Screenshots/Screenshot from 2025-01-31 18-08-22.png"},{"key":"files","type":"file","fileNotInWorkingDirectoryWarning":"This file isn't in your working directory. Teammates you share this request with won't be able to use this file. To make collaboration easier you can setup your working directory in Settings.","filesNotInWorkingDirectory":["/home/niaz/Pictures/Screenshots/Screenshot from 2025-02-01 12-21-53.png"],"src":"/home/niaz/Pictures/Screenshots/Screenshot from 2025-02-01 12-21-53.png"},{"key":"files","type":"file","fileNotInWorkingDirectoryWarning":"This file isn't in your working directory. Teammates you share this request with won't be able to use this file. To make collaboration easier you can setup your working directory in Settings.","filesNotInWorkingDirectory":["/home/niaz/Pictures/Screenshots/Screenshot from 2025-01-23 20-41-35.png"],"src":"/home/niaz/Pictures/Screenshots/Screenshot from 2025-01-23 20-41-35.png"}]},"url":"http://localhost:3000/review/","description":"This endpoint allows an user to add an review only after buying a product. Users can give as many reviews as they want only after buying the product.
\norderItemId (string): Order id of the product that the user has ordered.
rating (number): Rating of the user on a product they ordered.
files (images): Images of the product.
Status: 201 = This status indicates that the task of the endpoint was successful and have added an review in product.
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows an user to get a list of reviews on a product using the provided id.
\nNo req data on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and have recieved an array of reviews.
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows an user to delete their review on a product using their review id.
\nNo req data on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and have deleted the review they previously added
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates an error about the review id not being found.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are client reviews operations on the application. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"b8d1af09-781f-4915-b4b8-477af9b7bba4"},{"name":"Categories Module","item":[{"name":"Get Categories","id":"a044e350-af42-4f1b-b8e0-1dc31a361a93","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"http://localhost:3000/category/","description":"This endpoint allows to get an array of categories.
\nNo req data found on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and have recieved an array of categories.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are client categories operations on the application. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"36b1d33a-742f-4584-98b0-07a0bc111e40"},{"name":"Cart Module","item":[{"name":"Add Product to Cart","id":"31fd4965-cdb6-45a0-abf3-69f8d875c265","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"productId\": \"80b20266-69a5-4e0f-bb5b-ff4f6916cc47\",\n \"quantity\": 20\n}","options":{"raw":{"language":"json"}}},"url":"http://localhost:3000/cart/","description":"This endpoint allows the user to add an existing Product to their cart.
\nproductId (string): Product id of the product the user wants to add in their cart.
quantity (number): Quantity of the added products in the cart.
Status: 201 = This status indicates that the task of the endpoint was successful and products has been added to the user's cart.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates an error about product not being found through provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to get existing Products from their cart.
\nNo req data on this get endpoint.Status: 200 = This status indicates that the task of the endpoint was successful and products has been fetched from the user's cart.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to update an existing Product to their cart.
\nproductInCartId (string): Product id that is in the user's cart.
quantity (number): Quantity of the newly updated products in the cart.
Status: 200 = This status indicates that the task of the endpoint was successful and product has been updated in the user's cart.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates an error about product not being found through provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows the user to remove an existing Product from their cart.
\nproductInCartId (string): Product id that is to be removed from the user's cart.Status: 200 = This status indicates that the task of the endpoint was successful and product has been removed from the user's cart.
\nStatus: 400 = This status indicates an error about client's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates an error about product not being found through provided id.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are crud operations on the products in cart. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"3d207656-5eb4-4a26-992e-325e70736fca"},{"name":"Order Module","item":[{"name":"Place Order","id":"c1c5279a-5834-4a76-a4a9-d4a93a5b198b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"productId\": \"32024e5c-ae41-40ed-a786-ac6b59f85e72\",\n \"quantity\": 1,\n \"paymentMethod\": \"ONLINE\"\n}","options":{"raw":{"language":"json"}}},"url":"http://admin.localhost:3000/order","description":"This endpoint allows an user to place an order by providing the product id.
\nproductId (string): Product id of the product that the user has ordered.
quantity (number): Number of products that the user wants to buy.
paymentMethod (images): Payment method and be of two types \"COD\" or \"ONLINE\".
Status: 201 = This status indicates that the task of the endpoint was successful and have ordered a product.
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates an error about the product or address of the user not being found.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows an user to place an order by providing the product id.
\norderId (string): Order id of the product that the user has ordered and now want to be canceld.Status: 200 = This status indicates that the task of the endpoint was successful and have caceled an order.
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates an error about the order not being found.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are client order operations on the application. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"49deaae6-9a38-4ef5-863a-00dcdadf35ce"},{"name":"Address Module","item":[{"name":"Add Address","id":"d173828b-7b4b-41b9-a206-79c69f524aff","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"street\":\"Golden Street\",\n \"city\":\"Uttara\",\n \"state\":\"Dhaka\",\n \"postalCode\":\"5555\",\n \"country\":\"Iran\"\n}","options":{"raw":{"language":"json"}}},"url":"http://localhost:3000/address/","description":"This endpoint allows an user to add their address to place an order.
\nstreet (string): Street name of the address where the user wants their product to be delivered.
city (string): City where the user wants their product to be delivered.
state (string):State or division of the address where the user wants their product to be delivered.
postalCode (string): Postal code of the address where the user wants their product to be delivered.
country (string): Country name of the address where the user wants their product to be delivered.
Status: 201 = This status indicates that the task of the endpoint was successful and have added an address.
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows an user to get their address.
\nNo req data found on this endpoint.Status: 200 = This status indicates that the task of the endpoint and recieved the address.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus 404 = This status would indicate an error about the address not being found.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows an user to update their address that is already saved.
\nstreet (string): Street name of the address where the user wants their product to be delivered.
city (string): City where the user wants their product to be delivered.
state (string):State or division of the address where the user wants their product to be delivered.
postalCode (string): Postal code of the address where the user wants their product to be delivered.
country (string): Country name of the address where the user wants their product to be delivered.
Status: 200 = This status indicates that the task of the endpoint was successful and have updated an address.
\nStatus: 400 = This status indicates an error about user's type validation. Error message will contain status and the indicated type error.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus: 404 = This status indicates that the user have not yet added an address.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThis endpoint allows an user to delete their address.
\nNo req data found on this endpoint.Status: 200 = This status indicates that the task of the endpoint and deleted the address.
\nStatus: 401 = This status indicates an error about the user being unauthenticated.
\nStatus 404 = This status would indicate an error about the address not being found.
\nStatus: 500 = This status indicates an unexpected error in the server side. This has nothing to do with the user.
\nThese set of API endpoints are crud operations on an user's address. Here they are minimally documented based on their inputs and outputs.
\n","_postman_id":"1d00295a-3aaa-4feb-8902-cbe98d8684f9"}]}