Three small questions about 'Supplier_Update' method

Extensibility
1

While building an integration to populate [ContactEmail] on existing supplier records, I worked with the Supplier_Update method via the API and came across three things I wanted to ask about:

1. Supplier_Update is not in the current method reference

Supplier API Methods lists Create, Get, Search, and Delete, but no Update. The endpoint works at /1_2/supplier/update - is it meant to be documented alongside the others?

2. The request wrapper is SupplierDetails, not (as expected) SupplierData.

The wrapper differs from the existing Supplier_Create method (which uses SupplierData) and from both of the client method endpoints (which use ClientData). The 400 response from the API names the expected wrapper, so recovery is easy, I was just wondering if that was by design or if it should be tweaked to be consistent with the other methods?

3. The response field SupplierDetailsUpdated returns false on a successful update.

After supplying several real [ContactEmail] changes to records whose existing value was null, the API responds with the message {"SupplierDetailsUpdated": false}

Yet, a follow-up Supplier_Get method confirms the values have actually been successfully written to the records in QuickFile.

Is this a small bug or does the flag mean something other than what it sounds like?

Appreciate your thoughts.

John.

2

Hello John

  1. Yes this appears to be absent from the documentation site, we will get that updated. Here is there direct link >> Supplier_Update API Schema

  2. Supplier_Create also uses SupplierDetails wrapper in the request. Supplier_Create API Schema

  3. We’ll need to look into this for you, I will update this thread once we investigate

For reference, we are currently building a new RESTful API that should be released in the next 4-6 weeks

You may want to consider waiting for this and we can grant you early access.

3

That would be smashing thank you - if there’s anything I can help with in terms of testing etc. please feel free to reach out.

Appreciate your time,

John.