API Documentation

⏰ Send Event Reminder Notification

POST https://api.drp-ncnmo.org/send_event_reminder.php

Content-Type: application/json

Description:

This endpoint sends a reminder push notification to all users who have saved or are attending a specific event. The event ID is required and is used to fetch event details and identify all users linked to the event. Notifications are sent using Expo push notifications.

A custom reminder message can optionally be provided. If not provided, a default reminder message will be sent based on the event title.

Request Body Parameters:

• event_id (required) - The ID of the event
• message (optional) - Custom reminder message

Sample Request:

{
  "event_id": 12,
  "message": "Reminder: The event starts in 1 hour at the main hall."
}

Sample Success Response:

{
  "success": true,
  "message": "Reminder notifications sent successfully",
  "sent_to": 25
}

Sample Error Response (Missing Event ID):

{
  "success": false,
  "message": "Missing required field: event_id"
}

Sample Error Response (Event Not Found):

{
  "success": false,
  "message": "Event not found"
}

Notes:

• Only users who have saved or are linked to the event will receive notifications.
• Notifications are sent via Expo push notification service.
• If no users are found, the API will still return success with sent_to = 0.

👥 Get Event Attendees Details

POST https://api.drp-ncnmo.org/get_event_attendees.php

Content-Type: application/json

Description:

This endpoint retrieves detailed information about all users attending (or who have saved) a specific event. The event ID is provided in the request body. The system fetches all matching emails from the mysaved_event table and joins them with the ncnmo_table to return full user profiles.

This is useful for displaying attendee lists, managing event participants, or sending targeted notifications.

Request Body Parameters:

• event_id (required) - The ID of the event

Sample Request:

{
  "event_id": 12
}

Sample Success Response:

{
  "status": "success",
  "event_id": 12,
  "count": 2,
  "data": [
    {
      "id": 1,
      "firstName": "John",
      "lastName": "Doe",
      "email": "john@example.com",
      "city": "Benin",
      "state": "Edo",
      "profession": "Developer",
      "bio": "Software engineer",
      "birthMonth": "June",
      "birthYear": 1998,
      "chapter": "Edo",
      "mentorship": "Yes",
      "mentorAreas": "Tech",
      "verify_status": "verified",
      "business_link": "",
      "created_at": "2024-01-10 12:00:00",
      "profile_picture": "profile.jpg",
      "email_verified": "YES"
    }
  ]
}

Sample Error Response (Missing Event ID):

{
  "status": "error",
  "message": "Missing required field: event_id"
}

Notes:

• Uses mysaved_event table to identify attendees.
• User details are fetched from ncnmo_table using email as the link.
• Returns unique users only (duplicates removed using GROUP BY email).
• If no attendees are found, an empty array is returned with count = 0.

🏷️ Get Event Tags

GET https://api.drp-ncnmo.org/get_event_tags.php

Content-Type: application/json

Description:

This endpoint retrieves all available event tags used for categorizing events. Tags are returned in alphabetical order and can be used to populate category dropdowns during event creation or editing.

Sample Request:

GET /get_event_tags.php

Sample Success Response:

{
  "status": "success",
  "data": [
    {
      "id": 1,
      "name": "lecture"
    },
    {
      "id": 2,
      "name": "workshop"
    },
    {
      "id": 3,
      "name": "conference"
    }
  ]
}

Sample Error Response (No Tags Found):

{
  "status": "error",
  "message": "No event tags found."
}

✅ Submit Verification Request

POST https://api.drp-ncnmo.org/verify_account.php

Content-Type: application/json

Sample Request Body:

{
  "email": "user@example.com"
}

Sample Success Response:

{
  "status": "success",
  "message": "Your verification is under processing"
}

Sample Error Response (Email Not Provided):

{
  "status": "error",
  "message": "Email is required"
}

Sample Error Response (Update Failed):

{
  "status": "error",
  "message": "Failed to update verification status"
}

🔔 Push Notification — Question Answered

Description:

