ISSUE IDENTIFIED // Error when calling Event API - 23rd January 2026

Incident Report for Citrus-Lime Service Status

Postmortem

Incident Postmortem: EventAPI Transaction Posting Issue

Date: 23 January 2026
Status: Resolved

Summary

Earlier today, we identified and resolved an issue that affected the EventAPI’s ability to post transactional data to third-party applications that integrate with Citrus-Lime.

Impact

Between 04:30am and 12:18pm (GMT) on 23/01/26, POS transactions were not successfully posting to some external services. This may have affected integrations including:

  • Accounting platforms (e.g. Xero, QuickBooks)
  • Customer rewards systems
  • Marketing platforms (e.g. Mailchimp, Omnisend)
  • Custom webhook integrations configured by individual retailers

During this window, transactions continued to process normally within Citrus-Lime, just not to the external services.

This issue did not impact the standard Cloud POS API or the Batch Data API - only integrations powered by the EventAPI were affected.

Root Cause

The issue was caused by a server configuration problem following an overnight restart, which resulted in the EventAPI being unable to process outbound transactional messages correctly.

Resolution

The configuration issue was identified and corrected, restoring normal service. Once the fix was applied, transaction posting resumed immediately.

Data posting should retry and catch up independently, but if you believe you are missing data in any connected third-party systems during the affected timeframe, please contact our Support team for guidance on next steps.

Posted Jan 23, 2026 - 13:15 GMT

Resolved

This issue has been resolved.
Posted Jan 23, 2026 - 12:39 GMT

Update

Further work has uncovered that this issue is also affecting postings through to MailChimp and Omnisend.
Posted Jan 23, 2026 - 12:20 GMT

Investigating

We have identified an ongoing issue with the Event API which is affecting Webhooks, including the posting of data to Xero and Quickbooks.

Our team are working to resolve this as soon as possible and further updates will be provided in due course.
Posted Jan 23, 2026 - 12:15 GMT
This incident affected: API.