Zuora API
newAccount body parameter removal on PUT /v1/orders/{id}
Deprecated, no dateSubscribe to Zuora APIShare
Zuora API deprecated the newAccount body parameter on PUT /v1/orders/{id} on March 15, 2024, without a shutdown date. Calls that continue to pass the parameter will fail. The change applies directly to the request body of the update order operation.
Calls it hits
PUT /v1/orders/{id}body parameter newAccount
What to use instead of these calls
Create the account first using POST /v1/accounts and reference it with existingAccountNumber when updating the order.
In Zuora API's words
In the request body of the "Update an order" operation, deprecated the newAccount field.
Facts
- API
- Zuora API
rest.zuora.com - Kind
- Parameter removal
- Announced
- March 15, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Zuora API's own pages
Questions
When does this change take effect?
Zuora API deprecated PUT /v1/orders/{id}, body parameter newAccount without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Zuora API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Zuora API 4
-
No date
/v1/object/credit-balance-adjustment*Removal Deprecated, no date -
No date
/v1/object/invoice-adjustment*Removal Deprecated, no date -
No date
/v1/object/invoice-item-adjustment*Removal Deprecated, no date -
No date
POST /v1/batch-queryParameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.