NIS2Europe API — SLA & Versioning Policy

Service Level Agreement (SLA)

This SLA applies to the NIS2Europe Compliance API (api.nis2europe.eu), operated by AIPOS OÜ (reg. 16966532).

Effective date: 2026-07-22

Important: The 99.9 % uptime commitment is effective once the redundant infrastructure (primary + failover server) is fully deployed. Until then, we publish our actual uptime on the Status page transparently and do not apply SLA credit claims for the pre-redundancy period.

Uptime Targets

Tier	Monthly Uptime	Max Downtime / Month
Professional (3 900 EUR/mo)	99.5 %	~3.6 hours
Enterprise (9 900 EUR/mo)	99.9 %	~43 minutes

Uptime is defined as the percentage of minutes in a calendar month during which the GET /v1/health endpoint returns HTTP 200 when polled from our monitoring system.

Scheduled maintenance (announced ≥ 24 hours in advance via email + status page) is excluded from downtime calculations.

SLA Credit Calculation

If the uptime guarantee is missed in a given calendar month, you are entitled to a service credit applied to your next invoice:

Actual Uptime	Credit (% of monthly fee)
99.0 % – < SLA target	10 %
95.0 % – < 99.0 %	25 %
< 95.0 %	50 %

Credits are calculated automatically from the uptime data on the public status page and applied to the following month's invoice. To claim a credit, contact info@nis2europe.eu within 14 days of the end of the affected month. Credits do not apply to Baas (free) tier or sandbox usage.

Exclusions

Force majeure events (natural disasters, acts of war, widespread Internet outages)
Scheduled maintenance windows (notified ≥ 24h in advance)
Issues caused by client-side errors, invalid API keys, or rate limit exhaustion
Outages caused by third-party services outside AIPOS OÜ control (Revolut, DNS, CDN)

Versioning Policy

Current stable version: v1

The current API is versioned at /v1/. All endpoints under /v1/ are considered stable and follow the guarantees below.

Stability Guarantee

No breaking changes to existing /v1/ endpoints without a deprecation notice.
Additive changes (new optional fields in responses, new endpoints) may be deployed at any time without notice.
Deprecation notice: Any breaking change to an existing endpoint is announced ≥ 90 days in advance via email to all active API clients + entry in KB Changelog.
The deprecated endpoint continues to function for the full 90-day deprecation window.

What counts as a breaking change

Removing a field from a response that was previously present
Changing the type of an existing field
Removing an endpoint
Changing the meaning of a required request parameter

What is NOT a breaking change

Adding new optional request fields
Adding new response fields
Adding new endpoints
Changing error messages (the code field is stable; the message field is informational)
Updating KB content (legal sources, translations) — these are logged in /v1/changelog

Version lifecycle

Phase	Duration	Action
Stable	Until next major version	Full support, SLA applies
Deprecated	≥ 90 days	Works but sunset date announced
End-of-life	—	Endpoint returns 410 Gone

Rollout of /v2 (future)

When a future /v2 is introduced, /v1 will continue to operate in parallel for at least 12 months. The exact sunset date will be communicated ≥ 180 days in advance.

Changelog & notifications

All API changes (breaking and non-breaking), KB knowledge base updates, and SLA incidents are logged at:

GET /v1/changelog — machine-readable KB version history
Status page — live and historical incident log
Email: API clients receive email notifications for deprecation notices and scheduled maintenance

Support

Response times

Tier	P1 Critical	P2 High	P3 Normal
Professional	4 business hours	1 business day	3 business days
Enterprise	1 hour	4 business hours	1 business day

Support contact: info@nis2europe.eu

P1 = API completely unavailable; P2 = significant degradation or data quality issue; P3 = questions, feature requests.