Closed davidolanrewaju closed 1 week ago
fetching products is not a super admin matter, and so called top products is just a filter
@buka4rill
Specify status codes in all the response payload
Hello everyone @markessien, @buka4rill, @davidolanrewaju
I’ve created a new issue Implement API Endpoints for READ/GET and DELETE Subscription Plans that complements this issue. While this issue focuses on creating subscription plans, my issue addresses the endpoints required for reading, getting, and deleting those subscription plans.
The goal is to complete the suite of CRUD operations for subscription plans, ensuring a comprehensive API that covers all necessary interactions with subscription data. Please refer to the new issue #231 for details on the additional endpoints needed.
Description
Develop backend support to create subscription plans. This feature will enable admin to create various plans.
Acceptance Criteria
Error Handling:
Security Measures:
Purpose
To provide admin with the ability to create different subscription plans.
Requirements
Expected Outcome
DB Schema
Endpoints
Endpoint:
HTTP POST /api/v1/plans
Request Body:
Success Response: Create Subscription Plan
Error Response: Unauthorized Access
{ "status": 403, "error": "User is not authorized to create subscription plans." }
HTTP/1.1 400 Subscription plan already exists Content-Type: application/json
{ "status": 400, "error": "subscription plan already exists." }