Opting-out via API recommended practices The UPC would like to communicate API opt-out’s best practices recommandation. We would like to invite the users lodging opt-out via API to follow the below best practices. 1. Introduce massive opt-outs requests, if possible, between 11pm and 8am CET. Indeed, the CMS is less used during the night allowing users to schedule their request and spread usage, consumption of the CMS on 24 hrs.2. Limit as much as possible requests to the CMS to the essential ones and, therefore, introduce some delays between requests to ensure the CMS as enough time to process them. The following process is an example proposal to illustrate the idea: a. Post request of opt-out (waiting time between two consecutives posts >1sec – depending on number of opt-out to introduce over a period of time), i. The first feedback received via API by the requester is a valid proof of opt-out for the UPC. Please find below an example of the message received when your request has been properly accepted by the CMS :1 { 2 “message”:” Subject only to a check that your application has been signed electronically, your application has been accepted by the Registry and pursuant to Rule 5.12 will be treated as entered on the register on the date the Court enters into force”, 3 “requestID”: “DSDF2474GE122”, 4 “receptionTime” : “2023-01-30 14:15:21” 5 } b. At +1 min after the request of opt-out has been sent, the status of the opt-out can be checked via the GetRequestStatus API call, c. At +24 hours after the request of opt-out has been sent the receipt can be downloaded via API call,