Connect
Connect to your Apso-generated APIs and databases. This section is for frontend developers, backend developers, and AI assistants that need to verify a generated service behaves correctly outside the codebase.
Use these pages after generation succeeds and before you build product features on top of the API.
Request lifecycleOne request, with every backend boundary visible.
Authenticated- 01ClientServer component, mobile app, or service
- 02SDK or RESTTyped operation and validated payload
- 03IdentitySession, JWT, or API key context
- 04Tenant scopeAuthorization and row boundary
- 05ServiceGenerated route, product logic, and database
Effective connection workflow
- Start the generated service locally.
- Confirm
/healthresponds. - Create one record with curl or Swagger.
- Read it back through the generated list endpoint.
- Add authentication and tenant headers only after the unauthenticated path works.
- Move the same request shape into your frontend or SDK client.
API connection
Your Apso-generated backend exposes a REST API with the following structure:
https://your-api.example.com
├── /auth # Authentication endpoints
├── /users # User management
├── /{entity} # Entity CRUD endpoints
└── /health # Health checkGetting started
Configure your PostgreSQL connection
Database setupUse Swagger UI, curl, and API clients
Test the APIDiagnose and fix connection issues
TroubleshootingAuthentication methods
Apso supports multiple authentication methods:
| Method | Use case | Header |
|---|---|---|
| JWT Bearer | User sessions | Authorization: Bearer <token> |
| API Key | Service-to-service | X-API-Key: <key> |
| Session Cookie | Web applications | Cookie-based auth |
Request format
For authenticated JSON requests, include these headers:
# Required headers
Content-Type: application/json
Authorization: Bearer <your-token>
# Multi-tenancy header (if enabled)
X-Organization-Id: <org-id>Response format
Successful responses:
{
"data": { /* entity or array */ },
"meta": {
"total": 100,
"page": 1,
"limit": 20
}
}Error responses:
{
"statusCode": 400,
"message": "Validation failed",
"errors": [
{ "field": "email", "message": "Invalid email format" }
]
}Last updated on