Base URL
Authentication
Most endpoints require authentication. Include your API key in the request headers:Available Endpoints
The microservice provides the following key endpoints:Health Check
GET /api/test
Check if the microservice is operational
Account Processing
POST /api/process-account/{accountId}
Process a specific account for data collection and synchronization
Implementation Details
The microservice uses a queue-based system to handle resource-intensive tasks. When you call theprocess-account
endpoint, the task is added to one of several load-balanced queues and processed asynchronously to prevent rate limiting and resource exhaustion.
Response Formats
All API responses follow a consistent JSON format:Error Handling
The API uses standard HTTP status codes to indicate the success or failure of requests:200 OK
: The request was successful201 Created
: A resource was successfully created400 Bad Request
: The request was malformed or missing required parameters401 Unauthorized
: Authentication failed or was not provided403 Forbidden
: Authentication succeeded, but the user lacks permission404 Not Found
: The requested resource was not found500 Server Error
: An unexpected error occurred on the server
Rate Limiting
The API implements rate limiting to prevent abuse. You can make up to 100 requests per minute. If you exceed this limit, you will receive a429 Too Many Requests
response.