Service Availability & Uptime Commitment

LiteAPI is designed to provide a highly available and reliable service for travel search and booking operations. This page outlines LiteAPI’s service availability objectives, uptime commitment, and operational principles.

Please note: This page is provided for informational purposes and does not constitute a legally binding service level agreement unless explicitly agreed in writing.

Uptime Commitment

LiteAPI commits to maintaining 99.95% monthly service uptime for its production APIs.

Uptime is calculated on a monthly basis and reflects the availability of LiteAPI’s core API services.


Definition of Availability

A service is considered available when:

  • Production API endpoints are reachable
  • Requests receive valid responses (excluding client-side errors)

Availability measurements exclude:

  • Scheduled maintenance windows
  • Customer-side issues (e.g. network failures, invalid requests)
  • Force majeure events outside LiteAPI’s reasonable control

Monitoring and Measurement

LiteAPI continuously monitors API availability and performance using internal monitoring systems.

Availability metrics are:

  • Tracked in real time
  • Reviewed on an ongoing basis
  • Used to trigger alerts and incident response processes

Customers may also monitor availability and performance using the LiteAPI Dashboard, which provides historical and near real-time visibility into API metrics.


Incident Response and Recovery

In the event of a service disruption, LiteAPI follows defined incident response procedures to:

  • Identify and mitigate the issue
  • Restore service as quickly as possible
  • Communicate relevant updates to affected customers when appropriate

LiteAPI prioritizes incidents based on severity and customer impact.


Maintenance and Changes

LiteAPI may perform maintenance activities to improve reliability, security, and performance.

Where feasible:

  • Maintenance is planned to minimize customer impact
  • Customers may be notified in advance of significant changes

Emergency maintenance may be performed when required to protect service integrity or security.


Exclusions

The uptime commitment does not apply to:

  • Sandbox or test environments
  • Beta or experimental features
  • Customer misuse of the APIs
  • Third-party outages outside LiteAPI’s direct control

Transparency and Continuous Improvement

LiteAPI uses availability and incident data to:

  • Improve system resilience
  • Reduce downtime risk
  • Enhance operational processes

Service reliability is treated as an ongoing priority.


Summary

  • Uptime commitment: 99.95% monthly availability
  • Scope: Production LiteAPI APIs
  • Visibility: Real-time and historical metrics via LiteAPI Dashboard