FinFeedAPI provides a 99.9% monthly availability target for paid plans, supported by service monitoring and defined SLA terms for production services.
For organizations with more demanding operational requirements, Enterprise agreements can include customized commitments around availability, latency, incident response, support, and infrastructure.
The FinFeedAPI SLA defines service availability and operational commitments for customers using the platform in production. The standard SLA is available across paid plans.
Availability is calculated monthly as Monthly Uptime Percentage, with FinFeedAPI using commercially reasonable efforts to make covered Services available 99.9% of the time.
Availability is measured using third-party performance and monitoring services. Unavailable Time occurs when the FinFeedAPI API is unavailable for use according to the applicable monitoring service.
The SLA applies to the availability of FinFeedAPI Services within the agreed service scope. This provides organizations running financial applications, analytics systems, research platforms, and data pipelines with defined operational expectations for FinFeedAPI services.
If Monthly Uptime Percentage falls below the SLA target, eligible customers may receive a service credit according to the applicable SLA terms. Service credits are applied according to the SLA terms and cannot be redeemed for cash.
| Monthly Uptime Percentage | Service Credit |
|---|---|
| ≥ 99.9% | 0% |
| = 99.0% | 5% |
| < 99.0% | 10% |
FinFeedAPI operates the infrastructure used to process and deliver financial data, but many datasets originate from independent exchanges and other third-party sources. The SLA therefore covers FinFeedAPI Services within the agreed scope, rather than the availability or accuracy of external data sources. This distinction allows service availability to be measured against infrastructure and services within FinFeedAPI control.
An available API does not always mean that every external data source is continuously publishing data. This is particularly important for financial data workflows that depend on exchanges, regulatory sources, prediction market venues, and other independent data providers.
If gaps caused by a third-party source are identified, historical data may be backfilled where technically possible.
However, the completeness and continuity of data originating from third parties are not covered by the SLA.
Organizations with stricter operational requirements can define additional service commitments through a customized Enterprise SLA. Enterprise SLA terms are defined according to the technical scope, infrastructure requirements, and operational needs of each deployment.
FinFeedAPI continuously monitors its production services and provides operational visibility through the public status page. Combined with third-party SLA monitoring, this gives teams greater visibility into service performance and operational events.
Yes. A standard SLA is available for paid plans, with a 99.9% monthly availability target. Customized SLA terms are also available for Enterprise customers.
Availability is measured monthly as Monthly Uptime Percentage using third-party performance and monitoring services.
Eligible customers may receive a service credit based on the Monthly Uptime Percentage and applicable SLA terms.
No. Availability or data issues caused by independent exchanges and other third-party sources are outside the SLA. Historical gaps may be backfilled where technically possible.
Yes. Enterprise agreements can include customized commitments for areas such as availability, latency, incident response, resolution timelines, support, and infrastructure.
Different financial data workloads have different requirements for availability, response times, support, and infrastructure.
FinFeedAPI Enterprise can provide customized SLA terms designed around your production environment and operational requirements.
