API Documentation

Authentication

Every request must include a personal access token as a Bearer token in the Authorization header. Generate a token from your Partner Dashboard → API Access (login required).

Authorization: Bearer <your-token>

Returns puja bookings assigned to the authenticated Pandit partner. Pandit partners only — Acharya/other partner types receive a 403.

Example request:

curl https://www.smcty.melonkode.com/api/partner/bookings \
  -H "Authorization: Bearer <your-token>" \
  -H "Accept: application/json"

Example response:

{
  "data": [
    {
      "booking_no": "SMCS-PJ-000042",
      "devotee_name": "Rajesh Kumar",
      "phone": "9876543210",
      "preferred_date": "2026-09-15",
      "city": "Patna",
      "status": "pandit_assigned",
      "payment_status": "unpaid"
    }
  ]
}

Returns Kundali orders assigned to the authenticated Acharya partner. Acharya partners only — Pandit/other partner types receive a 403.

Example request:

curl https://www.smcty.melonkode.com/api/partner/kundali-orders \
  -H "Authorization: Bearer <your-token>" \
  -H "Accept: application/json"

Example response:

{
  "data": [
    {
      "order_no": "SMCS-KD-000017",
      "devotee_name": "Sunita Devi",
      "mobile": "9876543210",
      "service": "Janma Kundali",
      "status": "processing"
    }
  ]
}

Notes

• Both endpoints are read-only — there is currently no write API.
• Data is scoped strictly to your own partner profile; there is no way to fetch another partner's records.
• Revoke a token any time from your Partner Dashboard if it's compromised.