This push notification is sent via Expo Push Notifications when a response is posted to a community question. The notification is delivered to the user who originally asked the question.

Notifications are only sent if the user has a valid Expo push token registered in the system.

Trigger:

• An admin or authorized user submits a response to a question
• The question status is updated to Answered

Notification Title:

📝 Your Question Has Been Answered

Notification Body:

A response has been posted to your question. Tap to view it.

Notification Data Payload:

The following data object is included in the push notification payload and can be used by the mobile application for deep linking or navigation.

{
  "question_id": 45,
  "type": "community_answer"
}

Payload Field Notes:

• question_id – Unique ID of the answered question
• type – Notification type identifier. Used by the mobile app to determine navigation behavior.

Mobile App Handling (Recommended):

When type = "community_answer", the mobile app should:

• Open the community questions section
• Navigate directly to the answered question using question_id

Notes:

• Notifications are sent only if a valid Expo push token exists
• Duplicate or invalid tokens are automatically ignored
• This notification is informational and non-dismissible

🎓 Submit Mentor Answer & Notify User

POST /https://api.drp-ncnmo.org/mentorship/answerQuestion.php

Content-Type: application/json

Purpose:

Allows a mentor to submit an answer to a user's question. Once the answer is saved, the user who asked the question will receive a push notification if they have Expo tokens registered.

Required Request Body:

{
  "questionId": 42,
  "response": "Here is your answer with guidance...",
  "mentorName": "John Doe",
  "mentorEmail": "john@example.com"
}

Success Response:

{
  "success": true,
  "message": "Answer submitted successfully",
  "notified_devices": 2
}

notified_devices indicates how many Expo tokens received the push notification.

Possible Error Responses:

Missing Required Field:

{
  "success": false,
  "message": "Missing required field: response"
}

Question Not Found:

{
  "success": false,
  "message": "Question not found"
}

Failed to Save Response:

{
  "success": false,
  "message": "Failed to save response",
  "error": "Detailed database error"
}

Invalid Method:

{
  "success": false,
  "message": "Only POST method is allowed"
}

Push Notification Details:

When the answer is submitted, the questioner receives a push notification via Expo:

• Title: 🎓 Your Question Has Been Answered
• Body: A mentor has replied to your question. Tap to view the answer.
• Data Payload:

{
  "question_id": 42,
  "type": "mentorship_answer"
}

Notes:

• If the user has no registered Expo tokens, no push is sent but the answer is still saved.
• Ensure the mentor submitting the answer has proper authorization in your application logic (not handled in this API).

🚨 Report Question

POST https://api.drp-ncnmo.org/reportCommunityQuestion.php

Content-Type: application/json

Description:

Allows a user to report a question. The endpoint records the reporter's email, the question ID, and information about the question poster. Duplicate reports by the same reporter for the same question are not allowed.

Request Body (JSON):

{
  "reporterEmail": "reporter@example.com",
  "questionId": 123
}

Request Parameters:

• reporterEmail (required) — Email of the user reporting the question
• questionId (required) — ID of the question being reported

Response Fields:

• success — true if the report was successful, false otherwise
• message — Details about the result or error

Sample Success Response:

{
  "success": true,
  "message": "Question reported successfully"
}

Sample Error Response (Duplicate Report):

{
  "success": false,
  "message": "You have already reported this question"
}

Sample Error Response (Missing Fields):

{
  "success": false,
  "message": "reporterEmail or questionId not provided in JSON body"
}

Sample Error Response (Question Not Found):

{
  "success": false,
  "message": "Question not found"
}

🚨 Report Mentorship Question

POST https://api.drp-ncnmo.org/reportMentorshipQuestion.php

Content-Type: application/json

Description:

Allows a user to report a mentorship question. The endpoint records the reporter's email, the mentorship question ID, and information about the question poster. Duplicate reports by the same reporter for the same question are not allowed.

Request Body (JSON):

{
  "reporterEmail": "reporter@example.com",
  "questionId": 123
}

