About JAAulde

JAAulde · ‎12-08-2017

Excellent point, @bolaurent!

JAAulde · ‎12-08-2017

Thanks for the reply, @lukasz! It is difficult for us, especially as Zuora has directed everyone to start using REST as opposed to SOAP, but I certainly understand the size of the job. Your note explaining that SOAP is currently fully covered under the new API system is helpful, and explains a lot!

JAAulde · ‎10-17-2017

In my experience, a solid REST API denotes success/failure via HTTP status code, and the response contains a represnetation of the created/modified object's new state. The Zuora REST API's various endpoints return inconsistent data structures, none of which directly rerpesent the object which was acted upon. Specifically, I'd love to see the CRUD endpoints denote creation/update success via an HTTP status code in the 200 range, remove the `success` property of the response body, and return all current properties of the newly created/updated object. As is, I have to POST data for object creation, then use the ID that was returned to GET an actual representation of the created object. This is, as I said, rather non-standard and a waste of API calls and processing time.

JAAulde · ‎02-13-2017

Great, thank you very much!

JAAulde · ‎02-10-2017

I noticed that the PHP REST API wrapper has misconfigured Composer properties, and the README.md section on Composer installation relfects those as well. Specifically, it seems that some placholders in a Swagger config did not get filled in with proper values, resulting in the package's name being GIT_USER_ID/GIT_REPO_ID. This results in a similarly named folder structure in vendor/ upon installation. I forked the project and committed a patch, then submitted a pull request: https://github.com/zuora/codelibrary-php/pull/1 I recognize that accepting the pull may not be the best fix from your end given the Swagger generation involed, but if some action could be taken I'd appreciate it. An added bonus would be to register the package at https://packagist.org so that the repository addition to local composer.json files wouldn't be necessary. Thanks very much for your consideration! Jim

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Re: REST API Return data not useful

Re: REST API Return data not useful

REST API Return data not useful

Re: PHP REST wrapper has improper composer configuration

PHP REST wrapper has improper composer configuration