We are endeavouring to make use of some of the configuration API endpoints so we can ensure our customer configuration is consistent with the capabilities of our solution.
This endpoint was chosen as a reasonably simple test: we want to force testMode to FALSE programmatically.
Unfortunately, the api documentation just shows yards of JSON and our existing payment integration makes use of XML documents.
We are seeing a 401 returned whenever we PUT to api/v1/configuration/application.
What is different about the configuration endpoints relative to the Auth and Refund type endpoints?
Many thanks
Not answered so "assumed" wrong.
Seems API may have issues with whitespace and PUT ...configuration/*