Request Parameters:

• reporterEmail (required) — Email of the user reporting the mentorship question
• questionId (required) — ID of the mentorship question being reported

Response Fields:

• success — true if the report was successful, false otherwise
• message — Details about the result or error

Sample Success Response:

{
  "success": true,
  "message": "Mentorship question reported successfully"
}

Sample Error Response (Duplicate Report):

{
  "success": false,
  "message": "You have already reported this mentorship question"
}

Sample Error Response (Missing Fields):

{
  "success": false,
  "message": "reporterEmail or questionId not provided in JSON body"
}

Sample Error Response (Question Not Found):

{
  "success": false,
  "message": "Mentorship question not found"
}

🔍 Check Block Status

POST https://api.drp-ncnmo.org/checkBlockStatus.php

Content-Type: application/json

Description:

Checks whether a user (blocker_email) has blocked another user (blocked_email). This endpoint verifies a one-directional block relationship.

Request Body (JSON):

{
  "blocker_email": "john@example.com",
  "blocked_email": "jane@example.com"
}

Request Parameters:

• blocker_email (required) — Email of the user who may have blocked another user
• blocked_email (required) — Email of the user being checked

Response Fields:

• isBlocked — YES if blocked, NO if not blocked

Sample Success Response (Blocked):

{
  "success": true,
  "blocker_email": "john@example.com",
  "blocked_email": "jane@example.com",
  "isBlocked": "YES"
}

Sample Success Response (Not Blocked):

{
  "success": true,
  "blocker_email": "john@example.com",
  "blocked_email": "mark@example.com",
  "isBlocked": "NO"
}

Sample Error Response:

{
  "success": false,
  "message": "blocker_email and blocked_email are required"
}

🚫 Block User

POST https://api.drp-ncnmo.org/blockUser.php

Content-Type: application/json

Description:

Allows a user to block another user. Once blocked:

• The blocked user will no longer appear in user listings
• The blocker and blocked user will not see each other’s content

Request Body (JSON):

{
  "blocker_email": "john@example.com",
  "blocked_email": "jane@example.com"
}

Request Parameters:

• blocker_email (required) — Email of the user performing the block
• blocked_email (required) — Email of the user being blocked

Sample Success Response:

{
  "success": true,
  "message": "User blocked successfully"
}

Sample Error Responses:

{
  "success": false,
  "message": "blocker_email and blocked_email are required"
}

{
  "success": false,
  "message": "You cannot block yourself"
}

✅ Unblock User

POST https://api.drp-ncnmo.org/unblockUser.php

Content-Type: application/json

Description:

Allows a user to unblock a previously blocked user. Once unblocked:

• The users may appear in each other’s listings again
• Content visibility is restored

Request Body (JSON):

{
  "blocker_email": "john@example.com",
  "blocked_email": "jane@example.com"
}

Request Parameters:

• blocker_email (required) — Email of the user performing the unblock
• blocked_email (required) — Email of the user being unblocked

Sample Success Response:

{
  "success": true,
  "message": "User unblocked successfully"
}

Sample Error Response:

{
  "success": false,
  "message": "blocker_email and blocked_email are required"
}

📌 Report an Event

POST /https://api.drp-ncnmo.com/reportEvent.php

Content-Type: application/json

Description:

Allows a user to report an event by its event_id. The API uses the event_id to look up the original poster (posted_by) and their email in the event_table. A report is created with the reporter's name and email, the reported user's name and email, the event ID, and a default status of pending.

JSON Input:

{
  "reporter_name": "Jane Doe",
  "reporter_email": "jane@example.com",
  "event_id": 123
}

Sample Response (Success):

{
  "status": "received",
  "report_id": "550e8400-e29b-41d4-a716-446655440000"
}

Sample Error Responses:

Missing Required Fields:

{
  "error": "Missing required fields"
}

Event Not Found:

{
  "error": "Event not found"
}

Database Error:

{
  "error": "Failed to create event report"
}

📌 Report a User

