Aljezri - Home

Showing 25 of 80 from the live probe.

• Get On Demand Services For Order

  Get on-demand services available for order creation (GET /admin/orders/services/on-demand-services).

• Get Spare Parts For Order

  Get spare parts available for order creation (GET /admin/orders/services/spare-parts).

• Get Corrective Services For Order

  Get corrective services available for order creation (GET /admin/orders/services/corrective).

• Get Preventive Services For Order

  Get preventive services available for order creation (GET /admin/orders/services/preventive).

• Get Packages For Order

  Get packages available for order creation (GET /admin/orders/services/packages).

• Get Schedule For Order

  Get schedule availability for visit creation (POST /admin/orders/schedule).

• Create Order

  Create a new order: wallet pay then create. Response `data.order` includes `_id` (#sequence), `orderMongoId`, `orderSequence`, and `orderId` (same as `orderMongoId`, for H.5 spec).

• Create Visit For Order

  Create a visit for an existing order (POST /admin/orders/visits). orderId must be the order sequence (#1234 or 1234), not Mongo _id. Requires scheduledDate (ISO) and technicianTeam id.

• Get Work Order

  Retrieve a work order by ID.

• List Work Orders

  List work orders with optional filters.

• Get Visit

  Retrieve an order visit by visit sequence (admin/orders/visits).

• List Visits

  List order visits with optional filters (admin/orders/visits).

• Get Appointment

  Retrieve a work-order appointment by appointment sequence.

• List Appointments

  List appointments (scheduling) with optional filters.

• Get Facility

  Retrieve a facility by ID.

• Get Asset

  Retrieve an asset by ID.

• List Assets

  List assets by facility.

• Get Technician

  Retrieve a technician by ID.

• List Technicians

  List technicians with optional filters.

• Get Team

  Retrieve a team by ID.

• List Teams

  List technician teams, optionally filtered by operation zone, member technician, or name. Includes teams shared through service-provider agreements.

• List Notifications

  Audit feed of admin notifications — what fired, when, and how widely. Filter by date range, notificationType and role; AI alerts carry role "AI_Alerts". By default the one-row-per-recipient fan-out is collapsed into one event with recipientCount, so counts are not inflated (pass dedupe=false for raw rows). NOT tenant-scoped: AdminNotification has no domainId, so results span every domain — use role to narrow. Omitting `from` reads the last 30 days rather than the whole collection.

• List Activity Log

  Activity log for an order, work order or quotation — who did what, when. Each entry is {actor:{id,name,type}, action, details, category, timestamp}, newest first, with actor.type one of admin/customer/technician. THE LAST ADMIN ENTRY IS THE DE FACTO HANDLER of the entity — use it to decide who to @mention. entityId: order → sequence, work_order → Mongo _id, quotation → sequence. Work orders additionally return statusChanges (the status timeline).

• List Mention Admins

  Resolve a person's name to the admin _id that `mentions` requires. Returns every active admin in the domain as {_id, name, firstName, lastName, domainId}; nameContains filters client-side. Use this instead of guessing an id when a human names who to notify. Admins only — technicians cannot be mentioned.

• List Facilities

  Enumerate facilities. One compact row per facility: _id, sequence (the human-readable facilityId), name, active, city, country, domainId. Filter by name, city, country, active or free-text search. Use this to COUNT facilities — `total` is the full match count, not the page size. Note the Facility schema has no zone field and no per-facility client reference; domainId is the owning tenant.