Skip to main content

Changelog

Who this is for: everyone integrating Zamplia. When to use it: before upgrading or when you notice new behavior. What happens next: you'll know what changed and whether action is needed.

We version our APIs and ship backward-compatible changes whenever possible. Additive changes (new endpoints, new optional fields, new enum values) can land without notice; breaking changes are announced in advance and accompanied by a Migration Guide.

What counts as backward-compatible​

  • Adding a new endpoint or optional request field.
  • Adding a new field to a response.
  • Adding a new value to an existing enum.

Build clients that ignore unknown response fields so additive changes never break you.

What counts as breaking​

  • Removing or renaming an endpoint, field, or enum value.
  • Changing the type or meaning of an existing field.
  • Changing authentication requirements.

These are communicated ahead of time with a migration path.

Releases​

Documentation Platform — current​

  • Rebuilt the developer portal: clearer Demand vs Supply paths, Getting Started, lifecycle guides, and an enterprise design system.
  • No API contracts changed — all endpoints, fields, payloads, enums, auth methods, and SDK signatures are unchanged.

Demand API v2 / Supply API v2​

  • Stable. See the Demand API and Supply API references for current operations.
  • Demand API reference is now spec-generated and grouped into Projects, Qualifications, Quotas, Group Security, Reconciliation, and Reference Data (previously a single undifferentiated group). Documentation/taxonomy only — no endpoints, schemas, hosts, enums, payloads, or auth changed. See the Migration Notes.

Subscribe to updates via Support.