POST /https://api.drp-ncnmo.com/reportUser.php

Content-Type: application/json

Description:

Allows an authenticated or identified user to report another user for misconduct. The API stores the reporter's and reported user's names and emails along with the reason for reporting. Each report is assigned a unique report_id and a default status of pending.

JSON Input:

{
  "reporter": {
    "name": "Jane Doe",
    "email": "jane@example.com"
  },
  "reported_user": {
    "name": "John Smith",
    "email": "john@example.com"
  },
  "reason": "Harassment"
}

Sample Response (Success):

{
  "status": "received",
  "report_id": "550e8400-e29b-41d4-a716-446655440000"
}

Sample Error Responses:

Missing Required Fields:

{
  "error": "Missing required fields"
}

Self-Reporting Attempt:

{
  "error": "You cannot report yourself"
}

Database Error:

{
  "error": "Failed to create report"
}

📌 Get Verification Status

POST /https://api.drp-ncnmo.com/knackApi.php

Content-Type: application/json

Description:

Checks the user's verify_status from ncnmo_table using the provided email. The API returns the exact verification status stored in the database (for example: unverified, pending, verified, rejected).

JSON Input:

{
  "email": "user@example.com"
}

Sample Response (Unverified User):

{
  "status": "unverified",
  "message": "Account status fetched successfully."
}

Sample Response (Pending User):

{
  "status": "pending",
  "message": "Account status fetched successfully."
}

Sample Response (Verified User):

{
  "status": "verified",
  "message": "Account status fetched successfully."
}

Sample Error Responses:

Missing Email:

{
  "status": "error",
  "message": "Missing email in JSON body"
}

Email Not Found:

{
  "status": "error",
  "message": "Email not found."
}

Database Error:

{
  "status": "error",
  "message": "Database query failed",
  "details": "SQL error message here"
}

📌 Get All Sub Categories

GET /https://api.drp-ncnmo.com/sub_category.php

Content-Type: application/json

Description:

Retrieves all records from the sub_category table. The endpoint returns full details including ID, name, image, category info, location, icon, and more.

Table Fields Returned:

• id
• sub_name
• sub_details
• location
• sub_image
• cat_id
• cat_name
• icon
• convention
• learn_more

Sample Success Response:

{
  "status": "success",
  "total": 3,
  "data": [
    {
      "id": "1",
      "sub_name": "Programming",
      "sub_details": "Learn coding and more",
      "location": "Online",
      "sub_image": "programming.jpg",
      "cat_id": "10",
      "cat_name": "Education",
      "icon": "code-icon.png",
      "convention": "2025-02-01",
      "learn_more": "https://example.com/programming"
    }
  ]
}

Sample Error Response:

{
  "status": "error",
  "message": "Database query failed",
  "details": "SQL error message here"
}

📌 Verify Email Status

POST /https://api.drp-ncnmo.com/verify_status.php

Content-Type: application/json

Description:

Retrieves the verify_status of a user from ncnmo_table using the user's email address. The email must be supplied in the JSON body.

JSON Input:

{
  "email": "user@example.com"
}

Sample Success Response:

{
  "verify_status": "verified"
}

Sample Error Responses:

Missing Email:

{
  "error": "Email not provided"
}

Email Not Found:

{
  "error": "Email not found"
}

Database Error:

{
  "error": "Database query failed",
  "details": "SQL error message here"
}

📌 Delete User Account

POST /https://api.drp-ncnmo.com/delete_account.php

Content-Type: application/json

Description:

Deletes a user account from ncnmo_table using the user's email address. Also removes any associated mentor profile from the mentors table. Email must be supplied in the JSON body.

JSON Input:

{
  "userEmail": "user@example.com"
}

Sample Success Response:

{
  "status": "success",
  "message": "User account deleted successfully"
}

Sample Error Responses:

Missing Email:

{
  "status": "error",
  "message": "Missing userEmail in request body"
}

Invalid Email Format:

{
  "status": "error",
  "message": "Invalid email format"
}

