This page tracks every update to the wxrks API, so you can see what's new and keep your integration on the latest version.
Each entry says whether it needs a change on your side or is simply there for you to pick up. Check it before you ship, and tell us if you spot an update that isn't listed.
We started tracking the wxrks API surface today, covering 148 documented endpoints across 19 sections along with their parameters, request bodies and response shapes. This entry is the baseline rather than a change. From here on, anything that moves in the API gets an entry on this page.
Wording and structure only. The API itself is unchanged.
No changes in this category.
Your integration needs an update to stay on the current version: an endpoint or field that moved, a parameter that became required, or a change to authentication.
An update that may or may not apply to you: a new field whose requirement isn't settled, a header change, a reorganised endpoint. Worth a look at your integration.
Something new you can pick up: a new endpoint, a new optional parameter, or an extra field in a response. Adopt it when you're ready, or leave your calls as they are.
Wording, examples or structure in the documentation. No change in API behaviour.
We compare the full published API surface at dev.wxrks.com against the previous known state and record what moved. That covers every documented endpoint along with its parameters, request body and response shape. The date on each entry is the date we detected the change.
One caveat worth being straight about: this tracks the API as documented. An update that ships without the documentation changing won't appear here, so if you come across one, tell us. That's a gap we want to know about.