API Documentation
The Fegura API enables you to programmatically scan AWS accounts, generate architecture diagrams, and integrate with your CI/CD pipelines. This RESTful API uses standard HTTP methods and returns JSON responses.
Base URL
All API requests should be made to:
https://api.fegura.aiQuick Start
To get started, you'll need an API key. You can create one from your API Keys settings page.
Here's a quick example to list your connected AWS accounts:
curl https://api.fegura.ai/api/accounts \
-H "Authorization: Bearer feg_live_your_api_key" \
-H "Fegura-Version: 2026-02-01"Response
{
"success": true,
"data": {
"accounts": [
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"alias": "Production",
"awsAccountId": "123456789012",
"status": "connected",
"createdAt": "2026-01-15T10:30:00.000Z",
"updatedAt": "2026-01-15T10:30:00.000Z"
}
],
"meta": {
"hasMore": false
}
}
}Key Concepts
Authentication
Learn about API keys, scopes, and securing your requests.
Versioning
Understand our date-based versioning system.
Errors
Error codes, response formats, and handling failures.
Webhooks
Receive real-time notifications for scan and diagram events.
Endpoints
- Accounts - Manage connected AWS accounts
- Scans - Trigger and monitor infrastructure scans
- Diagrams - Retrieve generated architecture diagrams
Response Format
All API responses follow a consistent JSON structure:
// Success response
{
"success": true,
"data": { ... }
}
// Error response
{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Account not found"
}
}Rate Limits
Rate limiting is not currently enforced. We reserve the right to introduce rate limits in the future — when we do, we'll communicate the limits in advance and add standard rate limit headers to responses.