5.4 KiB
📌 API Endpoint Overview
This document provides a categorized and role-specific overview of all API endpoints implemented (or to be implemented) in the system. It is structured for easy readability, regular updates, and fast navigation.
⚖️ Roles
admin— Endpoints accessible only to admins.user— Endpoints accessible to regular authenticated users.
Status Legend:
done- Fully implemented and Testedok— Implemented but not testedpartial— Implemented but incomplete or unstableTODO— Needs implementationnot ok— Implemented but incorrect or buggy
Testers will write done, not ok and developers will define status that is not tested or something like that, so developers can write code with no communication and fully peace.
🔑 Auth & Users
users:
POST /auth/register— user — remakePOST /auth/verify— user — okGET /auth/me— user — ok
me/companies:
GET /me/companies— user — okPOST /me/companies— user — ok
users/:
GET /users/<uuid:pk>/companies— user — okPOST /users/<uuid:pk>/companies— user — ok
🏢 Companies
companies:
-
GET /companies— admin — ok -
POST /companies— admin — ok -
GET /companies/<uuid:pk>— admin — ok -
DELETE /companies/<uuid:pk>— admin — ok -
PATCH /companies/<uuid:pk>— admin — ok -
GET /companies/<uuid:pk>/contracts— user — partial- filters:
folder,status: list[str]
- filters:
-
GET /companies/<uuid:pk>/folders— user — ok -
POST /companies/<uuid:pk>/folders— user — ok -
GET /companies/<uuid:pk>/accounts— user — ok -
POST /companies/<uuid:pk>/accounts— user — TODO
💳 Company Accounts
-
GET /company-accounts— admin — ok -
POST /company-accounts— admin — ok -
GET /company-accounts/<uuid:pk>— admin — ok -
PATCH /company-accounts/<uuid:pk>— admin — ok -
DELETE /company-accounts/<uuid:pk>— admin — ok -
POST /accounts/verify— user — TODO- required:
phone,code
- required:
🌐 Banks
GET /banks— admin — okPOST /banks— admin — okGET /banks/<uuid:pk>— admin — okDELETE /banks/<uuid:pk>— admin — okPATCH /banks/<uuid:pk>— admin — ok
📍 Contracts
GET /contracts— admin — okPOST /contracts— user — okGET /contracts/<uuid:pk>— admin — okDELETE /contracts/<uuid:pk>— admin — okPATCH /contracts/<uuid:pk>— admin — okGET /contracts/<uuid:pk>/files— user — okGET /contracts/<uuid:pk>/owners— user — ok
📄 Contract Owners
GET /contract-owners— admin — okPOST /contract-owners— admin — okGET /contract-owners/<uuid:pk>— admin — okDELETE /contract-owners/<uuid:pk>— admin — okPATCH /contract-owners/<uuid:pk>— admin — okGET /contract-owners/<uuid:pk>/contract— user — okPOST /contract-owners/<uuid:pk>/files— user — not okGET /contract-owners/<uuid:pk>/files— user — not okDELETE /contract-owners/<uuid:pk>/files/<uuid:pk>— user — okPOST /contract-owners/<uuid:pk>/files/<uuid:pk>/upload— user — ok
📂 Files
GET /files— admin — okPOST /files— admin — okGET /files/<uuid:pk>— admin — okDELETE /files/<uuid:pk>— admin — okPATCH /files/<uuid:pk>— admin — ok
📁 Folders
GET /folders— admin — okPOST /folders— admin — okGET /folders/<uuid:pk>— admin — okDELETE /folders/<uuid:pk>— admin — okPATCH /folders/<uuid:pk>— admin — okGET /folders/<uuid:pk>/contracts— admin — ok
📋 File Contents
GET /file-contents— admin — okPOST /file-contents— admin — okGET /file-contents/<uuid:pk>— admin — okDELETE /file-contents/<uuid:pk>— admin — okPATCH /file-contents/<uuid:pk>— admin — ok
This structure ensures developers can navigate quickly, see responsibilities by domain, and easily track implementation status. Update it regularly as your API evolves.