Vlad,
Thank you , that makes sense, and seems so obvious now you have said
it! Switch from positional to named parameters. Works perfectly.
Kind regards,
Adrian Fretwell
Sibthorpe
Nottinghamshire
UK.
On 08/07/2020 15:28, Vlad Patrascu wrote:
Hi Adrian,
In the cases (like
Hi Adrian,
In the cases (like 'pua_publish') where there are multiple optional
parameters that cannot be simply identified by position in the array,
the 'params' member in the JSON-RPC request should be an Object with
named parameters.
As such, you should have:
"params": {
Hello,
What is the correct way to specify empty parameters in an MI call using
JSON?
For example this call to pua_publish has two unused parameters; ETag and
extra_headers, in the old way they were represented by a dot, but if I
try that now I get an invalid etag message:
Pua_publish:
