API does not respond when trying to create purchase orders with incorrect account id about xero-openapi HOT 1 CLOSED

@can3p - Thanks for the feedback.

I've tested this with our Java and PHP SDKs. The Java SDK catches the invalid string before posting to the API, but the PHP does throw 500 error when you use a ContactId = "BROKEN".

I'm not sure this is a valid test case. I tried a second time with our PHP SDK and used a properly formatted, but invalid GUID ContactId= "00000000-0000-0000-0000-000000000000" and received a 200 response with a validation error for the Purchase Order.

Nonetheless, I'll be sharing this bug with our API team so they can prioritize fixing it. This isn't an issue with the OpenAPI spec per se but with the API. Client SDKs we generate from these spec only support JSON as we felt supporting serialization for both JSON and XML was not necessary and between the two JSON is the preferred req/resp format.

While the API supports both an Object OR an Array of Objects when creating a Purchase Order, OpenAPI specs only allow for a single path/verb combination. For this reason, we've chosen to include the plural create as you can create a single or plural objects using this method.

from xero-openapi.