Base URL
Use your deployed host (for example https://stargit.com) and keep API access scoped by
account/workspace permissions.
Developer Documentation
StarGit API & Integration Reference
Build against StarGit with predictable auth, queue-backed Git operations, and StarBridge-connected execution. This page provides the core endpoints and implementation patterns.
Auth0-first with optional native auth
Queue and polling execution model
Multi-server agent orchestration
Authentication
Use bearer tokens for authenticated endpoints. Production deployments should keep token issuance and secret management server-side.
Execution Model
Action requests are enqueued and executed through StarBridge polling. Design clients for async completion and status refresh.
API Reference
Start with the core flows below. Expand each section for request examples and expected behavior.
Register your app or service identity, then use the returned credentials/token in authenticated requests.
curl -X POST https://stargit.com/api/register \
-H "Authorization: Bearer YOUR_TOKEN"StarGit uses OAuth2-style token flows for API access. Exchange your app credentials for an access token:
curl -X POST https://stargit.com/api/authenticate \
-d "client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET"Core endpoints used by typical integrations:
- GET /api/users - Retrieve a list of users.
- POST /api/users - Create a new user.
- GET /api/projects - Get project information.
For self-hosted deployments, replace stargit.com with your own StarGit domain.