User Not Found:

{
  "status": "error",
  "message": "No user found with this email"
}

Database Failure:

{
  "status": "error",
  "message": "Database query failed",
  "error": "SQL error message here"
}

📌 Get Event by Slug

POST https://api.drp-ncnmo.org/get_event_by_slug.php

Content-Type: application/json

Description:

Fetches a single event from event_table using a unique event slug. Optionally checks whether a user is attending the event when userEmail is provided.

JSON Input:

{
  "slug": "national-conference-2025",
  "userEmail": "user@example.com"
}

Note: userEmail is optional. If not provided, the API will return "attending": "No".

Sample Success Response:

{
  "status": "success",
  "event": {
    "id": "14",
    "title": "National Conference 2025",
    "slug": "national-conference-2025",
    "date_start": "2025-12-15",
    "event_datetime_utc": "2025-12-15 14:30:00",
    "event_date": "2025-12-15",
    "event_time": "14:30",
    "location": "Texas",
    "cat_id": "3",
    "cat_name": "Convention",
    "subcategory_id": "12",
    "subcategory_name": "Annual",
    "details": "Event details info...",
    "image": "event14.jpg",
    "posted_by": "Admin",
    "email": "admin@ncnmo.com",
    "date": "2025-01-15",
    "status": "active",
    "interest": "0",
    "info": "upcoming",
    "gender": "Both",
    "chapter": "National",
    "event_group": "",
    "event_tag": "NCNMO",
    "year": "2025",
    "off": "0",
    "attending": "Yes",
    "image_type": "png"
  }
}

Sample Error Responses:

Missing Slug:

{
  "status": "error",
  "message": "Missing slug in JSON input"
}

Event Not Found:

{
  "status": "error",
  "message": "Event not found for slug: national-conference-2025"
}

Database Failure:

{
  "status": "error",
  "message": "Database query failed",
  "error": "SQL error message here"
}

📸 Update Profile Photo

POST https://api.drp-ncnmo.org/updatePhoto.php

Content-Type: application/json

Description:

Updates the user's profile picture. The image must be sent as a Base64 encoded string because mobile apps (React Native) cannot upload files using $_FILES.

JSON Request Body:

{
  "userEmail": "example@gmail.com",
  "profile_picture": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA..."
}

Fields:

• userEmail — User's registered email address.
• profile_picture — Base64 encoded image (PNG, JPG, JPEG, GIF).

Sample Success Response:

{
  "status": "success",
  "message": "Profile picture updated successfully.",
  "profile_picture_url": "https://yourdomain.com/uploads/profile_67392abc17.png"
}

Sample Error Responses:

Missing fields:

{
  "status": "error",
  "message": "Missing userEmail or profile_picture."
}

Invalid Base64 string:

{
  "status": "error",
  "message": "Invalid base64 image data."
}

Database or file save error:

{
  "status": "error",
  "message": "Failed to save profile picture."
}

🔐 Update Password

POST /https://api.drp-ncnmo.com/updatePassword.php

Content-Type: application/json

Description:

Allows a user to securely update their account password. The API verifies the user's current password before applying the change.

JSON Input:

{
  "userEmail": "user@example.com",
  "current_password": "oldpassword123",
  "new_password": "newstrongpassword456",
  "confirm_password": "newstrongpassword456"
}

Sample Success Response:

{
  "status": "success",
  "message": "Password updated successfully."
}

Sample Error Responses:

Missing Fields:

{
  "status": "error",
  "message": "All fields are required."
}

Incorrect Current Password:

{
  "status": "error",
  "message": "Current password is incorrect."
}

Password Mismatch:

{
  "status": "error",
  "message": "New password and confirmation do not match."
}

User Not Found:

{
  "status": "error",
  "message": "User not found."
}

📘 Fetch Event Thread Messages

POST /https://drp-ncnmo.com/event_thread.php

Content-Type: application/json

Description:

Fetches all messages for a specific event. Messages are returned in chronological order along with the user's name, email, avatar (first two letters of the name), and formatted creation time.

