📢 Important Update for Digit API Users! 📢
Heads up, technical folks! We've made some changes to our API to improve clarity and consistency for how we handle serialized vs. non-serialized items. We know API updates can be a headache, so we're keeping this brief and to the point.
What's Changing?
We've renamed several inventory-related mutations to explicitly include "Serialized" in their names. This is to better reflect their function and distinguish them from future mutations that will handle non-serialized items.
The functionality of these mutations remains exactly the same. They simply have a new name.
Old Mutation Name | New Mutation Name |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Additionally, we are standardizing the structure of our error responses to provide a more consistent and predictable experience for developers.
Before:
JSON
{ "code": "CONFLICT", "message": "There was a conflict with the current state of the resource.", "details": { "message": "Oops! Someone else was using that resource. Please try again." } }Now:
JSON
{ "message": "There was a conflict with the current state of the resource.", "extensions": { "code": "CONFLICT", "details": { "message": "Oops! Someone else was using that resource. Please try again." } } }
What do you need to do?
If your integrations use any of the old mutation names listed above, you'll need to update your code to use the new names. This is a simple find-and-replace, but it's a critical step to ensure your integrations continue to function correctly.
If you are parsing our error responses, you may need to adjust your code to account for the new structure, where the code and details fields are nested under extensions.
We recommend making this change as soon as possible to avoid any disruption. For any questions please don't hesitate to reach out to [email protected].