FMS API SLAs are structured to accommodate iterative updates and feature releases.
Uptime
Our target uptime during beta is 95%, with possible maintenance windows that may impact availability. Notifications will be sent in advance for any planned maintenance.
Due to the nature of beta testing, response times may vary. Expected average response time is under 1 second, but performance may fluctuate with API traffic and active developments.
Our support team will respond to any reported issues or questions within 48 hours during standard business hours (9 AM - 5 PM EST). For urgent issues affecting API availability or severe functionality bugs, responses are prioritized.
Beta APIs are subject to rate limits. Default limits are set at 100 requests per minute per API key. If additional capacity is needed, please contact us to discuss.
Data consistency and replication may not yet be fully optimized. In rare cases, slight data lags may occur. During beta, we are actively tuning the system for better data accuracy and timeliness.
Standardized error codes are provided in API responses (e.g., 401 Unauthorized, 404 Not Found, 429 Too Many Requests). Refer to Error Handling documentation to interpret and troubleshoot any encountered errors.
These SLAs apply to APIs in production status.
99% with possible maintenance windows that may impact availability. Notifications will be sent in advance for any planned maintenance.
Expected average response time is under 1 second, but performance may fluctuate with API traffic or requests for larger than average payloads.
Our support team will respond to any reported issues or questions within 48 hours during standard business hours (9 AM - 5 PM EST). For urgent issues affecting API availability or severe functionality bugs, responses are prioritized.
Production APIs are subject to rate limits. Default limits are set at 100 requests per minute per API key. If additional capacity is needed, please contact us to discuss.
Standardized error codes are provided in API responses (e.g., 401 Unauthorized, 404 Not Found, 429 Too Many Requests). Refer to our error code documentation to interpret and troubleshoot any encountered errors.