Request Body:

{
  "event_id": 123
}

Sample Success Response:

{
  "status": "success",
  "data": [
    {
      "id": 1,
      "user_name": "John Doe",
      "email": "john@example.com",
      "message": "Looking forward to this event!",
      "created_at": "Tuesday, December 10, 2025 2:30 PM",
      "avatar": "JO"
    },
    {
      "id": 2,
      "user_name": "Jane Smith",
      "email": "jane@example.com",
      "message": "Excited to join!",
      "created_at": "Tuesday, December 10, 2025 2:45 PM",
      "avatar": "JA"
    }
  ]
}

Sample Error Response (No Messages Found):

{
  "status": "error",
  "message": "No messages found for this event."
}

Sample Error Response (Missing Event ID):

{
  "status": "error",
  "message": "Missing event_id in request."
}

📘 Add Event Thread Message

POST /https://drp-ncnmo.com/insertchat.php

Content-Type: application/json

Description:

Adds a new message to an event thread. All fields are required. The API returns the message details, creation time, and a user avatar generated from the first two letters of the user name.

Request Body:

{
  "event_id": 123,
  "user_name": "John Doe",
  "email": "john@example.com",
  "message": "Looking forward to this event!"
}

Sample Success Response:

{
  "success": true,
  "user_name": "John Doe",
  "message": "Looking forward to this event!",
  "created_at": "Tuesday, December 10, 2025 2:30 PM",
  "avatar": "JO"
}

Sample Error Response (Missing Fields):

{
  "success": false,
  "error": "Missing fields"
}

Sample Error Response (Database Failure):

{
  "success": false,
  "error": "Database insert failed"
}

📘 Attend / Unattend Event

POST /https://drp-ncnmo/attend-event.php

Content-Type: application/json

Description:

Marks the user as attending or unattending an event. The user email and event slug must be provided in the request body. The "action" parameter determines whether to attend or unattend ("attend" or "unattend").

Request Body:

{
  "slug": "event-123",
  "userEmail": "user@example.com",
  "action": "attend"
}

Sample Success Response (Attend):

{
  "status": "attended"
}

Sample Success Response (Already Attending):

{
  "status": "exists"
}

Sample Success Response (Unattend):

{
  "status": "unattended"
}

Sample Error Response:

{
  "status": "error",
  "message": "Event not found"
}

📘 Delete Event (User-Specific)

POST /https://drp-ncnmo.com/api/delete_event.php

Content-Type: application/json

Description:

Deletes a specific event **only if it belongs to the user making the request**. The event ID and the user's email must be provided in the JSON request body. Users who saved the event will be notified via email of its cancellation.

Request Body:

{
  "id": 123,
  "userEmail": "user@example.com"
}

Sample Success Response:

{
  "status": "success",
  "message": "Event deleted and all affected users notified."
}

Sample Partial Success Response (Some emails failed):

{
  "status": "partial_success",
  "message": "Event deleted, but some emails failed.",
  "errors": [
    "Failed to send to user1@example.com: SMTP Error",
    "Failed to send to user2@example.com: SMTP Error"
  ]
}

Sample Error Responses:

{
  "status": "error",
  "message": "Invalid request: missing event ID or userEmail."
}

{
  "status": "error",
  "message": "Event not found or you do not have permission to delete it."
}

📘 Get Chapters

GET /https://api.drp-ncnmo.org/getChapters.php

Content-Type: application/json

Description:

Fetches a list of all chapters sorted alphabetically by name.

Sample Success Response:

{
  "status": "success",
  "data": [
    {
      "id": "1",
      "name": "Introduction"
    },
    {
      "id": "2",
      "name": "Getting Started"
    }
  ]
}

Sample Empty Response:

{
  "status": "error",
  "message": "No chapters found."
}

📝 User Registration

POST /https://api.drp-ncnmo.org/register.php

Content-Type: application/json

Sample Request Body:

