As you know from our previous communication, we have been experiencing recurrent difficulties with our API testing Console https://developers.epo.org/ due to abusive behaviour of certain users. This behaviour was causing frequent unavailability of the testing feature of the Developer’s portal forcing us to come up with an alternative solution. In the last few weeks we have been working hard to develop and deploy a new, more secure model for users who want to test OPS service.
The new API Console will be put into production on Thursday, 31 August 2017 and will at the same time completely replace the old testing model.
With the introduction of this new model there will be some changes in design and in the way OPS testing can be performed in the future:
- Only registered users can test OPS from now on (they need to register to OPS first and after registration is accepted they can add their own real or test App into their account and test OPS by using their own authentication token)
- The new console only offers testing of OPS version 3.2
- With the introduction of this new testing model on https://developers.epo.org/, an anonymous use of OPS services is now completely discontinued
Please note that the EPO does not assume any responsibility for any malfunction of the testing feature of the API Console. There may be a brief period of time while the developer portal is unavailable while we conclude the conversion.
Please see short instructions on how to test new Develope's Area testing console: http://documents.epo.org/projects/babyl ... OPS_en.pdf
If you have questions, please contact us at email@example.com .