APIAgent-ready
Nine endpoints in the API reference now match the service
Nine endpoints in the published reference described calls that the service does not answer. The reference now names the right method and request body, and the endpoints that were never built have been withdrawn.
Reading the published reference and calling what it described could produce a 404 on an endpoint that was never built, or a rejection on a method the service does not accept. Nine operations were affected, and each has been resolved against the behaviour that actually ships.
- Updating a customer, an invoice or a dispute is a partial update and is documented as one. Send only the fields you want to change, rather than a complete replacement object
- Adding a line to an order is documented as the single-line append it has always been, instead of a bulk replace that was never implemented
- Request schemas now list exactly the fields each endpoint reads, along with the limits it expects, so a reference-valid body is an accepted body
- Order line amounts are documented as the decimal strings the API returns, not as numbers
- Updating or deleting a customer by external id, and the contacts endpoints, have been withdrawn from the reference. They were listed but never built, and calling them could only fail