BasicPSF · Pepkor Product Solutions
API Documentation
This documentation covers the endpoints used to integrate with the BasicPSF platform on behalf of Pepkor Product Solutions. All endpoints use the BasicPSF API over HTTPS.
Available Endpoints
PATCH
Push Booking Result — Single
/fmi/data/vLatest/databases/{db}/layouts/QC_Booking/records/{id}
Push a single QC booking result in real time immediately after a booking is confirmed or rejected. One call per booking.
→
POST
Push Booking Results — Batch
/fmi/data/vLatest/databases/{db}/layouts/QC_Booking/script/CLIV Booking Results Batch
Push multiple QC booking results in a single call. Use for scheduled or queued batch jobs where multiple bookings have been processed together.
→
When to use each endpoint
Single (PATCH)
Use when confirming or rejecting one booking in real time, immediately after it is processed on the CLIV platform.
Batch (POST)
Use when pushing a queue of results together in a scheduled or end-of-day job. All results are sent in one authenticated call.
Environments
UAT / Testing
Host
pps.basicpsf.com
Database
BasicPSF_Test
Status
Active
Production
Host
pps.basicpsf.com
Database
BasicPSF_PPS
Status
Active
Authentication
All endpoints use the BasicPSF API session-based authentication. A session token must be obtained before each request and included as a Bearer token in the Authorization header. Full authentication details are covered on each endpoint page.
Key Points
Auth method
Session token (Bearer)
Token lifetime
15 min inactivity
Login endpoint
POST /fmi/data/vLatest/databases/{db}/sessions
Credentials
Provided via secure channel