Update packages
The same endpoint as Create packages. Include a package's
id on an entry and that package is updated rather than created, so one call
can mix new and changed packages. An id that does not exist is created as a
new package rather than rejected.
Send every field on each entry you update, not only the ones that changed: the entry replaces the package.
Changing the default package. Any entry can take over as the default by
setting is_default: true, and the old default is cleared. But if the current
default is in the body and no entry sets is_default: true, the call fails
with a 500 and Cannot unset default package., even when all you changed
was its name.
Send is_default: true whenever you update the default package.
The fields are the same as on Create packages, plus:
| Field | Type | Required | Notes |
|---|---|---|---|
packages[].id |
integer | yes | The package to update. |
The response is the same bare array as on create, holding only the packages you sent.