{
  "firstName": "Opeyemi",
  "lastName": "Wasiu",
  "email": "ope@example.com",
  "password": "123456",
  "confirmPassword": "123456",
  "city": "Lagos",
  "state": "Lagos",
  "profession": "Developer",
  "bio": "Software developer",
  "birthMonth": "June",
  "birthYear": "1995",
  "chapter": "West",
  "mentorship": "Yes",
  "mentorAreas": ["Web Development", "Career Growth"]
}

Sample Success Response:

{
  "success": true,
  "message": "Registration successful. Please check your email for verification code."
}

✅ Email Verification

POST /https://api.drp-ncnmo.org/verify.php

Content-Type: application/json

Sample Request Body:

{
  "email": "ope@example.com",
  "otp": "123456"
}

Sample Success Response:

{
  "success": true,
  "message": "Email verified successfully."
}

Sample Invalid OTP Response:

{
  "success": false,
  "message": "Invalid OTP."
}

Sample Email Already Verified Response:

{
  "success": true,
  "message": "Email already verified."
}

🔄 Resend Verification Code

POST /https://api.drp-ncnmo.org/resendVerification.php

Content-Type: application/json

Sample Request Body:

{
  "email": "ope@example.com"
}

Sample Success Response:

{
  "success": true,
  "message": "New verification code sent to your email."
}

Sample Email Already Verified Response:

{
  "success": true,
  "message": "Email already verified."
}

🔑 User Login (JWT Enabled)

POST https://api.drp-ncnmo.org/login.php

Content-Type: application/json

Authenticates a user and returns a JWT token. Optionally accepts an Expo Push Token to enable push notifications on the user’s device.

Request Body Parameters:

• email (required) – User’s email address
• password (required) – User’s password
• expo_token (optional) – Expo push notification token for the device

Sample Request Body:

{
  "email": "ope@example.com",
  "password": "123456",
  "expo_token": "ExponentPushToken[xxxxxxxxxxxxxxxxxxxxxx]"
}

Note: The expo_token is optional. Login will succeed even if it is not provided.

Sample Success Response:

{
  "success": true,
  "message": "Login successful.",
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI...",
  "user": {
    "id": 12,
    "name": "Opeyemi Wasiu",
    "email": "ope@example.com"
  }
}

Sample Email Not Verified Response:

{
  "success": false,
  "message": "Email not verified. Please verify your email.",
  "email": "ope@example.com"
}

Sample Invalid Password Response:

{
  "success": false,
  "message": "Invalid password."
}

Sample Email Not Found Response:

{
  "success": false,
  "message": "Email not found."
}

🚪 User Logout (Remove Device Token)

POST https://api.drp-ncnmo.org/logout.php

Logs out the authenticated user by removing the current device’s Expo Push Notification token. This prevents further push notifications from being sent to that device.

Headers:

• Authorization: Bearer <JWT_TOKEN>
• Content-Type: application/json

Request Body Parameters:

• expo_token (required) – Expo push token of the device to log out

Sample Request:

POST /logout.php
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI...
Content-Type: application/json

{
  "expo_token": "ExponentPushToken[xxxxxxxxxxxxxxxxxxxxxx]"
}

Sample Success Response:

{
  "success": true,
  "message": "Logout successful. Device token removed."
}

Sample Token Already Removed Response:

{
  "success": true,
  "message": "Logout successful. Token already removed."
}

Sample Unauthorized Response:

{
  "success": false,
  "message": "Invalid or expired token."
}

Sample Missing Token Response:

{
  "success": false,
  "message": "expo_token is required for logout."
}

📅 Get Trending Event

GET /https://api.drp-ncnmo.org/getTrendingEvent.php

Sample Success Response:

{
  "success": true,
  "event": {
    "id": 5,
    "name": "Tech Expo",
    "details": "Annual technology conference",
    "location": "New York",
    "date": "2025-01-20",
    "timeUntil": "in 3 weeks",
    "sub_image": "expo.jpg",
    "learn_more": "https://example.com/expo"
  }
}

