Zaptec
All Systems Operational

About This Site

This is Zaptec's status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here.

As always, if you are experiencing any issues with Zaptec, don't hesitate to get in touch with us and we'll get back to you as soon as we can.

Uptime over the past 90 days. View historical uptime.
Zaptec Cloud Services Operational
90 days ago
100.0 % uptime
Today
Portal ? Operational
90 days ago
100.0 % uptime
Today
API ? Operational
90 days ago
100.0 % uptime
Today
Charger backend ? Operational
90 days ago
100.0 % uptime
Today
OCPP Operational
90 days ago
100.0 % uptime
Today
Websites ? Operational
90 days ago
100.0 % uptime
Today
Cellular connection ? Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
99.95 % uptime
Today
Portal ? Operational
90 days ago
99.98 % uptime
Today
Charge authorization ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
Mar 15, 2025

No incidents reported today.

Mar 14, 2025

No incidents reported.

Mar 13, 2025

No incidents reported.

Mar 12, 2025

No incidents reported.

Mar 11, 2025

No incidents reported.

Mar 10, 2025

No incidents reported.

Mar 9, 2025

No incidents reported.

Mar 8, 2025

No incidents reported.

Mar 7, 2025

No incidents reported.

Mar 6, 2025

No incidents reported.

Mar 5, 2025

No incidents reported.

Mar 4, 2025

No incidents reported.

Mar 3, 2025
WebAPI / Zaptec Portal
Postmortem - Read details
Mar 7, 09:53 CET
Resolved - This incident has been resolved.
Mar 3, 16:12 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 3, 14:44 CET
Update - We are continuing to investigate this issue.
Mar 3, 11:57 CET
Investigating - We are currently investigating this issue.
Mar 3, 10:54 CET
Mar 2, 2025

No incidents reported.

Mar 1, 2025
Important API Update
Completed - The scheduled maintenance has been completed.
Mar 1, 01:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 1, 00:00 CET
Scheduled - Dear Partners,

We want to inform you about some upcoming improvements to the Zaptec API that will enhance efficiency, performance, and reliability. These updates will take effect from 01-03-2025, and we want to ensure you have all the details needed for a smooth transition.

What’s changing?

1.
More accurate Error Handling for Charger State Requests
Endpoint Affected: GET /api/charger/{id}/state

What’s Changing?
- If the requested charger ID does not exist, the API will now return a 404 Not Found instead of 200 OK with an empty list.
- New 404 Response Format:
{
"errorCode": 512,
"details": "charger not found"
}

Why This Change?
This aligns with best practices for API responses, making it clearer when a charger ID is invalid.
It helps integrators handle errors correctly and reduces unnecessary retries.

What You Need to Do:
Please ensure your integration can handle 404 Not Found responses appropriately.
Avoid automatically retrying requests when this status is received.

2.
Updated Pagination Limits for Better Performance
Endpoints Affected:
GET /api/installation
GET /api/charger
GET /api/chargeHistory

What’s Changing?
Maximum page size reduced: 5000 → 100
Default page size reduced: 500 → 50

Why This Change?
Prevents excessive database load, improving response times.
Ensures a more stable and efficient experience for all API users.

What You Need to Do:
If your integration currently requests more than 100 records per page, please update it to respect the new limits.
If no changes are made, responses will automatically be limited to 100 records per page.

3.
Charge History Data Now Limited to the Last 365 Days
Endpoint Affected: /api/chargeHistory

What’s Changing?
You will only be able to query charge history data for the last 365 days.

Why This Change?
Helps optimize database performance by archiving older data.
Ensures faster query response times.

What You Need to Do:
If your integration queries charge history beyond 365 days, please adjust the date range accordingly.


Next Steps & Support
Effective Date: 01-03-2025
Final Rollout: 01-04-2025
We understand that changes like these may require some adjustments, and we’re here to support you through the transition. If you have any questions or need assistance, feel free to reach out to us!

We truly appreciate your collaboration in making these improvements possible. Thanks for being a valued partner!
Feb 17, 12:42 CET
← Incident History Powered by Atlassian Statuspage