Hi all,
I noticed a change in the interface for calling the web services via the console, compared to when I tested this morning.
I am getting an error but what is more important is, it is not clear how to pass the schema and the values needed for the request body to be sent in text/plain.
The curl command generated was:
curl -X POST --header "Authorization: Bearer THE AUTH BEARER" --header "Content-Type: text/plain" -d "EP1672821" "http://ops.epo.org/3.2/rest-services/pu ... escription"
And I got a response with:
<fault xmlns="http://ops.epo.org">
<code>SERVER.EntityNotFound</code>
<message>No results found</message>
</fault>
I also tried number=EP1672821 using the text field provided for specifying values and the error was more an interpratation / parsing error so the request could not lead to anywhere.
Any thoughts?
Others more lucky with this?
Regards,
Kamon
Changes in querying the services using the API console?
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: Changes in querying the services using the API console?
Hi,
I am not sure what you mean - I see no change ion interface at all (see image below), Or do you mean POST? But that one didn't change either
Regards,
OPS support
I am not sure what you mean - I see no change ion interface at all (see image below), Or do you mean POST? But that one didn't change either
Regards,
OPS support
Re: Changes in querying the services using the API console?
Sorry, I get it now.
I had just confused both entries from the main page. It's the GET one I was looking for.
-- Kamon
I had just confused both entries from the main page. It's the GET one I was looking for.
-- Kamon