RRPproxy Homepage
RRPproxy Homepage


API commands

Please find in the following a set of the most commonly used standard API commands in order to register, modify, renew, and transfer a domain name.

Domain Registration

(API Command reference » AddDomain)
command         = AddDomain
domain          = yourdomain.tickets
period          = (INT)
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0	= (NAMESERVER)
nameserver1 	= (NAMESERVER)

Domain Modification

(API Command reference » ModifyDomain)
command = ModifyDomain
domain  = yourdomain.tickets

Domain Renewal

(API Command reference » RenewDomain)
command    = RenewDomain
domain     = yourdomain.tickets
period     = (INT)
expiration = (INT)

Domain Deletion

(API Command reference » DeleteDomain)
COMMAND = DeleteDomain
DOMAIN = yourdomain.tickets

Domain Transfer

(API Command reference » TransferDomain)
command = TransferDomain
domain = yourdomain.tickets
action = REQUEST
auth = (TEXT)

Transfer procedure

  • After the transfer has been requested, our backend system sends a confirmation email to the Owner/Admin-C according to the WHOIS of the respective domain. In order to initiate the transfer successfully it is important, that this email is confirmed.
  • After confirmation the transfer is initiated through the official registry and the losing registrar will receive the transfer request.
  • The losing registrar will also send an email to the Owner/Admin-C. allowing him/her to deny the transfer. If you do not respond to the email of the losing registrar, then the transfer will get processed successfully after 5 days.

If the Email-Address in the WHOIS is invalid, then the transfer cannot be processed.If this is the case, then kindly contact your current registrar and ask him to update the WHOIS information accordingly.

Transfer notes

  • A .tickets domain transfer must be initiated with a so-called authorisation code, which can be obtained from the current registrar through the owner or Admin-C of the domain.
  • Ensure that your respective domain does not have a lock-status (REGISTRAR-LOCK or HOLD). This can be seen in the WHOIS.
  • If the domain is locked, then the owner can demand that the domain will be unlocked.
  • Please note that we are only allowed to initiate a gTLD transfer after confirmation of the "ICANN Form of Authorization" by the current registrant. The policies can be viewed under http://www.icann.org/transfers/
  • After a successful transfer of the domain, it will be transfer locked from the registry for a period of 60 days.


The format for auth info requires a minimum length of 8 characters and a maximum length of 32 characters.

Additionally, auth info must contain at least one of each of the following three character types:

  • Alphabetic character:a-z;
  • A-Z Numeric character : 0-9
  • Special characters: !;<=$%?&@[()]*^+-,'-{.|/}:~

Domain Restore

(API Command reference » RestoreDomain)
command = RestoreDomain
domain  = yourdomain.tickets

Domain Restrictions

  1. Standard Track Processing
    1. All Applications for .tickets names will be processed according to Standard Track Processing unless Fast Track Processing is requested by the Applicant to the Registry within five (5) Business Days of the Applicant being contacted by the Registry after the Registry received the application from the Applicant’s Registrar.
    2. Applications in Standard Track Processing will be held in reserved Pending Create status for up to 30 days during which time they will be Advertised on the Registry-managed website https://domains.watch. During the Advertisement Period, third parties with Eligible Rights in the Requested Name may submit Competing Applications for the identical domain name.
    3. At any point during the Advertisement Period the original Applicant may apply to Expedite a Standard Track Application by submitting evidence of an Eligible Right in the Requested Name. If the Registry is satisfied at its sole discretion that such an Eligible Right exists, it will terminate the Advertisement Period and the Requested Name will be registered to the original Applicant.
  2. Fast Track Processing
    1. An Applicant that can demonstrate having an Eligible Right in the Requested Name may bypass Standard Track Processing, including the Advertisement Period, by requesting Fast Track Processing. In order to prevent the start of the Advertisement Period, Fast Track Processing must be requested by the Applicant within 5 (five) Business Days of the Applicant being contacted by the Registry notifying the Applicant of the Registry’s receipt of the Applicant’s Application from the Applicant’s Registrar. Requests made after this time will be rejected and the Application will be published on the Registry-managed website https://domains.watch via which third parties may submit Competing Applications for the identical domain name.
    2. An Eligible Right in respect of a Requested Name is one of the following:
      1. A nationally or regionally registered trade mark registered in respect of tickets or ticketing goods or services; OR
      2. A name or other term that, while not registered as a trade mark, has been used in trade to distinguish the tickets or ticketing goods or services of one undertaking from those of another. What constitutes tickets or ticking goods or services for the purposes of this policy will be decided by the Registry at its sole discretion.
    3. Applicants can demonstrate an Eligible Right based on a registered trade mark by providing the following information:
      1. The text of the trade mark as registered;
      2. The registration number of the relevant trade mark;
      3. The date of registration;
      4. The jurisdiction of registration of the trade mark;
      5. The name of the registered owner of the trade mark or documentary evidence confirming that the Applicant is authorised by the registered owner of the trade mark to make the Application and have the domain name registered to it; and
      6. The address of the registered owner of the trade mark.
    4. Applicants can demonstrate an Eligible Right based on an unregistered name or other term by providing at the request of the Registry, one or more of the following types of evidence which must contain the full text of the Eligible Right in a clear and stand-alone format:
      1. Dated tickets;
      2. Dated advertising and marketing materials for tickets or ticketing goods or services (e.g. brochures, pamphlets, catalogues, product manuals, displays or signage, press releases, screen shots, social media marketing materials etc.);
      3. Links to websites, screen shots from websites relating to the sale or advertisement of tickets or ticketing goods or services;
      4. Headed and dated stationery, receipts, invoices relating to the sale or advertisement of tickets or ticketing goods or services; or
      5. Dated photographs or scans of product labels, tags or containers demonstrating the sale or advertisement of tickets or ticketing goods or services.

Applicants or Competing Applicants will submit, via the https://domains.watch website, no more than 10MB of documentary evidence in support of each Application or Competing Application. Further pages need not be considered by the registry.

Supported IDN Scripts

The following IDN scripts are supported by .tickets.
Provide the LANGUAGE TAG corresponding to your desired IDN within the AddDomain command as X-IDN-LANGUAGE extension.


Get more information of "IDN tables", which represent permitted code points (letters) allowed for Internationalised Domain Name registrations in particular registries on IANA Repository of IDN Practices.

Wedomains :)