Hi all, it's a bit confusing reading about success after changing the headers or changing the API. This I found out: - POST doesn't work - GET needs the API version 3.1 only for some functions and then depending on the the parameters, e.g: OK: https://ops.epo.org/3.1/rest-services/published-data/pub...

Sorry, search is not ok:

https://ops.epo.org/3.2/rest-services/p ... 2016000576

OK is:
https://ops.epo.org//rest-services/publ ... 2016000576

Hi, thanks for your advice. The get-method was ok for search. For images however I get e.g.: 1 Mi 8. Nov 11:30:00 CET 2017 UA: https://ops.epo.org/3.2/rest-services/published-data/publication/docdb/WO2017187334.A1/images 1 Mi 8. Nov 11:30:00 CET 2017 UA-method get 0 Mi 8. Nov 11:30:00 CET 2017 error...

Hi, please have a look on my log today: 1 Di 7. Nov 15:05:27 CET 2017 UA: https://ops.epo.org/3.2/rest-services/published-data/search/biblio,full-cycle applicant=IBM 1 Di 7. Nov 15:05:27 CET 2017 UA-method post 1 Di 7. Nov 15:05:27 CET 2017 UA-status: 500 Internal Server Error 0 Di 7. Nov 15:05:27 C...

In the afternoon I got '_msg' => 'Internal Server Error' on https://ops.epo.org/3.2/rest-services/published-data/search/biblio,full-cycle ( q=applicant%3DIBM ) This however worked: https://ops.epo.org/rest-services/published-data/search/biblio,full-cycle and also this: https://ops.epo.org/3.2/rest-s...

Thanks for your reply.
I understand, what OPS is doing.
In terms of searching for new documents per CQL, it doesn't seem to be possible to search
for changes in B documents

Hi Support, > CQL should be used for date ranges, names, titles, classifications Exactly this is what I did (not knowing the pubnumbers) and where I found, that a document that should be part of the result just isn't there. It doesn't matter, with which terms I came to the original result. The resul...

Based on a more complex query, US9780384B2 was one of the results to watch for changes. The same query with a newer pd doesn't deliver the most recent document. If I search for pn=US9780384B2 I get the results US2015349348A1 and US9780384B2 For US9780384B2, today I see a publicationdate of 20171003,...

Hello, the problem with the bad characters is not a problem of the interface. It seems to be inserted on epodoc/docdb generation for e.g. inventor- or applicant data. It combines country within the used field. Have a look on xml-transformation, ( in Perl) : $data->[0]->{'bibliographic-data'}->[0]->{...

Hello Support, with ti=Anhängekupplung I don't get any result. Also in the API-console I get "Not found" In the API Reference Guide once "ti" is mentioned as an index for the publication title in English (p. 132), page 134 however, says the ti index checks title in all languages....