Partner Account
Every integration starts with an approved partner account. Public requests are reviewed before sandbox or production access is activated.
Developers
Build with the One Siargao Pass API.
Approved partners can connect booking references, traveler records, pass status, QR readiness, and governed webhook workflows into OSP through reviewed partner access.
Platform Gateway
Website outside. Mobile app inside.
The public website explains and routes the ecosystem. The traveler app handles pass, QR, trips, Passport Map, and mobile-first journey actions.
The API is for approved partner integrations.
OSP APIs are not open anonymous endpoints. They are governed access paths for reviewed partners who need to connect booking records, traveler context, pass readiness, and QR-backed workflows.
Booking-to-Pass Intake
Approved partners may connect confirmed booking references into OSP-managed traveler pass and QR workflows.
Audit-Ready Events
Partner actions are designed to be logged for governance, troubleshooting, and compliance review.
Approved partner flow
The integration journey starts with review, then moves into scoped access. OSP remains the pass and QR lifecycle authority throughout the flow.
- 1Submit partner requestProvide organization details, partner type, contact email, and integration use case.
- 2OSP reviews accessPartner type, booking model, operational fit, and compliance boundaries are reviewed.
- 3Scoped API accessApproved partners may proceed to sandbox or production access only after token policy is active.
API Surface
Current and planned partner API surfaces.
These routes communicate the integration direction without exposing fake token UI or unapproved production access.
POST
/api/v1/partners/apply
Public partner access request intake. Creates a pending-review partner application and audit record.
Live intake
GET
/api/v1/partners/applications/:id/status
Partner application status lookup for submitted requests.
Available
POST
/api/v1/partners/admin/api-tokens
Token issuance route remains intentionally blocked until approval, guard policy, and token scope controls are complete.
Blocked by design
POST
/api/v1/ota/trips/intake
Future approved-partner booking-to-pass intake endpoint for external booking references.
Planned