API Reference Overview
The Nava Service API provides endpoints for authentication, transaction handling, approval workflows, and wallet integrations.
Base URL
https://internal.navalabs.dev/api
Authentication Methods
| Method | Header | Description |
|---|---|---|
| JWT (Bearer Token) | Authorization: Bearer <token> | User-facing endpoints, obtained via SIWE |
| API Key | x-api-key: <api-key> | Programmatic access |
| OAuth 2.1 | Authorization: Bearer <access_token> | MCP server access |
Transaction Status
| Status | Description |
|---|---|
PENDING | Transaction is awaiting verification |
APPROVED | Transaction has been approved |
REJECTED | Transaction has been rejected |
EXECUTED | Transaction has been executed on-chain |
FAILED | Transaction execution failed |
Rate Limiting
Rate limit headers are included in responses:
X-RateLimit-Limit: Maximum requests allowedX-RateLimit-Remaining: Remaining requestsX-RateLimit-Reset: Time when the rate limit resets
Transaction Creation Limits (POST /transactions)
| Bucket | Limit | Window |
|---|---|---|
| Per IP address | 100 requests | 60 seconds |
| Per JWT user | 10 requests | 60 seconds |
| Per API key | 30 requests | 60 seconds |
Error Responses
All errors follow a consistent format:
{
"statusCode": 400,
"message": "Error description",
"error": "Bad Request"
}
| Status | Meaning |
|---|---|
400 | Invalid request parameters |
401 | Authentication failed |
403 | Not authorized for this resource |
404 | Resource not found |
429 | Rate limit exceeded |