Update or create pass marks

Update existing pass mark configuration or create new one if none exists (upsert operation). Use Cases:

• Update pass mark thresholds: Modify existing O-Level and A-Level pass marks
• Initial configuration: Create pass marks if none exist
• Academic policy changes: Update pass requirements for new academic year
• System reconfiguration: Change pass mark standards Upsert Behavior: The endpoint automatically determines whether to update or create:
• If configuration exists: Performs partial update (PATCH-like behavior)
• If no configuration exists: Creates new configuration
• Returns appropriate status code (200 for update, 201 for create)
• Response includes action field indicating operation performed Request Body: Accepts partial data for updates:
• o_level: Pass mark for O-Level (0-100) - Optional
• a_level: Pass mark for A-Level (0-100) - Optional
• Can update one or both fields Singleton Pattern:
• Only one pass mark configuration exists in the system
• Uses .first() to check for existing configuration
• Automatically handles create vs update logic Validation:
• Pass marks must be valid numbers (typically 0-100)
• Validation errors are caught and returned with 400 status
• Server errors are caught and returned with 500 status

PUT /api/v1/school/pass-marks/update-current

Update or create pass marks

cURL

curl --request PUT \
  --url https://api.example.com/api/v1/school/pass-marks/update-current/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "o_level": 50,
  "a_level": 50
}
'

200

Success-Updated

{
  "success": true,
  "action": "updated",
  "message": "Pass mark configuration updated successfully",
  "data": {
    "id": "uuid-123",
    "o_level": 45,
    "a_level": 50,
    "created_at": "2025-10-10T10:00:00Z",
    "updated_at": "2025-10-10T12:00:00Z"
  }
}

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/jsonapplication/x-www-form-urlencodedmultipart/form-data

Auto-populate created_by from request.user when available.

o_level · integer

Required range: 0 <= x <= 100

a_level · integer

Required range: 0 <= x <= 100

Response

200

application/json

{key} · any