Information
- OpenAPI version:
3.0.3
Overview
BRIDGEPORT API 1.0.0
Section titled “BRIDGEPORT API 1.0.0”HTTP API for BRIDGEPORT — a self-hosted deployment management tool for Docker-based infrastructure. All error responses follow the standard envelope: {code, message, field?, hint?, requestId?}.
Operations
Section titled “Operations”POST
/api/auth/loginGET
/api/auth/meDELETE
/api/environments/{id}DELETE
/api/servers/{id}PATCH
/api/servers/{id}DELETE
/api/services/{id}PATCH
/api/services/{id}DELETE
/api/config-files/{id}DELETE
/api/dependencies/{id}DELETE
/api/settings/spacesPOST
/api/connectionsDELETE
/api/connections/{id}POST
/api/sync/batchDELETE
/api/secrets/{id}PATCH
/api/secrets/{id}DELETE
/api/vars/{id}PATCH
/api/vars/{id}DELETE
/api/registries/{id}PATCH
/api/registries/{id}GET
/api/usersPOST
/api/usersDELETE
/api/users/{id}PATCH
/api/users/{id}DELETE
/api/admin/webhooks/{id}DELETE
/api/databases/{id}PATCH
/api/databases/{id}DELETE
/api/backups/{id}GET
/api/eventsAuthentication
Section titled “Authentication”bearerAuth
Section titled “bearerAuth”BRIDGEPORT supports two bearer token types: short-lived JWTs (Authorization: Bearer <jwt>) issued by POST /api/auth/login, and long-lived API tokens (prefix bport_pat_) minted via POST /api/admin/tokens.
Security scheme type: http