Skip to main content
tibs-api is now the real shared backend service for TIBS. The OpenAPI files in this docs repo are synced from the API repository and should be treated as a live contract snapshot, not a future draft.

​
Live service

  • Base service URL: https://tibs-api.onrender.com
  • Versioned base path: /api/v1
  • Health check: https://tibs-api.onrender.com/api/v1/health
  • Swagger UI: https://tibs-api.onrender.com/api/docs
  • Redoc: https://tibs-api.onrender.com/api/redoc
  • Live OpenAPI JSON: https://tibs-api.onrender.com/api/openapi.json
  • Live OpenAPI YAML: https://tibs-api.onrender.com/api/openapi.yaml
This docs repo also keeps synced snapshots for reference:

​
Authentication and access

Access modelHow it worksTypical routes
PublicNo token required/api/v1/health
Bearer tokenAuthorization: Bearer <supabase_access_token>most non-public routes
External API keyX-API-KEY: tibs_live_<prefix>_<secret> on selected read-only routessearch, incidents, vehicles, corridors, routes, saccos
Surveyor roleBearer token plus surveyor role/api/v1/surveyor/*
Admin roleBearer token plus admin role/api/v1/admin/*

​
Current domains

DomainRepresentative routes
HealthGET /api/v1/health
AuthGET /api/v1/auth/me
API keysGET /api/v1/api-keys, POST /api/v1/api-keys, DELETE /api/v1/api-keys/{id}
ReportsPOST /api/v1/reports
IncidentsGET /api/v1/incidents/nearby, GET /api/v1/incidents/{id}
VehiclesGET /api/v1/vehicles/{identifier}, GET /api/v1/vehicles/{identifier}/incidents
FeedbackPOST /api/v1/feedback, GET /api/v1/vehicles/{identifier}/feedback-summary
CorridorsGET /api/v1/corridors, GET /api/v1/corridors/{id}/incidents
RoutesGET /api/v1/routes
SaccosGET /api/v1/saccos, GET /api/v1/saccos/{id}/vehicles
SearchGET /api/v1/search
LearningGET /api/v1/learning/courses, GET /api/v1/learning/progress
SurveyorPOST /api/v1/surveyor/session/start, GET /api/v1/surveyor/assignments, GET /api/v1/surveyor/stats
AdminGET /api/v1/admin/review-queue, POST /api/v1/admin/review, GET/PUT /api/v1/admin/users/{userId}/roles

​
Quick examples

Bearer-authenticated request: 
curl -sS "https://tibs-api.onrender.com/api/v1/auth/me" \
  -H "Authorization: Bearer $TOKEN"
External API key request: 
curl -sS "https://tibs-api.onrender.com/api/v1/search?q=rongai" \
  -H "X-API-KEY: $EXTERNAL_API_KEY"

​
How to use this section

  • Use this page when you want the real shared backend service used across TIBS.
  • Use the synced OpenAPI files for generators, SDK work, and schema review.
  • Use the repo-specific interface pages when you need the remaining Next.js route handlers and auth callbacks still living in tibs, tibs-survey, or tibs-learning-center.

Live interfaces

See how the dedicated API service fits alongside the remaining app-specific route handlers.

API introduction

Start at the section overview if you need the full map of API documentation in this site.