Sample When No Event Found:

{
  "success": false,
  "message": "No upcoming event found.",
  "event": {
    "id": 0,
    "name": "No Upcoming Event",
    "details": "Stay tuned for the next big conference!",
    "location": "—",
    "timeUntil": ""
  }
}

📂 Get Event Categories

GET /https://api.drp-ncnmo.org/getCategories.php

Sample Success Response:

{
  "success": true,
  "categories": [
    {
      "id": 1,
      "name": "Music",
      "slug": "music",
      "details": "All musical events and concerts."
    },
    {
      "id": 2,
      "name": "Technology",
      "slug": "technology",
      "details": "Tech meetups and conferences."
    }
  ]
}

Sample No Categories Response:

{
  "success": false,
  "message": "No categories found.",
  "categories": []
}

👤 Update Profile

POST https://api.drp-ncnmo.org/update_profile.php

Content-Type: application/json

📩 Sample JSON Request Body

{
  "email": "john@example.com",
  "bio": "Software developer and mentor",
  "profession": "Developer",
  "business_link": "https://mybusiness.com",
  "chapter": "West",
  "provideMentorship": "Yes",
  "topics": [
    "careerDevelopment",
    "entrepreneurship"
  ]
}

📤 Sample Success Response

{
  "status": "success",
  "message": "Profile updated successfully!",
  "data": {
    "bio": "Software developer and mentor",
    "profession": "Developer",
    "business_link": "https://mybusiness.com",
    "chapter": "West",
    "mentorship": "Yes",
    "mentorAreas": "careerDevelopment,entrepreneurship"
  }
}

⚠️ Sample Error Response (User Not Found)

{
  "status": "error",
  "message": "User not found"
}

⚠️ Sample Error Response (Invalid JSON)

{
  "status": "error",
  "message": "Invalid JSON input"
}

👤 Get Profile

POST https://api.drp-ncnmo.org/getProfile.php

Content-Type: application/json

📩 Sample JSON Request Body

{
  "email": "john@example.com"
}

📤 Sample Success Response

{
  "status": "success",
  "message": "Profile retrieved successfully",
  "data": {
    "firstName": "John",
    "lastName": "Doe",
    "email": "john@example.com",
    "city": "Charlotte",
    "state": "NC",
    "profession": "Engineer",
    "bio": "Experienced mechanical engineer",
    "chapter": "West",
    "business_link": "https://johndoe.com",
    "mentorship": "Yes",
    "mentorAreas": "Leadership,Career Development",
    "profile_picture": "uploads/profile_12abcd.png"
  }
}

⚠️ Sample Error Response (User Not Found)

{
  "status": "error",
  "message": "User not found"
}

⚠️ Sample Error Response (Invalid JSON)

{
  "status": "error",
  "message": "Invalid JSON input"
}

⚠️ Notes

• The API accepts only POST requests.
• Input must be valid JSON with email field.
• Returns all profile fields including mentorship info and mentor areas.
• Profile picture path is returned relative to the uploads/ directory.

🔒 Reset Password

POST /https://api.drp-ncnmo.org/reset_password_api.php

Content-Type: application/x-www-form-urlencoded

Sample Request Fields:

current_password: "oldpassword123"
new_password: "newpassword456"
confirm_password: "newpassword456"
    

Sample Success Response:

{
  "status": "success",
  "message": "Password updated successfully!"
}

Sample Error Responses:

{
  "status": "error",
  "message": "Current password is incorrect."
}

{
  "status": "error",
  "message": "New password and confirmation do not match."
}

{
  "status": "error",
  "message": "Please fill in all fields."
}

🔑 Forgot Password

POST /https://api.drp-ncnmo.org/forgot_password.php

Content-Type: application/json

{
"email": "user@example.com"
}

Sample Success Response:

{
"success": true,
"message": "Password reset link has been sent to your email."
}

Sample Error Response (email not found):

{
"success": false,
"message": "Email address not registered."
}