EYalla/Developers Contact us

API + Webhook Changelog

Format: newest entries first. Breaking changes are tagged ⚠️. Deprecations get a removal date.


2026-08-25 — ⚠️ A suspended store now returns 423, not 503

If you call the API for a store whose account is suspended, cancelled or expired, you now get 423 Locked instead of 503.

Why this matters to your integration. 503 means the service is unavailable, and almost every HTTP client treats that as "retry shortly" — so a suspended store was retried indefinitely, and the failure looked like an outage on our side rather than a billing problem the merchant can fix. 423 says the account is locked: the answer will not change until someone acts on it.

{ "error": "Tenant unavailable.", "status": "suspended", "reason": "Non-payment" }

What to change: stop retrying on 423 and surface reason to whoever operates the integration. 503 still means what it always did and is still worth retrying — a store that is merely mid-setup returns it, and that one does resolve on its own.

2026-08-20 — Merchant API v1 is live

The Merchant API is out of dark launch, available on the Elite plan:

  • Reads: GET /v1/orders, GET /v1/orders/{number}, GET /v1/products, GET /v1/products/{id}, GET /v1/customers, GET /v1/customers/{id}.
  • Writes: PATCH /v1/orders/{number}/fulfilment (fires the same events as the admin panel) and POST/PATCH /v1/products.
  • Per-key scopes, 60 req/min rate limit, per-request audit log, keys hashed at rest.
  • Base URL: https://api.eyalla.net/v1.

2026-05-15 — v0.4 series

Initial public scaffold of the developer documentation site. The platform itself has been shipping since 2026-05; this site lags as integration surfaces stabilize.

Active webhook events:

  • order.created, order.paid, order.payment_failed, order.refunded
  • order.status_changed (NEW — covers confirmed / processing / shipped / delivered / cancelled transitions)
  • tenant.created, tenant.suspended
  • subscription.cancelled

API: not yet public. Sandbox tenants get a token but endpoints are tagged "alpha — subject to change". Watch this page for the v0.5 release where REST stabilizes.


Earlier

Pre-public preview. Not documented externally — internal-only.


Subscribing to changes

  • This page itself: RSS feed at /developers/api-changelog/feed.xml. Point any feed reader at it — every dated entry below is an item, newest first. Your reader will also find it automatically from this page.
  • Major-version announcements via email to your developer-account contact.
  • Critical breaking changes also surface as a banner inside the tenant Filament admin so store owners can pressure their integrators to update.