Overview
System endpoints provide monitoring and diagnostic capabilities for your Partner API integration. Use these to check API health, review usage logs, and track rate limit consumption.Health Check
Verify that the API is operational and responding correctly.Endpoint
Headers
Your API authentication token
Request Example
Response
Overall API health status:
healthy, degraded, or downCurrent API version
ISO 8601 timestamp of health check
Status of individual service components
API Information
Get details about the API version, your integration, and available features.Endpoint
Headers
Your API authentication token
Request Example
Response
Current API version
Your integration details (externalId, permissions, accountType)
List of enabled features for your account
Base URLs for different API resources
Use this endpoint to:
- Verify your integration configuration
- Check which features are enabled for your account
- Confirm API version before making calls
- Display integration status in your admin dashboard
Usage Logs
Retrieve logs of your API requests including requests, responses, and errors.Endpoint
Headers
Your API authentication token
Query Parameters
Page number for pagination
Number of logs per page (max 200)
Filter logs from this date (ISO 8601)
Filter logs until this date (ISO 8601)
Filter by specific endpoint (e.g., “/api/audio”)
Filter by HTTP status code or range (e.g., “200”, “4xx”, “5xx”)
Filter by HTTP method (GET, POST, DELETE)
Request Example
Response
Array of log entries
Pagination metadata
Log Retention: Logs are retained for 30 days. Export logs regularly if you need longer retention.Common Uses:
- Debugging integration issues
- Auditing API usage
- Monitoring performance
- Compliance and security reviews
Rate Limits
Check your current rate limit consumption and remaining quota.Endpoint
Headers
Your API authentication token
Request Example
Response
Rate limit configuration for your account
Current usage statistics
Timestamps when limits reset
Rate Limit Headers
All API responses include rate limit information in headers:X-RateLimit-Limit
X-RateLimit-Limit
Maximum requests allowed in the current time window (per minute).
X-RateLimit-Remaining
X-RateLimit-Remaining
Number of requests remaining in the current time window.
X-RateLimit-Reset
X-RateLimit-Reset
Unix timestamp when the rate limit resets.
Monitoring Best Practices
Set Up Alerts
Monitor for:
- Consecutive 5xx errors
- Rate limit warnings (>80% usage)
- Slow response times (>2s)
- Degraded health status
Log Regularly
Review logs weekly for:
- Unusual traffic patterns
- Failed requests (4xx, 5xx)
- High response times
- IP address changes
Track Performance
Monitor metrics:
- Average response time
- Request success rate (%)
- Rate limit consumption
- Error distribution
Health Checks
Implement monitoring:
- Poll
/healthevery 60s - Alert on 2+ consecutive failures
- Track uptime SLA (>99.9%)
- Monitor service components
Example: Complete Monitoring Setup
Troubleshooting
High Error Rates
High Error Rates
Symptoms: Seeing many 4xx or 5xx errors in logsCommon causes:
- Invalid request format (400)
- Authentication issues (401)
- Rate limits exceeded (429)
- Server issues (5xx)
- Review logs:
GET /api/integration/logs?status=4xx - Check token validity:
POST /api/integration/test - Monitor rate limits:
GET /api/integration/limits - Implement retry logic with exponential backoff
Slow Response Times
Slow Response Times
Symptoms: Response times >2 seconds consistentlyCommon causes:
- Large file uploads
- Network latency
- Server load during peak hours
- Inefficient request patterns
- Check logs for
responseTimefield - Optimize file sizes (compress audio before upload)
- Use batch operations when possible
- Cache frequently accessed data
Degraded Health Status
Degraded Health Status
Symptoms: Health check returns
degraded or downActions:- Check service component status in health response
- Review recent logs for errors
- Reduce request rate temporarily
- Contact support if issue persists >5 minutes

