Reseller Documentation (DE)

• Generelle Informationen
• Was ist ein "OT+E" System?
• Warum ein Joker.com Reseller werden?
• Wie kann ich ein Reseller werden?
• Wer kann ein Reseller werden?
• Gibt es eine Gebühr, um Reseller zu werden?
• Wie aktualisiere ich meine Reseller-Daten?
• Wie füge ich bestehende Domains zu meinem Portfolio hinzu?
• Wofür dient die 'admin'-E-Mail-Adresse?
• Wofür dient die sogenannte 'Zusätzliche Whois-Signatur'?
• Was ist der Joker.com PGP/GPG-Schlüssel?
• Wenn ich Joker.com irgendwann verlassen möchte, muss ich dann mit Problemen beim Transfer meiner Domains rechnen?
• Wie hoch ist der Mindestfinanzierungsbetrag, um Reseller zu werden?
• Muss ich die Mehrwertsteuer bezahlen?
• Was ist der Unterschied zwischen einem Reseller und einem Endkunden?
• Muss ich PGP verwenden?
• Kann ich mehrere Methoden parallel verwenden, um auf meine Domains zuzugreifen?
• Wie verlängere ich eine Domain, ohne Guthaben auf meinem Konto zu haben?
• Reseller Control Panel
• The Reseller Control Panel
• The Joker.com PHP Client
• Installation of Joker.com PHP Client
• Usability Hints
• DMAPI
• Basics
• Account and Handling
• Domains
• Contacts
• Nameservers
• Modify Zonedata
• Rights and Roles
• Other Requests
• Code-Examples
• Email Gateway
• Basics
• Macros
• DNS / URL-Forwarding
• Domains
• Contacts
• Nameservers
• Other Requests
• Examples
• Plugins
• Joker.com WHMCS Plugin
• Clientexec Registrar Plugin
• Hostbill Registrar Plugin
• Werkzeuge
• Check Domain Availability

Generelle Informationen

Was ist ein "OT+E" System?

"OT&E" bedeutet "Operational Test & Evaluation".

Dies ist in der Regel der Name für Test- und Bewertungssysteme, bei denen Aktivitäten niemals "echte" Daten oder Eigenschaften wie registrierte Domains oder Kontakte verändern.

Unser OT&E-System ist eine Art "Kopie" von Joker.com, bei der spezielle "Dummy"-Registrys verbunden sind. Domainänderungen und Objektmanipulationen können durchgeführt werden, ohne dass mit echten Daten gearbeitet werden muss.
Dies ermöglicht es Wiederverkäufern, ihre Skripte, Programme und Methoden über die Joker.com Portale und auch per Joker.com API zu testen.
 

Unsere OT&E Systeme bestehen i.W. aus:

• www.ote.joker.com (standard Web Portal)
  
• ote.rpanel.io (Portal für Wiederverkäufer)
  
• dmapi.ote.joker.com (Joker.com API)
  
• whois.ote.joker.com (Whois)
  
  

Wenn Sie an der Nutzung dieser Systeme interessiert sind, sollten Sie erwägen, Wiederverkäufer von Joker.com zu werden.

Wiederverkäufer profitieren von Rabatten von bis zu 40% auf alle Preise.

Warum ein Joker.com Reseller werden?

Es gibt zweifelsohne viele gute Gründe, an unserem Reseller-Programm teilzunehmen. Lassen Sie uns die aufregenden Vorteile erkunden, die Sie genießen können:

• Rabatte: Als Joker.com Reseller erhalten Sie Rabatte auf alle Domaintransaktionen. Sie beginnen mit einem Rabatt von 20%, der sich je nach Aktivität auf bis zu 40% erhöhen kann. Sparen Sie Geld und erweitern Sie Ihr Geschäft - eine Win-Win-Situation!
  

• Benutzerfreundliches Interface: Erhalten Sie Zugang zum Reseller Control Panel (rpanel.io), einer alternativen Weboberfläche, die speziell für Wiederverkäufer entwickelt wurde. Dieses leistungsstarke Tool vereinfacht die Domain-Verwaltung und ermöglicht es Ihnen, selbst große Mengen an Domains und Kontakten mühelos zu verwalten. Durch die Darstellung der Daten in Echtzeit entfällt das zeitraubende Ausfüllen von Formularen.
  

• Test- und Prüfsystem: Testen Sie die Registrierungs- und Domainmanipulationsmethoden von Joker.com, ohne die realen Daten zu beeinflussen. Das OT&E-System stellt virtuelle Domains und Registries zur Verfügung, mit denen Reseller experimentieren und verschiedene Funktionalitäten testen können. Sie können furchtlos experimentieren, Ihre Fähigkeiten verfeinern und Vertrauen gewinnen.
  

• Nahtlose Integration: Unsere HTTP-basierte API macht die Skripterstellung und Integration in Ihre bestehenden Lösungen zu einem Kinderspiel. Automatisieren Sie Prozesse und optimieren Sie Ihre Arbeitsabläufe ganz einfach.
  

• Bequeme API und E-Mail-Gateway: Registrieren Sie Domains mühelos, indem Sie Befehle per E-Mail mit PGP-signierten E-Mails senden. Unsere benutzerfreundliche API und unser E-Mail-Gateway vereinfachen den Prozess der Domainregistrierung und sorgen für einen reibungslosen Ablauf.
  

• Integrationsmodule für Hosting-Lösungen: Wenn Ihr Unternehmen Hosting-Lösungen wie WHMCS, Clientexec oder Hostbill nutzt, können Sie Ihre Domain-Anforderungen mit unseren Integrationsmodulen automatisieren. Diese Module erleichtern die Domainregistrierung, -erneuerung, -abrechnung und -wartung und lassen sich nahtlos in Ihre bestehende Geschäftslösung integrieren. Die Installation erfordert nur ein paar einfache Schritte, wenn sie überhaupt notwendig ist.

Wie kann ich ein Reseller werden?

Klicken Sie einfach hier und folgen Sie den Anleitungen.

Wer kann ein Reseller werden?

Als Privatperson oder Unternehmen können Sie Joker.com Reseller werden. Wenn Sie fünf oder mehr Domains haben, lohnt es sich auf jeden Fall, über die Möglichkeiten eines Resellers nachzudenken.

Gibt es eine Gebühr, um Reseller zu werden?

Nein, die Anmeldung als Joker.com Reseller ist absolut kostenlos. Allerdings müssen Sie als Reseller Ihr Joker.com-Konto im Voraus aufladen (Pre-Payment). Die Höhe des Betrages, den Sie einzahlen, liegt ganz bei Ihnen.

Jedes Mal, wenn Sie eine Bestellung aufgeben, wird der entsprechende Betrag von Ihrem Konto abgebucht. Diese Funktion gewährleistet zuverlässige automatische Erneuerungen, wenn Sie sich dafür entscheiden, sie zu nutzen.

Wie aktualisiere ich meine Reseller-Daten?

Um Ihre persönlichen Daten, Ihre Standards für die Registrierung, Whois-Vorlagen und mehr zu ändern, melden Sie sich bitte bei Joker.com mit Ihren Reseller-Zugangsdaten an.

Klicken Sie dann im Dashboard unter "Schnellzugriff" auf "Resellerbereich" und wählen Sie "Resellerdaten aktualisieren", oder verwenden Sie das Menü "Resellerbereich", gefolgt von "Resellerprofil".

Weitere Einstellungen wie "Sprache für System-E-Mails" oder "Automatische Verlängerung" finden Sie unter Ihr Konto oder auch im Menü "Mein Joker", gefolgt von "Mein Profil".

Wie füge ich bestehende Domains zu meinem Portfolio hinzu?

Wechsel zu einem Reseller-Konto

Wenn Sie sich entscheiden, Ihr Joker.com-Login-Konto auf ein Joker.com Reseller-Konto zu migrieren, werden alle Ihre Domains automatisch zu diesem Reseller-Konto hinzugefügt.

Verschieben einer Domain von Joker.com Benutzer A zu Benutzer B (kooperativ)

Wenn Sie die vorhandene Domain besitzen und ein anderes Joker.com-Konto verwenden, klicken Sie auf das "Menü"-Symbol (das "Hamburger"-Symbol rechts) der Domain, die Sie verschieben möchten, und wählen Sie "Rechte".

Wählen Sie "Zuweisung" (= "Interner Transfer") als "Rolle", geben Sie die E-Mail-Adresse des Kontoinhabers ein, an den die Domain übertragen werden soll, fügen Sie bei Bedarf einen Kommentar/Beschreibung hinzu und klicken Sie auf "Hinzufügen".

Sie können dann weitere Domains hinzufügen. Drücken Sie bitte "Speichern", wenn Sie fertig sind.

Anschließend wird ein Transfer-Link an die von Ihnen eingegebene E-Mail-Adresse gesendet. Sie finden dies auch als "ausstehenden" Datensatz im oben genannten "Berechtigungen"-Dialog. Der "Transfer-Link" ist 7 Tage lang gültig.

Der Empfänger des Transfer-Links importiert die Domain einfach, indem er auf diesen Link klickt.

Alternativ enthält diese E-Mail auch einen "internen Transfer-Key", der über "Domain Transfer" auf Joker.com ("interner Transfer") verwendet werden kann.

Verschieben einer Domain von Joker.com Benutzer A zu Benutzer B (Beanspruchung)

Wenn Sie Domains von einem Joker.com-Konto (regulär oder Reseller) zu einem anderen Joker.com-Konto (z. B. Ihrem neuen Reseller-Konto) "verschieben" oder beanspruchen möchten, wählen Sie bitte "Inhaber/Rechtetransfer" im "Domains"-Menü.

Geben Sie Ihre Domain ein und klicken Sie auf "Weiter" - abhängig von den Whois-Daten und dem aktuellen Besitz der Domain müssen Sie möglicherweise ein Dokument einsenden.

Vorgehensweise mit dem E-Mail-Gateway

Wenn Sie Domains, die anderen Joker.com-Login-Konten gehören, "verschieben" möchten, können Sie dies einfach mit dem Roles & Grants-System durchführen, um einen internen Transfer zum gewünschten Konto durchzuführen.

Wofür dient die 'admin'-E-Mail-Adresse?

Ein Joker.com-Reseller hat in der Regel zwei registrierte E-Mail-Adressen bei Joker.com, eine für die 'Robot'-E-Mails und eine weitere für administrative Aufgaben.

Reseller-Neuigkeiten und monatliche Rechnungen werden an die administrative Adresse gesendet. Die 'Robot'-Adresse entspricht der Standardadresse, die mit dem Joker.com-Login verknüpft ist.

Alle Benachrichtigungen, die sich aus Domain-Bestellungen, Verlängerungen und Änderungen ergeben, werden an diese Adresse gesendet.

Diese Adresse für Benachrichtigungen kann einfach in 'Mein Profil' geändert werden.

Wofür dient die sogenannte 'Zusätzliche Whois-Signatur'?

Die "Zusätzliche Whois-Signatur" ist ein Teil der Daten, die während der Registrierung als Joker.com-Reseller abgefragt werden.

Diese Eingabefelder sind optional, aber wenn Sie sie bereitstellen, werden sie verwendet, um Ihre Zeichen im globalen Whois für Ihre Domains zu veröffentlichen.

Auf diese Weise können Ihre Kunden Sie als ihren Domain-Anbieter identifizieren.

Die von Ihnen bereitgestellten Zeichen werden als "Sponsoring Reseller" angezeigt.

Bitte beachten Sie: Sie können diese Daten jederzeit im Reseller-Bereich einrichten oder ändern.

Was ist der Joker.com PGP/GPG-Schlüssel?

Dies ist der öffentliche GPG/PGP-Schlüssel von Joker.com - Sie können ihn verwenden, um signierte Mails von Joker.com zu verifizieren:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mIsEPOorJQEEAJauWOOvusxn9GFEPjZnQ3x/48OfaPwSN4cIF5ezpUT6FycZQa+q
eUnNlS+bj80ULXnyyigmkUGwEtW/Qoyd55RM983pr4KtuHSMSU9gCN1syuHlDOAm
71u6irfv5RaHbJXauMCAgUKn+dBNZVZyUTm9aW2pudcwY45apF2tieTZAAYptClq
b2tlci5jb20gc2lnbmVyIHNlcnZpY2UgPGluZm9Aam9rZXIuY29tPoiyBBMBAgAc
BQI8/NifAhsDBAsHAwIDFQIDAxYCAQIeAQIXgAAKCRAm3eE0EUTiIx9RA/9HGDrD
cVM6PjZHr5jpT4svpv7xrjVRn2OIR+s80RuBAnLyAWOflqJ9342SYD8C7BMAqYm4
wXvC3/yvbQEAqsmJ5Bbq2NV+KDepahTtL8SUQ6TkOSUd9NDOvLoQWVI6o1Dz/3MG
HLJfNtx6067Sq8pP8PuYyscPyZ7/uiUilyOrqg==
=O/7Q
-----END PGP PUBLIC KEY BLOCK-----

Wenn ich Joker.com irgendwann verlassen möchte, muss ich dann mit Problemen beim Transfer meiner Domains rechnen?

Joker.com respektiert seine Kunden und bietet ausgehende Transfers als normalen Vorgang an.

Es gibt keine zusätzlichen oder versteckten Gebühren, die mit einem Transfer-Out verbunden sind.

Wie hoch ist der Mindestfinanzierungsbetrag, um Reseller zu werden?

Derzeit gibt es keine Mindestfinanzierung für Ihr Reseller-Konto. Ihr Rabatt basiert auf dem in der Vergangenheit erzielten Umsatz, so dass Sie die Flexibilität haben, in Ihrem eigenen Tempo zu wachsen.

Weitere Informationen finden Sie auch unter Joker.com Reseller Subscription.

Muss ich die Mehrwertsteuer bezahlen?

Es wird keine Mehrwertsteuer berechnet für:

• alle Wiederverkäufer und andere Geschäftskunden aus EU-Ländern außer Deutschland, die eine gültige USt-IdNr. angegeben haben
• Schweizer Kunden
• Kunden von außerhalb der EU

Die Mehrwertsteuer wird berechnet für:

• Kunden aus der EU, die keine gültige USt-IdNr.  haben
• Wiederverkäufer und Geschäftskunden aus Deutschland, unabhängig von der Umsatzsteuer-Identifikationsnummer (deutsche Kunden mit Umsatzsteuer-Identifikationsnummer sind in der Regel zur regulären Umsatzsteuer-/Steuerrückerstattung berechtigt)

Schweizer und Liechtensteiner Kunden sind bis zum 31. Dezember 2017 von der Umsatzsteuer befreit. Ab dem 1. Januar 2018 ändert sich dort die Gesetzgebung, was bedeutet, dass wir auch dort die Mehrwertsteuer berechnen müssen - es sei denn, Sie geben uns eine UID. 

Was ist der Unterschied zwischen einem Reseller und einem Endkunden?

Als Reseller profitieren Sie von mehreren zusätzlichen Optionen:

• Bessere und wettbewerbsfähige Preise; je mehr Umsatz Sie generieren, desto höher ist der Rabatt, den Sie erhalten.
• Benachrichtigungs-E-Mails zu Verlängerungen oder Anfragen werden nur an Sie gesendet.
• ICANN WDPR-E-Mails werden in Ihrem Namen gesendet (wir verwenden Ihre Adresse als Absender).
• Sie verwalten alle Domains Ihrer Kunden innerhalb Ihres Portfolios; jedoch können Sie, falls erforderlich oder gewünscht, Ihre Kunden - oder nur einige von ihnen - ihre Domains selbst verwalten lassen.
• Verschiedene Tools stehen kostenlos zur Verfügung (WHMCS, HTTP API, rpanel.io, Web-Frontend, E-Mail-Gateway, OT&E-Testplattformen).

Muss ich PGP verwenden?

PGP oder GPG wird nur benötigt, wenn Sie das E-Mail-Gateway nutzen möchten, um Domains zu bestellen, zu verlängern oder zu verwalten. Wenn Sie die API, RPanel oder die Website nutzen möchten, ist PGP nicht erforderlich.

Kann ich mehrere Methoden parallel verwenden, um auf meine Domains zuzugreifen?

Ja, das ist möglich. Sie sollten jedoch sicherstellen, dass Sie dieselben Aufträge nicht zweimal für dasselbe Objekt erteilen. Wenn Sie beispielsweise eine Verlängerungsanfrage über die Mail-Schnittstelle senden und dasselbe über DMAPI tun, wird die Domain zweimal verlängert.

Wie verlängere ich eine Domain, ohne Guthaben auf meinem Konto zu haben?

Bitte melden Sie sich von Joker.com ab und besuchen Sie dann "Verlängern" im "Domains"-Menü.

Sie sehen dann eine "Vereinfachte Verlängerung ", bei der Sie jede Domain mit jeder Zahlungsmethode verlängern können.

Sie können auch ein anderes Joker.com-Konto verwenden oder ein neues dafür erstellen. Nur wenn Sie mit Ihrem regulären Reseller-Konto angemeldet sind, verwendet das System immer die Reseller-Fonds für Zahlungen.

Alternativ können Sie auch nur geringe Beträge auf Ihr Reseller-Konto einzahlen, nur um regelmäßige Verlängerungen zu ermöglichen.

Die Verwendung von PayPal fügt sofort Gelder auf Ihr Konto hinzu.

Reseller Control Panel

The Reseller Control Panel

RPanel Next is the next generation of our Reseller Control Panel.

It has been created from scratch, focussed to provide you with the ultimate tool to handle all needs of a domain's business.

The application is pretty self-explanatory, but here is a short list of what's important to know about this tool. But you definitely should give it a try!

• Login 
  
  

  Click this link or type https://rpanel.io/ into the address bar of your browser. Use your known login credentials to login. (In case you aren't a reseller yet you can become one here in 3 easy steps).

  Once logged in, you'll see an overview of your account, your current balance, your ID and information about the number of domains you have. Additionally, current news and promo activities are providded, and a history your activities from the last 30 days is available.

  Filtering/searching is always possible using the header input fields on top of the table columns.

   

• Domains 
  
  
  
  

  Click on "domains" in the top menu and select "overview". In this view you see all your domains in a table from which you can modify every aspect of the domains. With a click on "register" in the top right corner you are able to register new domains. All these actions can be done from this overview table but you can also select the respective menu item from the domains menu on the top.

   

  

   

• Contacts 
  
  

  Click on "contacts" in the top menu to get an overview of all existing contacts. If you click on the contact handle you see all details about this specific contact. Clicking "modify" or "delete" on the right site lets you modify contact info or delete a contact alltogether. Deleting a contact has to be confirmed in the next step. The create button in the top right corner lets you create a new contact.

   

• Nameservers
  
  

  If you like to add new nameservers you can do this under the menu item "Nameservers". Create new ones or create a template for nameservers which you can use afterwards.

   

• Language
  
  

  Lets you switch between German and English. Those changes are not persistend. To change the default language, click on the user icon next to "language" and select "settings".

   

• Settings
  
  

  This is found under the profile icon. From this menu item you can edit your default language, your preferred date/time format, if and when you want to get notified when your balance runs low and if you want to activate or deactive domain autorenew globally. 

   

• Execute Request
  
  

  This is found under the profile icon. Here you can enter and execute DMAPI requests. Please check the DMAPI area in this FAQ for more information on that.

   

• Feedback
  
  

  This is found under the profile icon. Please provide us with feedback to further improve our new RPanel. Every kind of constructive feedback will be greatly appreciated. 

   

• Logout
  
  

  This is found under the profile icon. You are logged out automatically after a certain time of inactivity. If you are working on a shared computer or want to switch accounts you can log out here. 

   

• Cart
  
  

  If you registered any domains you have to check out your cart. Here you can add whois privacy to your domains if possible, change the registration period, auto renew status and configure the domain(s) (add contact information or nameservers).

The Joker.com PHP Client

Joker.com provides this tool as an fully working example of how to make use of the Joker.com API (DMAPI).

The Joker PHP Client is a lightweight web interface, demonstrating how to implement a full-featured domain handling.

Installation of Joker.com PHP Client

To successfully install this client application, you need a basic knowledge of Web servers, PHP and file systems.

In principle the installation is only a copy and run. The first thing to do is to ensure, that your Web server runs PHP files, and if not to configure it appropriately.

Quick installation:

 1. Untar or unzip the distribution (be sure to unzip the subdirectories):

tar -xzvf package_name_x.x.x.tar.gz

in your webserver's document root. If you don't have direct access to your document root, put the files in a directory on your local machine, and transfer the directory on your web server using, for example, ftp.

 2. Ensure that all the scripts have the appropriate owner (if PHP is running in safe mode, having some scripts with an owner different from the owner of other scripts will be a problem). Be sure that the application can write log files, temp files and sessions. This means that the folders specified in config.php should be made writeable for the application.

 3. This application needs cURL to communicate with DMAPI. You have to have the cURL PHP module enabled. If you run Windows it is provided with every instance of PHP and has to be uncommented in php.ini. Do not forget to restart your webserver after enabling the module. If you run Linux then this module has to be compiled and included. If you wonder how to do this, please read the PHP manual dealing with cURL (http://php.net/curl).

Problems were reported when "zend.ze1_compatibility_mode" is set to "on" in PHP 5.2.5. In lower versions this setting caused no problems.

 4. It is recommended that you protect the directory in which you installed the client (unless it's on a closed intranet), for example with HTTP-AUTH (in a .htaccess file).

 5. Open the file <www.your-host.com>/<your-install-dir>/index.php in your browser. The Joker.com PHP client should now display a welcome screen with a login dialog.

Have fun and don't forget to send feedback!

Usability Hints

Some notes:

• The default session duration of DMAPI (the service behind this interface) is 1 hour. This means that after 1 hour of inactivity, you will be logged out of both DMAPI and Reseller Control Panel, and asked again for your username and password.
• For support issues, please send us your inquiry through our support area.

DMAPI

Basics

    domain=example.com
    period=12 (in months, as usual)
    expyear=2016 (privacy expiration year, similar to domain renewal request)
    privacy=basic|pro 

    If neither period nor expyear is provided, then privacy is ordered for
    remaining domain lifetime, whatever it is.

    Example:
    https://dmapi.joker.com/request/domain-privacy-order?domain=example.com&privacy=basic&auth-sid=<your-current-session-id> 

Account and Handling

login

Login with Username & Password

Requires (mandatory):

Returns:

To be able to use the entire API, you must have a reseller account with Joker.com (and use this account to log in).

 Example:

  https://dmapi.joker.com/request/login?username=johndoe&password=mypass

Login with API Keys

Instead of using your user- and password credentials, you may also use so called 'API keys' for login. This way, you can create several DMAPI access facilities, which has several advantages:

• you do not need to expose username and password in your scripts
• API keys can be restricted to be "read only" (no modifications possible), or to allow 'modifications only' (can not produce costs)
• you may hand API keys to your staff to enable them to do specific things with Joker.com

Create your API keys in 'My Profile' in section 'Manage Joker.com API access keys'

Example usage:

https://dmapi.joker.com/request/login?api-key=Key_created_in_your_Profile_at_Joker.com

The result is the same as for "login"-request, you have to use the provided auth-sid for the subsequent actions.

logout

Returns: Nothing

Used to forcibly close (terminate) a session. The session identified by Auth-SID may not be used anymore to send requests. Normally not required as session will timeout anyway (default: 1 hour).

result-list

Accepts:

 Returns:

List of answers from joker.com (one per line):

TimeStamp SvTrId Proc-ID request-type status ClTrId

Where:

TimeStamp: The time when request was made, YYYYMMDDHHMMSS
SvTrID: Tracking-Id associated with this request.
Proc-ID: Proc-Id associated with this request.
request-type: The type of the request.
request-object: The object name (host, domain or contact handle)
status: ack, nack or ?, where ack means that request was completed successfully.
ClTrId: User specified transaction ID, or "-" if nothing was provided by the user

 Example:

https://dmapi.joker.com/request/result-list

result-retrieve

Accepts:

Returns:

Please note:

Since there is no requirement of uniqueness for user-specified transaction ids, it is not possible to use them to retrieve specific results. 

Example:

  https://dmapi.joker.com/request/result-retrieve?proc-id=8181810&auth-sid=<your-current-session-id>

result-delete 

Accepts:

Returns:

A descriptive message (confirmation) in case of success.

This request will delete the content (not the status) of a reply to an asynchronous request. Deleted results will not be listed anymore when using result-list.

query-profile 

Returns:

Returns reseller profile data in format "key: value". May be used to query account balance

 Example:

https://dmapi.joker.com/request/query-profile

query-account-balance

Returns:

Returns actual account balance - available, pending and total.

Example:

https://dmapi.joker.com/request/query-account-balance

You will get a response like this:

Status-Code: 1000
Status-Text: OK
Columns: available,pending,total,currency
Separator: TAB

975.00	25.00	1000.00	USD

The columns are:

query-order-list

Parameters

Returns

A CSV-like list following the usual DMAPI header:

Status-Code: 1000
Status-Text: OK
Row-Count: 6
Columns: order_id,proc_id,created_at,status,type,amount_brutto,amount_netto,currency,identifier

85671266	917263183	2024-03-17T07:58:14Z	ok	renew	10.19	10.19	USD	example.org
85671265	917263182	2024-03-17T07:58:12Z	ok	renew	10.19	10.19	USD	example.com
85671256	917263173	2024-03-17T07:57:06Z	ok	renew	29.40	29.40	USD	example.net
85671255	917263172	2024-03-17T07:57:05Z	ok	create	2.00	2.00	USD	example.zone
85671227	917263144	2024-03-17T07:54:07Z	ok	service_request	0	0		example.com
85671226	917263143	2024-03-17T07:54:07Z	ok	create-contact	0	0		CCOM-91167381

Output columns description

Positive amounts are amounts paid, i.e. deducted from your balance.

Negative amounts are amounts received, i.e. added to your balance. This usually happens if you get a refund.

If status is not ok, then the amount is neither added or deducted - it is just a reference to the cost of the order.

If show-all=false (the default) then only orders processed within last 3 years are visible.

If show-all=true then only orders from last 90 days are visible.

Period covered by after/before parameters may not be longer than 90 days. The period is enforced silently, you will get no warning - just orders within 90 days, so if there are none you will see empty response.

Empty (no rows) output means that there are no orders matching specified parameters are visible.

If you use ranged search by order-id or proc-id and do not limit search period using after and/or before, the maximum number of rows returned is 1000 (and is the default). It could be lowered by using limit parameter, but 1000 is the maximum anyway.

However, if you do use after and/or before parameters, they will be applied independently - this means that if specified id range does not fit into specified time range, you will get no results.

Parameters fqdn and fqdn-like actually could be used not only for domain names but for other object identifies, like contact handles - it depends on operation.

Please note that all returned data, including amounts charged, is for informational purposes only!

The sum of amounts may not exactly match the issued invoices due to possible adjustments related to discounts, manual processing, and other corrections that cannot be properly reflected in this list.

Domains

query-domain-list

Accepts (optional)

Returns

List of registered domains and their expiration dates (one per line, separated by whitespace). If "showstatus" is present, the the list will be with three columns, the last one showing domain status (like "lock,autorenew" etc - comma separated).

Example:

https://dmapi.joker.com/request/query-domain-list?pattern=a*&showstatus=1&auth-sid=<your-current-session-id>

domain-register

Requires (mandatory)

Accepts (optional)

 This request allows to register a domain.

You must have registered contacts (handles) to be able to register a domain.(=> contact-create, query-contact-list)

Important: Please note that the registration period is in months, not years. In most cases, this number is a multiple of 12.

Example:

https://dmapi.joker.com/request/domain-register?domain=example.com&period=12&status=production&owner-c=COCO-4711&billing-c=COCO-4712&admin-c=COCO-4712&tech-c=COCO-4712&ns-list=a.ns.joker.com,b.ns.joker.com,c.ns.joker.com&auth-sid=<your-current-session-id>

domain-renew

Requires (mandatory)

Accepts (optional)

With this request you can renew the domain. Please be aware that all renewals are not refundable.

"expyear" is a safety option which can be used instead of "period" to renew domain till specified year (not longer). If you use "period", and by mistake send the request more than once, domain will be renewed again, while with "expyear", it will not be renewed if it's expiration year is greater or equals to specified.

Only one of "period" or "expyear" may be used, but not both.

 Please note:

• registration period is in months, not years! In most cases, this number is a multiple of 12.
  
• to prevent from unintended/errorneous multiple renewals, a specific domain name can only be renewed once per 6 hours. This means, if you want to renew a domain for 2 years, you should use a period of "24" - in case you want to renew using two requests with a period of "12", the 2nd request must not be sent before 6 hours after the 1st one.
  

Example:

  https://dmapi.joker.com/request/domain-renew?domain=example.com&period=12&auth-sid=<your-current-session-id

domain-modify

Requires (mandatory)

Accepts (optional)

With this request you can modify

• contact handles
• nameservers
• DNSSEC parameters (for DNSSEC capable nameservers and TLDs supporting DNSSEC)

 Please only specify contact handles which you want to modify, all unspecified handles will be left as is.

 For DNSSEC, you will find more information here .

Example:

 Example for adding a key (and enabling DNSSEC):

Example for removing DNSSEC information:

domain-delete

Requires (mandatory)

Accepts (optional)

With this request you can delete a domain.

If you delete a domain (gTLDs only) within the first 72 hours after the registration, the registration-fee will be refunded to your account.

To delete a domain which is registered for more than 72 hours, you must specify "force=1", otherwise the request will be rejected.
Please note: The number of refundable deletions of domains per month is limited, and depends on the number of domains in a portfolio, and the related TLD registry.

Example:

domain-owner-change

Requires

With this request you can change the visible WHOIS owner of a domain.

Either "name" or "lname" and "fname" must be provided. Fields not marked as optional are mandatory, and must not be empty.

For the revised ICANN IRTP-C (change of registrar) policy, please also visit our documentation.

Example:

domain-lock

Requires (mandatory)

With this request you can lock a domain to prevent from fraudulent transfer attempts.

If a domain is locked, each transfer-request from a foreign registrar will be declined.

 Example:

https://dmapi.joker.com/request/domain-lock?domain=example.com&auth-sid=<your-current-session-id>

domain-unlock

Requires (mandatory)

With this request you can unlock a domain.

If you want to transfer a domain to a foreign registrar, it has to be unlocked.

 Example:

https://dmapi.joker.com/request/domain-unlock?domain=example.com&auth-sid=<your-current-session-id>

domain-transfer-in-reseller

Requires (mandatory)

With this request you can initiate a transfer of the domain from another registrar to Joker.com.

You have to provide a valid AUTH-ID (you have to request this from the current provider of the domain). 

Please note:

• please make sure, that there is no so-called 'registry lock' active for the domain to be transferred. Please verify, that the current registrar does not block the domain, resp. deactivates the blocking
• the domain to be transferred must have been active for at least 60 days at the current registrar, otherwise the transfer may fail
• the domain to be transferred must not be object of an active ICANN UDRP dispute procedure
• the domain should have a remaining term of least 7 days, to ensure that the transfer succeeds within the time limits (a maximum of 5 days is granted to confirm or object a transfer). In case the domain has less than 7 days of remaining term, a successful transfer cannot be warranted.
• this procedure will trigger email notifications to the owner and the admin contact of the domain to be transferred (this is following mandatory ICANN transfer provisions)

Example:

domain-set-property

Requires (mandatory)

 With this request you can set a property (flag) for a domain or a set of domains, selected by wildcard pattern.

List of available properties and their effects:

If an empty value is provided, then the property will be cleared, i.e. the default will be used.

Example:

domain-get-property

Requires

With this request you can query the value of a specific property set for a domain. 

It returns a single line, which looks like:

Example:

domain-transfer-get-auth-id

Requires

 Retrieves domain's Auth-ID, which is required when transfering domains to another registrar.

This request is not real-time, i.e. you have to check detailed reply (use "result-retrieve") to get the Auth-ID.

 Please note:

Every request will generate a new Auth-ID, thus rendering any previously requested Auth-ID invalid.

 Example:

domain-transfer-control

This request allows to retrieve status information for all pending transfers. Additionally, transfers can be cancelled, or the FOA email can be re-sent. 

Parameters:

        action                  One of: list, show, resend-foa, cancel
        domain                  Domain name to control transfer of (ignored when action=list)
 

action=list

When action=list, this request returns a list (columns are separated by tabs) of all currently pending transfers:

        <domain> <state> <owner-email> <admin-email>

where <state> is one of (listed in "natural" transition order):

                IN_DB
                PAYMENT_PREPARED
                PAYMENT_ACQUIRED

                PENDING_FOA_SENDING

                        Joker.com could not parse the recipient of the FOA.
                        Manual action from Joker.com is required and happens
                        during office hours, thus in worst case it may take
                        few days (during weekend or holidays).

                FOA_BEEN_SENT
                
                        FOA is sent and Joker.com is waiting for owner's
                        reaction. Owner has 5 days to react, thus the state
                        may last up to 5 days.
                        
                FOA_NACK                FOA is rejected
                FOA_ACK                 FOA is accepted

                REGISTRY_REQUEST_SENT

                REGISTRY_REQUEST_RECEIVED_NOW_WAITING
                
                        FOA had been accepted, transfer request is sent
                        and the losing registrar has to release the domain.
                        This state may take up to 5 days, we could do nothing
                        to speed it up.
                        While in this state, transfer may be cancelled
                        by using "action=cancel".

                REGISTRY_CANCELATION_PENDING
                
                        The user has requested cancel of domain transfer
                        by using "action=cancel".

                DOMAIN_WITH_JOKER_PENDING_COMPLETE
                
                        The domain is actually with Joker.com, but either
                        we haven’t noticed yet (batch pending) or manual
                        work is necessary.
                        Please contact Joker.com if this state lasts longer
                        than 1 hour.

                PAYMENT_COMMITTED

                TRANSFER_PROCESSED_SUCCESSFULLY

action=show

When action=show, the status of a specified domain is returned like:

        domain: example.com
        status: FOA_BEEN_SENT
        owner_email: owner@example.com
        admin_email: admin@example.com
        transfer-id: 123456

action=resend-foa

When action=resend-foa, FOA will be resent (only possible in state FOA_BEEN_SENT).

action=cancel

When action=cancel, the (pending) transfer will be cancelled.

Returns

Status code is 1000 for successful request, or >= 2000 otherwise.

Example

https://dmapi.joker.com/request/domain-transfer-control?domain=example.com&action=resend-foa

domain-check

Requires (mandatory)

Accepts (optional)

With this request you can check if a domain is available for registration, and what type of domain pricing will be applied for different types of orders.

Returns one or more lines with key-value pairs as follows:

domain-status: <status>

<status> can be one of:

If <status> is "unavailable", then domain-register request will fail, though domain-transfer-* and domain-renew (if domain is with Joker.com) are possible, of course.

domain-status-reason: <status-reason>

Provides human-readable description why domain is unavailable for registration, like blocked, reserved, registered etc.
May be absent if registry does not provide specific reason. Should not be parsed as value is registry dependent and could be virtually anything.

domain-class: <class>

Specifies price-class. Anything but "standard" is considered "premium", though some registries use "tier-1", "premium", "BBB" etc.
Mostly a hint, values except "standard" should not be interpreted as they have no useful meaning and vary among registries.

domain-price-<type>: <price> <currency> <period>y

Reports domain price, where <type> will be value provided in check-price parameter, i.e. create, renew, transfer, restore.

• <price> is the final price, i.e. amount that will be deducted from the user's account, considering all discounts, promos etc.
• <currency> is a 3-letter currency code, serves only as information.
• <period> is reported in years and suffixed by "y", like "5y", and it may be different from "period" parameter value (depends on registry), for instance when requested period is not available, too low or too high.
  The price reported is valid only for specified period, i.e. if price is 100 for 2 years it does not necessarily mean that price for 1 year is 50, thus it only makes sense to check price for the period which will be used verbatim in subsequent request of specified <type>.

domain-price-promo: <start> <end>

<start> and <end> are ISO timestamps in format like 2019-07-01T00:00:00.000Z

For domains that have promotional pricing, this provides start and end timestamps of promotional period. Usually its mere presence means that promo-pricing is in effect, but to be sure values have to be checked explicitly.
If "domain-status" returned "premium" or "domain-class" returned anything but "standard", then the parameter max-price must be present in register/transfer/renew requests.

Full response example (web.blog):

    domain-status: unavailable 
    domain-status-reason: blocked 
    domain-class: standard 
    domain-price-create: 8.21 USD 1y 
    domain-price-promo: 2019-09-01T00:00:00.000Z 2019-12-31T23:59:59.000Z 

Example:

https://dmapi.joker.com/request/domain-check?domain=example.com&auth-sid=<your-current-session-id>

Contacts

query-contact-list

Accepts:

Returns:

List of registered contacts (handles), one per line.

When "extended-format" is requested, output columns are separated by tabs ("\t"), and "Columns" header provides column names.

 Example:

https://dmapi.joker.com/request/query-contact-list?pattern=coco-47*&tld=com&auth-sid=<your-current-session-id>

contact-create

Requires:

Either "name" or "lname" and "fname" must be provided. 

Fields not marked '(optional)' are mandatory (and must not be empty).

Parameters "lname" and "fname", if provided, will be converted to "name" (simple concatenation of "fname" and "lname"), because registries support only "name" format. In general, use of "fname" and "lname" is deprecated, and support for these fields will be removed in version 1.2.

"orgid" represents Swedish personal or organisational number and is required for .SE/.NU contacts.

It starts with ISO 3166 Alpha-2 country code in square brackets. If the country code for Sweden is given [SE] a valid Swedish personal or organisational number must be given (6 digits, dash, 4 digits), otherwise 1 to 123 characters can follow.

If organization is empty and the country code for Sweden [SE] is given, orgid must be a personal number, not an organisational number.

"vatid" is optional for .SE/.NU contacts. It starts with a two letter country code (uppercase), followed by an optional space, followed by a country specific string containing digits 0-9, and letters a-z and A-Z, maximum 64 Chars.

For .fi contacts:

"x-ficora-type" is required for .fi contacts. The following values are accepted: privateperson, company, corporation, institution, politicalparty, township, government, publiccommunity

"x-ficora-registernumber" is required if x-ficora-type is set to "company".

"x-ficora-is-finnish" is always required for .fi contacts: yes = finnish company or person, no = not a finnish person or company

"x-ficora-identity" is required for .fi contacts, if x-ficora-type is set to 'privateperson' and x-ficora-is-finnish is set to 'yes'

"x-ficora-birthdate" is required for .fi contacts, if x-ficora-type is set to 'privateperson' and x-ficora-is-finnish is set to 'no' in the following date format "YYYY-MM-DD".

Please note:

• Parameters listed here (except "tld") may be used (or are required) in other requests, this is indicated by referring to "Contact fields".
• "lang" must contain two-letter ISO country (language) code, and is only required when creating .EU contacts. The purpose is to specify language to be used in notifications emails, sent from EURid. Please note - this field cannot be modified later, and the default is 'EN' (English)!
• "app-purpose", "nexus-category" and "nexus-category-contry" are required only when creating .US contacts, and cannot be modified later.

 Example:

https://dmapi.joker.com/request/contact-create?tld=com&name=John Doe&email=johnd@someisp.com&address-1=Smartroad 1&city=Smalltown&postal-code=40122&country=US&phone=+1.422.8001&auth-sid=<your-current-session-id

contact-modify

Requires:

Accepts:

Field names exactly like in contact-create request, except that omitted fields won't be modified. That is, if you specify a field, it will be used as a new value, if you omit it, the old value will remain.

The field "tld" is not relevant for this request and will be ignored if present.

contact-delete

Requires:

With this request you can delete previously registered contacts 

Example:

https://dmapi.joker.com/request/contact-delete?handle=coco-4711&auth-sid=<your-current-session-id>

Nameservers

query-ns-list

Accepts:

 Returns:

List of registered name servers, one per line.

If "full" is non-zero, then the list will include IP addresses, IPv4 (2nd column) and IPv6 (3rd column).

Columns will be separated by tab ("\t") character. If specific IP is not present (say, there is only IPv4 or IPv6), it will be listed as "-".

 Example of list with IPs:

Example:

  https://dmapi.joker.com/request/query-ns-list?pattern=*my-own-ns*&full=1&auth-sid=<your-current-session-id>

ns-create

Requires:

With this request a new nameserver can be registered with the registry. This is needed to use a nameserver with glue records.

Either an IPv4 or IPv6 address is required.

Multiple IPs could be specified using "," (comma) as a separator, like "ip=1.2.3.4,4.5.6.7"

ns-modify or host-modify

Requires:

With this request you can modify the IP address of a registered nameserver. 

Multiple IPs could be specified using "," (comma) as a separator, like "ip=1.2.3.4,4.5.6.7"

ns-delete or host-delete

Requires:

With this request you can delete a registered nameserver.

Modify Zonedata

dns-zone-list

Accepts:

Returns:

List zones (domains) which are managed and served by Joker.com name
servers. Zones are listed one per line.

dns-zone-get

Requires:

Returns:

Returns list of zone records.

The format of zone is as follows (one record per line):

<label> <type> <pri> <target> <ttl> <valid-from> <valid-to> <parameters(s)> 

Where:

All values from "name" to "ttl" are mandatory for every record.

<valid-to> and <valid-from> are not implemented yet, so usually are 0, and may be omitted if there are no other parameters required.

<parameters(s)> are record dependent, used in NAPTR, MAILFW, FRAME and URL records.

<ttl> must be at least 60 for all records except NAPTR and SVC, where it can be 0 (meaning: no caching). For MAILFW/URL/FRAME <ttl> is irrelevant and assumed to be 60 seconds (i.e., any change will be
in effect within 60 seconds from zone change).

<pri> preference value for MX records, priority/weight for SRV records and order/preference for NAPTR records. For any other record, the value must be 0.

Examples of zone records:

 www A 0 127.0.0.1 86400
www AAAA 0 fec0::17 86400

@ MX 10 mail.example.com. 86400

redirect URL 0 http://joker.com 86400

Sets redirection from redirect.joker.com to http://joker.com (assuming that current zone is "joker.com").

frame FRAME 0 http://joker.com 86400 0 0 "Header: Frame-Forward" "head" "title" "body"

Sets frame-based redirection similar to URL redirection.

For FRAME record, extra parameters are as follows:

• Extra HTTP headers. (newlines may be escaped as \n)
• Extra text placed in <head></head> section of generated HTML.
• Title text (<title></title>) of generated HTML.
• Body text (used for <noframes> section)

username MAILFW 0 redirected@example.com 86400 0 0 1

This MAILFW records makes redirection of mail sent to username@joker.com (assuming that current zone name is "joker.com") to redirected@example.com, extra parameter ("1") specifies that spam-filtering should be used.

naptr NAPTR 10/100 replacement 86400 0 0 "flags" "service" "regex"

This NAPTR record has order 10 and preference 100. Only one of "replacement" or "regex" may be
specified, if "regex" is specified, "replacement" must be "." (without quotes), if "replacement"
is specified, "regex" must be empty string. Quotes are mandatory for all extra parameters.
For details please consult RFC 2915, or look here: http://de.wikipedia.org/wiki/NAPTR

_ldap._tcp SRV 10/100 ldap.example.com:389 60

This SRV record has priority 10, weight 100, target "ldap.example.com" and port "389" with TTL 60 seconds. Please consult RFC 2782 for details.

txt TXT 0 "key=value" 86400

Quoting of values for TXT records is mandatory.

caa   CAA 0   issue "letsencrypt.org" 86400
caa   CAA 0   issuewild "letsencrypt.org" 86400

caa   CAA 0   iodef "mailto:certissues@example.com" 86400

For more information about CAA records please check Wikipedia. 

www CNAME 0 example.com. 86400

Two special record types, DYNA and DYNAAAA, are used in case if DynDNS is active.
They have same meaning as corresponding "A" and "AAAA" records, except that their targets may be updated using Joker DynDNS service.

To enable/disable DynDNS service, and to define username/password used to access it, the record format is as follows:

$dyndns=yes:username:password

username/password may not contain spaces or colon (":") characters. If "no" is specified instead of "yes", DynDNS will be turned off (i.e. DYN* entries will have no effect).

In case if there are any errors, zone modification will not be accepted. All errors will be reported for every erroneous line, so if there are more than one, you will be able to see all detected errors.

dns-zone-put

Requires:

Returns:

Replace current zone for provided domain with specified value.

Field "zone" will be parsed as multiline text (so usual line erminators are expected).

Warning: This request will overwrite current zone, i.e. all current ecords will be replaced by new records.

The format of zone is as follows (one record per line):

<label> <type> <pri> <target> <ttl> <valid-from> <valid-to> <parameters(s)>

Rights and Roles

grants-list

Requires:

Accepts:

Get a list of active and pending grants. 

Returns lines in the following format (space-separated):

invitation <nr> <scope> <key> domain <domain-name> <role> - - - <invitee-email> <nick-name> grant <nr> <scope> domain <domain-name> <role> <inviter-username> <invitee-username> <invitee-userid> <invitee-email> <nick-name> 

 Where:

grants-invite

Request parameters:

With this request you can assign 'Roles' (permissions) of domains to other Joker.com users. The special role "creator" is an equivalent to an internal transfer of that domain to another Joker.com user. In this case, the domain is assigned to the receiving account's portfolio, including all rights and permissions on this domain.

There are two variants to use this functionality: If the client-uid (Joker.com user account id) is given, and the client-uid matches the associated user's email address in our system, the role is applied immediately - there will be no request for confirmation on the receiver's side. In case the client-uid is not given, but only the email address, the transaction has to be acknowledged by the receiving user. For this, he will get an email ('invitation'), containing a link and a key. Either the link has to be clicked, or the key has to be applied using Joker.com (=> Transfer). This can also be used for users which do not yet have a Joker.com account.

Returns status only (ok or not). Email is sent if request was succesfull.

grants-revoke

Requires:

Deletes an issued grant (permission) of a domain, or a pending invitation for a grant. 

Returns status only (ok or not). Email is sent if request was succesfull.

Other Requests

query-object

Accepts:

Returns:

Information about specified object (similar to whois), in format "key: value".

This request is deprecated - please use ' query-whois' instead.

query-whois

Accepts:

Returns:

Information about specified object (similar to whois), in the format "key: value".

The difference to the query-object request is, that this request reflects actual (live) data in Joker.com database, while query-object may show data which not yet up-to-date.

wa-email-list

Lists all domains and owner emails of domains from your portfolio which are pending whois (email) verification.

For Whois validation, the email address of the owner contact of a newly created, transfered or modifed gTLD has to be verified.This verification is done by sending an email to the owner contact, which contains a unique key in a link. When this link is clicked, the related email address is set to "validated".

 For full ICANN policy, please see Whois-Validation.

Requires: Nothing

Returns:

email-address<TAB>domain-name<TAB>verification-expiration-date

  email-address<TAB>domain-name<TAB>verification-expiration-date

 Where:

wa-email-details

Returns email verification status and the associated domain for provided verification key (whois verification, email validation).If there is more than one domain using the email address to be verified, output will have one line per domain. 

For full ICANN policy, please see Whois-Validation. 

Requires:

key Verification key sent to owner by verification email

Returns:

status<TAB>email<TAB>domain

Where: 

Sample:

wa-email-validate

Triggers a new email verification. In case the original verification email got lost or did not succeed otherwise, this request will send a new email. The original key will be automatically included.

This request returns special response header "Result", which will contain "ACK" if the validation request has been sent successfully, or "NACK" otherwise, e.g. if the email address is not in "verification pending" status, or already verified (whois verification, email validation).

 For full ICANN policy, please see Whois-Validation.

Requires:

email   Email address to send validation request to. This must be domain owner's email address.

 Returns:

Result: ACK    validation request has been sent
Result: NACK   no validation request has been sent for this email

 Sample:

wa-email-verify

key      Verification key sent to owner by verification email
answer   Answer to verification request - "yes" or "no"

Result: ACK    validation request has been successful
Result: NACK   validation request has been rejected or failed

domain-privacy-order

This request adds a subscription to Whois Privacy Services to an existing domain name.

A summary of all privacy related DMAPI commands is also available at DMAPI Whois Privacy Services.

 Requires (mandatory):

Accepts (optional):

"expyear" is a safety option which can be used instead of "period" to order privacy until the specified year (not longer).

If you use "period", and by mistake send the request more than once, the order would be executed again, while with "expyear", it will not be renewed if it's expiration year is greater or equals to the specified one.

Only one of "period" or "expyear" may be used, but not both.

 If neither period nor expyear is provided, then privacy is ordered for the remaining domain lifetime, whatever it is.

 Important: Please note that registration period is in months, not years! In most cases, this number is a multiple of 12.

 Example:

  https://dmapi.joker.com/request/domain-privacy-order?domain=example.com&privacy=pro&auth-sid=<your-current-session-id

This would order privacy service "pro" for the same period as the current term of the domain "example.com".

cor-verify

Authorizes a 'Change of Registrant' (COR) according to the ICANN IRTP-C policy as of 2016-12-01.

Please find the full documentation of the process at Joker.com here, the original ICANN policy is available here.

 This request can be used if you did not setup a verification 'push' URL with our provided module (see link above), or you want to use the standard email procedure.

 This request returns special response header "Result", which will contain "ACK" if the authorization request has been sent successfully, or "NACK" otherwise, e.g. if the key sent does not match the transaction.

 Requires:

key     authorization key (provided in COR confirmation request)
answer  answer to confirm the COR - "yes" or "no"

If the answer is "yes", the change-of-registrant will be executed, if in case of "no", it will be rejected. Please also note the new flag 'lock-opt-out' in 'domain-owner-change' if you do not want to lock the domain after the COR for 60 days.
Returns:

Result: ACK    authorization key has been accepted
Result: NACK   authorization key has not been accepted

 Sample:

query-price-list

Returns

List of domain prices per action and year (separated by tab) in the currency of the reseller account. The prices already include the reseller discount and also vat if it applies.

 Example:

https://dmapi.joker.com/request/query-price-list?auth-sid=<your-current-session-id>

query-promos-list

Parameters:

Returns:

List of promos with prices, current (active), upcoming or both, example response:

Status-Code: 1000
Status-Text: OK
SvTrId: 01db520b6683da6ae6a40ad503527bd8
Tracking-Id: 01db520b6683da6ae6a40ad503527bd8
Separator: TAB
Columns: type,operation,tld,currency,vat,price,standard_price,retail_price,min_period,max_period,period_type,valid_from,valid_to

domain	create	art	EUR	0.19	1.9	20.01	33.35	1	1	flex	2024-12-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
domain	create	blog	EUR	0.19	3.72	19.66	32.77	1	1	flex	2024-12-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
domain	create	com	EUR	0.19	12.36	10.16	16.93	1	1	flex	2024-11-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
domain	create	eu	EUR	0.19	3.25	4.46	7.44	1	1	flex	2024-11-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
...
domain	create	fun	EUR	0.19	1.91	25.01	41.68	1	1	exact	2024-07-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
domain	create	fun	EUR	0.19	10.0	50.02	83.36	2	2	exact	2024-07-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
domain	create	fun	EUR	0.19	18.1	75.03	125.05	3	3	exact	2024-07-01T00:00:00.000Z	2024-12-31T23:59:59.000Z
...

Values are TAB-separated, columns are:

All prices are netto (without VAT).

When period_type is flex, the price is per year, i.e. when you create/renew/transfer domain for more than one year the named price will be charged for every year.

When period_type is exact, the price is applied to the number of years specified in min_period, i.e. total price for the whole period. Please pay attention in such cases, as there may be multiple rows with same TLD for this kind of price - one for specific number of years (check last 3 rows in the example above).

Code-Examples

Perl

List domains of customer

#!/usr/bin/perl
use LWP::UserAgent;
use Data::Dumper;

my $dmapiURL = "https://dmapi.joker.com/request";

my $ua = LWP::UserAgent-> new;

my $req = HTTP::Request-> new(GET => $dmapiURL.'/login?username='.shift().'&password='.shift());
my $res = $ua-> request($req);

unless ($res-> is_success) {
print "Failed: ", $res-> status_line, "n";
exit -1;
}

my $auth=$res-> as_string;
my $output;

if ($auth =~ /Auth-Sid:s*(w+)/ms) {
$req=HTTP::Request-> new(GET => $dmapiURL.'/query-domain-list?auth-sid='.$1);
$res = $ua-> request($req);
if ($res-> is_success) {
$output=$res-> content;
}

else{
print "Failed: ", $res-> status_line, "n";
exit -2;
}
}

else {
print "Failed: Got no auth-id from DMAPI:n";
print $res-> content;
exit -3;
}


my @lines=split ("n",$output);
my $month=now + ("2M");
my %list;

my $p=0;
for my $line(@lines) {
#Skip first line
next unless $p or $line =~ /^s*$/;
unless ($p) { $p=1; next};
my ($fqdn,$exp)=split ("[ t]+",$line);
$list{$fqdn}=$exp;
}

for (sort keys %list) {
print "$_n";
}

List domains to expire next month

Needs:

Class::Date and Date::Parse from CPAN!

#!/usr/bin/perl

use LWP::UserAgent;
use Data::Dumper;
use Class::Date qw(:errors date localdate gmdate now -DateParse);

my $dmapiURL = "https://dmapi.joker.com/request";

my $ua = LWP::UserAgent-> new;
my $req = HTTP::Request-> new(GET => $dmapiURL. '/login?username='.shift().'&password='.shift());
my $res = $ua-> request($req);

unless ($res-> is_success) {
print "Failed: ", $res-> status_line, "n";
exit -1;
}

my $auth=$res-> as_string;
my $output;

if ($auth =~ /Auth-Sid:s*(w+)/ms) {
$req=HTTP::Request-> new(GET => $dmapiURL. '/query-domain-list?auth-sid='.$1);
$res = $ua-> request($req);

if ($res-> is_success) {
$output=$res-> content;
}
else {
print "Failed: ", $res-> status_line, "n";
exit -2;
}
}
else {
print "Failed: Got no auth-id from DMAPI:n";
print $res-> content;
exit -3;
}


my @lines=split ("n",$output);
my $month=now + ("2M");
my %list;

my $p=0;
for my $line(@lines) {
#Skip first line
next unless $p or $line =~ /^s*$/;
unless ($p) { $p=1; next};
my ($fqdn,$exp)=split ("[ t]+",$line);
next unless localdate($exp) < $month;
$list{$fqdn}=$exp;
}

for ( map {$_-> [0]}
sort {
$a-> [1] < => $b-> [1]
||
$a-> [2] cmp $b-> [2]
}
map {[$_, localdate $list{$_},$_]}
keys %list ) {
print "$_:".$list{$_}."n";
} 

Replace admin-c in multiple domains

#
# replace admin-c in multiple domains
#
#!/usr/bin/perl
use LWP::UserAgent;
use Data::Dumper;
my $ua = LWP::UserAgent->new;
my $req = HTTP::Request->new(GET => 'https://dmapi.joker.com/request/login?username='.shift().'&password='.shift());
my $res = $ua->request($req);
#--Admin-C :
my %ADMIN = ( de =>'CODE-12345' , org => 'CORG-12345', com => 'CCOM-12345', 'eu' => 'c12345' );
unless ($res->is_success) {
  print "Failed: ", $res->status_line, "\n";
  exit -1;
}
my $auth=$res->as_string;
my $output;
if ($auth =~ /Auth-Sid:\s*([a-z0-9]+)/m ) {
$auth = $1;
} else {
  print "Failed: Got no auth-id from DMAPI:\n";
  print $res->content;
  exit -3;
}
while ( <DATA> ) {
  chomp;
  my $fqdn = $_;
  ## for 3rd level domains this must be changed!
  my ( $sld, $tld ) = split ( /\./ , $fqdn );
  my $admin = $ADMIN{ $tld };
$req=HTTP::Request->new(GET => 'https://dmapi.joker.com/request/domain-modify?domain='.$fqdn.'&admin-c='.$admin.'&auth-sid='.$auth);
$res = $ua->request($req);
  if ($res->is_success) {
$output=$res->content;
     print $output;
  } else {
     print "Failed: ", $res->status_line, "\n";
     exit -2;
  }
}
__DATA__
domain1.de
domain2.eu
domain3.org
domain4.com
__END__

PHP

Introduction

List domains of a customer

<?php
 
//sends HTTP request using CURL
 
function query_host($conn_server, $params = "", $get_header = false)
{
 
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, $conn_server.$params);
    if (preg_match("/^https:\/\//i", $conn_server)) {
        curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);
        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
    }
 
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
 
    if ($get_header) {
        curl_setopt($ch, CURLOPT_HEADER, 1);
    }
 
    else {
        curl_setopt($ch, CURLOPT_HEADER, 0);
    }
 
    $result = curl_exec($ch);
 
    if (curl_errno($ch)) {
        print "curl error";
    }
 
    else {
        curl_close($ch);
    }
 
    return $result;
}
 
//builds query, sends request and gets the answer back
 
function execute_request($request, $params, &$sessid)
{
    //build the query
    $http_query = "/request/" . $request . "?" . $params   ."&auth-sid=".$sessid."&client-ip=".$_SERVER["REMOTE_ADDR"];
    //send the request
    $raw_res = query_host("https://dmapi.joker.com", $http_query, true);
    $temp_arr = @explode("\r\n\r\n", $raw_res, 2);
    //split the response for further processing
    if (is_array($temp_arr) && 2 == count($temp_arr)) {
        return $temp_arr[1];
    }
 
    else {
        return false;
    }
}
 
//basic parsing of the DMAPI header
 
function parse_response_header($header)
{
    $raw_arr = explode("\n", trim($header));
    $result = array();
    if (is_array($raw_arr)) {
        foreach ($raw_arr as $key => $value)
        {
            $keyval = array();
            if (preg_match("/^([^\s]+):\s+(.+)\s*$/", $value, $keyval)) {
                $arr[strtolower($keyval[1])] = $keyval[2];
            }
 
            else {
                print "Header line not parseable - pattern does not match\nRaw header:\n$value";
            }
        }
    }
 
    else {
        $arr = "";
        print "Unidentified error\nRaw header:\n$header";
    }
 
    return $arr;
}
 
//parses the reply from DMAPI into a header and body
function parse_response($res)
{
    $raw_arr = explode("\n\n", trim($res));
    $arr_elements = count($raw_arr);
    if ($arr_elements > 0) {
        $temp["response_header"] = parse_response_header($raw_arr["0"]);
        $temp["response_body"] = $raw_arr["1"];
    }
 
    else {
        print "Couldn't split the response into response header and response body\nRaw result:\n$res";
        $temp = "";
    }
 
return $temp;
}
 
$response = "";
$authid = "none";
//first obtaining an Auth-ID
$username = "<your username here>";
$password = "<your password here>";
$fields = "username=".urlencode($username)."&password=".urlencode($password);
$result = execute_request("login", $fields, $authid);
$result = parse_response($result);
$authid = $result["response_header"]["auth-sid"];
if (!$authid) {
    print "no auth-id was obtained - probably due to wrong username or password";
    exit;
}
 
//now asking for the domain list
$pattern = "*";
$fields = "pattern=".urlencode($pattern);
$result = execute_request("query-domain-list", $fields, $authid);
$result = parse_response($result);
 
print_r($result["response_header"]);
print "< br /> ";
print_r($result["response_body"]); 

Python

Introduction

Python is easy to use with DMAPI. Our examples are tested with python 3 on Windows and Linux, but should work on all platforms.

Running the Python example will look like:

$ ./dmapi-example.py 
Request-URL:  https://dmapi.ote.joker.com/request/login
Login: Status-Code: 0
 
Request-URL:  https://dmapi.ote.joker.com/request/query-domain-list
Domain List: Status-Code: 0
 
 domain: another-privacy-test.com
 expiration_date: 2018-06-30
 
 domain: another-privacy-test.net
 expiration_date: 2020-06-30
 
Request-URL:  https://dmapi.ote.joker.com/request/logout
Logout: Status-Code: 0

Login and list your domains

#!/usr/bin/env python
import requests
  
dmapiURL = 'https://dmapi.ote.joker.com'
dmapiUser = 'username'
dmapiPassword = 'password'
  
def main():
    loginResponse = login(dmapiUser,dmapiPassword)
    print("Login: Status-Code:", loginResponse.header['Status-Code'])
    if loginResponse.header['Status-Code'] !='0':
        print(loginResponse.header['Status-Text'])
        return
  
    sessionId = loginResponse.header['Auth-Sid'];
    print("")
    domainResponse = domainList(sessionId,1,5)
    print("Domain List: Status-Code:", domainResponse.header['Status-Code'])
    print("")
    domains = domainResponse.resultListWithNames()
    for domain in domains:
        for key, value in domain.items():
            print(" %s: %s" % (key, value))
        print("")
    logoutResponse = logout(sessionId)
    print("Logout: Status-Code:", logoutResponse.header['Status-Code'])
  
  
# implement dmapi commands as functions
def login(username,password):
    parameters = { 'username': username, 'password': password }
    message = sendCommand('login', parameters)
    return message;
  
def logout(sessionId):
    parameters = { 'auth-sid': sessionId }
    message = sendCommand('logout', parameters)
    return message;
  
def domainList(sessionId, list_from=1, list_to=""):
    parameters = { 'auth-sid': sessionId , 'from': list_from, 'to': list_to }
    message = sendCommand('query-domain-list', parameters)
    return message;
  
# general dmapi command call
def sendCommand(command,parameter={}):
    try:
        url = dmapiURL+'/request/'+command
        print("Request-URL: ", url)
        response = requests.get(url, params=parameter)
        # print URL with parameters for debugging purposes
        # print("Request-URL: ", response.url)
        if response.status_code != requests.codes.ok:
            raise CommandError("Command Failed! HTTP Status Code: %s" % response.status_code)
        return DmapiResponse(response.text)
    except requests.ConnectionError as e:
        raise CommandError("Connection Error: %s" % str(e))
    except requests.HTTPError as e:
        raise CommandError("Http Error: %s" % str(e))
    except CommandError as e:
        raise
    except Exception as e:
       raise CommandError("Unexpected Error: %s" % str(e))
  
class DmapiResponse():
    def __init__(self,responseBody):
        parts = responseBody.split("\n\n",1)
        if len(parts)>0:
            self.header = self.__parseKeyValueList(parts[0])
        if len(parts)>1:
            self.body = parts[1]
  
    def __parseKeyValueList(self,text):
        lines = text.split("\n")
        keyValueList = {}
        for line in lines:
            keyValue = line.split(' ',1)
            key = keyValue[0].rstrip(':')
            value = keyValue[1]
            keyValueList[key] = value
        return keyValueList
  
    def __getSeparator(self):
        if self.header.get('Separator') == 'TAB':
            return "\t"
        else:
            return " "
  
    def resultList(self):
        lines = self.body.split("\n")
        resultList = []
        separator = self.__getSeparator()
        for line in lines:
            values = line.split(separator)
            resultList.append(line.split(separator))
        return resultList
  
    def resultListWithNames(self):
        columnNames = self.resultListColumns()
        resultList = []
        if len(columnNames) > 0:
            rawList = self.resultList()
            resultList = []
            for row in rawList:
                columns = {}
                for idx, column in enumerate(row):
                    columns[columnNames[idx]] = column
                resultList.append(columns)
        return resultList
  
    def resultListColumns(self):
        if 'Columns' in self.header:
            columnsText = self.header['Columns']
            columns = columnsText.split(',')
            return columns
        else:
            return []
  
    def resultValues(self):
        return self.__parseKeyValueList(self.body)
  
class CommandError(Exception):
    def __init__(self, value):
        self.value = value
    def __str__(self):
        return repr(self.value)
  
# call main function
try:
    main()
except CommandError as e:
    print("Error:", str(e).strip("'"))

Login and list all A and CNAME records

#!/usr/bin/env python
import requests
 
dmapiURL = 'https://dmapi.joker.com'
dmapiUser = 'username'
dmapiPassword = 'password'
 
def main():
    loginResponse = login(dmapiUser,dmapiPassword)
    #print("Login: Status-Code:", loginResponse.header['Status-Code'])
    if loginResponse.header['Status-Code'] !='0':
        print(loginResponse.header['Status-Text'])
        return
 
    sessionId = loginResponse.header['Auth-Sid'];
    #print("")
    dnsZoneListResponse = dnsZoneList(sessionId,"")
    #print("DNS Zone List: Status-Code:", dnsZoneListResponse.header['Status-Code'])
    dnslist = dnsZoneListResponse.resultList()
    for row in dnslist:
        domain = row[0]
        expiration = row[1]
        #print(" domain: %s" % (domain))
        #print(" expiration: %s" % (expiration))
        #print("")
        dnsZoneResponse = dnsZoneGet(sessionId, domain)
        #print("DNS Zone GET for %s: Status-Code:" % (domain), dnsZoneResponse.header['Status-Code'])
        zoneEntries = dnsZoneResponse.resultList()
        for entry in zoneEntries:
            #print(' '.join(entry))
            if len(entry)<5:
                continue
            eLabel = entry[0]
            eType = entry[1]
            ePriority = entry[2]
            eTarget = entry[3]
            eTTL = entry[4]
            if eType == 'A' or eType == 'CNAME':
                print(("%s.%s\t%s" % (eLabel,domain,eTarget)).lstrip('@.'))
 
    logoutResponse = logout(sessionId)
    #print "Logout: Status-Code:", logoutResponse.header['Status-Code']
 
 
# implement dmapi commands as functions
def login(username,password):
    parameters = { 'username': username, 'password': password }
    message = sendCommand('login', parameters)
    return message;
 
def logout(sessionId):
    parameters = { 'auth-sid': sessionId }
    message = sendCommand('logout', parameters)
    return message;
 
def domainList(sessionId, pattern="", list_from=1, list_to=""):
    parameters = { 'auth-sid': sessionId , 'from': list_from, 'to': list_to, 'pattern': pattern }
    message = sendCommand('query-domain-list', parameters)
    return message;
 
def dnsZoneList(sessionId, pattern="", list_from=1, list_to=""):
    parameters = { 'auth-sid': sessionId , 'from': list_from, 'to': list_to, 'pattern': pattern }
    message = sendCommand('dns-zone-list', parameters)
    return message;
 
def dnsZoneGet(sessionId, domain):
    parameters = { 'auth-sid': sessionId , 'domain': domain }
    message = sendCommand('dns-zone-get', parameters)
    return message;
 
# general dmapi command call
def sendCommand(command,parameter={}):
    try:
        url = dmapiURL+'/request/'+command
        #print("Request-URL: ", url)
        response = requests.get(url, params=parameter)
        # print URL with parameters for debugging purposes
        # print("Request-URL: ", response.url)
        if response.status_code != requests.codes.ok:
            raise CommandError("Command Failed! HTTP Status Code: %s" % response.status_code)
        return DmapiResponse(response.text)
    except requests.ConnectionError as e:
        raise CommandError("Connection Error: %s" % str(e))
    except requests.HTTPError as e:
        raise CommandError("Http Error: %s" % str(e))
    except CommandError as e:
        raise
    except Exception as e:
       raise CommandError("Unexpected Error: %s" % str(e))
 
class DmapiResponse():
    def __init__(self,responseBody):
        parts = responseBody.split("\n\n",1)
        if len(parts)>0:
            self.header = self.__parseKeyValueList(parts[0])
        if len(parts)>1:
            self.body = parts[1]
 
    def __parseKeyValueList(self,text):
        lines = text.split("\n")
        keyValueList = {}
        for line in lines:
            keyValue = line.split(' ',1)
            key = keyValue[0].rstrip(':')
            value = keyValue[1]
            keyValueList[key] = value
        return keyValueList
 
    def __getSeparator(self):
        if self.header.get('Separator') == 'TAB':
            return "\t"
        else:
            return " "
 
    def resultList(self):
        lines = self.body.split("\n")
        resultList = []
        separator = self.__getSeparator()
        for line in lines:
            values = line.split(separator)
            resultList.append(line.split(separator))
        return resultList
 
    def resultListWithNames(self):
        columnNames = self.resultListColumns()
        resultList = []
        if len(columnNames) > 0:
            rawList = self.resultList()
            resultList = []
            for row in rawList:
                columns = {}
                for idx, column in enumerate(row):
                    columns[columnNames[idx]] = column
                resultList.append(columns)
        return resultList
 
    def resultListColumns(self):
        if 'Columns' in self.header:
            columnsText = self.header['Columns']
            columns = columnsText.split(',')
            return columns
        else:
            return []
 
    def resultValues(self):
        return self.__parseKeyValueList(self.body)
 
class CommandError(Exception):
    def __init__(self, value):
        self.value = value
    def __str__(self):
        return repr(self.value)
 
# call main function
try:
    main()
except CommandError as e:
    print("Error:", str(e).strip("'"))

C#

Applications for domain management with DMAPI are very easy to create using MS Visual Studio. This example code logs into the Joker.com system using DMAPI requests.

It provides a domain listing, whois lookup and "Email verification".

This has been tested using Visual Studio 2008 and 2010, but should work with any version, and also with free Visual Studio Express and .NET versions from 3.5 onwards. Please find the source code as an attachment below.

We also provide this as a windows binary to try without the need of building it before. In case you run Windows 10 with "Smartscreen", you have to click on "more information" to execute this, since this binray of course is not signed by a "manufacturer"...

This is how this will look like:

Email Gateway

Basics

How does the PGP/GPG-Mailinterface work?

Using the Joker.com email interface, you may send 'commands' to a special address at Joker.com by email. Those commands may consist of registration orders, domain renewals or modifications.

The Joker.com mail interface address is disclosed once you signed up as a reseller.

For security reasons, each request which is sent to the mail gateway has to be signed using PGP or GPG. This means, you need to have a pgp/gpg-installation on your machine. Some tools which can be used for this:

Emails which are not signed correctly will not be processed. All requests to the gateway have to be sent as PGP/GPG signed mails to the Joker mail-robot (you will receive the exact address if you have registered yourself as a reseller).

Mails are expected to be sent in the "traditional" format (signature is part of the message body), not (for example) in MIME encapsulated format!

The actual request (the command to be peroformed) has to be put into the subject of the email. Further details (for example the full qualified domain name) have to be put in the message body.

Example:

Subject: modify domain

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1

tld:org

sld:dummy

ns1-handle:ns1.dummy.org

ns2-handle:ns2.dummy.org

-----BEGIN PGP SIGNATURE-----

Version: GnuPG v1.0.2 (GNU/Linux)

Comment: For info see http://www.gnupg.org

iD7DBQE6ZtMfzWqd+drNYRURAuW4AJ4nRewOrNc+yLMmmCouVcMP3v5nWQCdHUlf

tJk/gOuFmDnIs3JS+7eRjnA=

=Fwmc

-----END PGP SIGNATURE-----

Where are the replies of the mail-gateway sent?

The replies of the gateway are generally sent to the "reply-to"-address. In order to specify that address, you will have to fill in the reply-to-field within the e-mails you send to the mail-gateway. 

How do I change my robot-email-address?

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mIsEPOorJQEEAJauWOOvusxn9GFEPjZnQ3x/48OfaPwSN4cIF5ezpUT6FycZQa+q
eUnNlS+bj80ULXnyyigmkUGwEtW/Qoyd55RM983pr4KtuHSMSU9gCN1syuHlDOAm
71u6irfv5RaHbJXauMCAgUKn+dBNZVZyUTm9aW2pudcwY45apF2tieTZAAYptClq
b2tlci5jb20gc2lnbmVyIHNlcnZpY2UgPGluZm9Aam9rZXIuY29tPoiyBBMBAgAc
BQI8/NifAhsDBAsHAwIDFQIDAxYCAQIeAQIXgAAKCRAm3eE0EUTiIx9RA/9HGDrD
cVM6PjZHr5jpT4svpv7xrjVRn2OIR+s80RuBAnLyAWOflqJ9342SYD8C7BMAqYm4
wXvC3/yvbQEAqsmJ5Bbq2NV+KDepahTtL8SUQ6TkOSUd9NDOvLoQWVI6o1Dz/3MG
HLJfNtx6067Sq8pP8PuYyscPyZ7/uiUilyOrqg==
=O/7Q
-----END PGP PUBLIC KEY BLOCK-----

Macros

E-mail Address

@email

This means an email address in the following format:

Valid values (.com/.net only):
foo@bar.com
foo@bar.com#1
foo@bar.com#15

Invalid values:
Hans Nase <hans@foo.com>
hans@foo.com (Hans Nase)


Valid values (.org/.info/.biz/.de/.cn only):
foo@bar.com
foo-bar@bar.com

Invalid values:
Hans Nase <hans@foo.com>
hans@foo.com (Hans Nase)
foo@bar.com#15

.com Contacts

new-handle (implicit creation of a new contact)

This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CCOM-<number>,

e.g. CCOM-176269.

ATTENTION:

The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".

If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".

If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".

If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".

There is a new request field called name within the contact definition. This field is mandatory, if you do not provide the fnamelname. You have to provide the request field name, if fname and lname are not found. This is very important for the whois output. Everytime a field person is shown. If you are using the request field name, the whois is showing the value for name, regardless the content of the request fields fname and lname. If you do not provide the request field name but your are providing the request fields fname and lname, the whois is showing the concatenation of these fields.

There is also a new request field called address-3 within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.

An existing contact (@comcont or @same-as) (.com only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:CCOM-176269
admin-contact-handle:CCOM-176229
tech-contact-handle:CCOM-176269
billing-contact-handle:CCOM-176269

In case you have entered a non-existing contact handle, the system will send you an errormail.

admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact

The @same-as makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.

Keep in mind that for .com-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

.net Contacts

new-handle (implicit creation of a new contact)

This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CNET-<number>, e.g. CNET-176269.

ATTENTION:

The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".

If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".

If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".

If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".

There is a new request field called name within the contact definition. This field is mandatory, if you do not provide the fnamelname. You have to provide the request field name, if fname and lname are not found. This is very important for the whois output. Everytime a field person is shown. If you are using the request field name, the whois is showing the value for name, regardless the content of the request fields fname and lname. If you do not provide the request field name but your are providing the request fields fname and lname, the whois is showing the concatenation of these fields.

There is also a new request field called address-3 within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.

An existing contact (@netcont or @same-as) (.net only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:CNET-176269
admin-contact-handle:CNET-176229
tech-contact-handle:CNET-176269
billing-contact-handle:CNET-176269

In case you have entered a non-existing contact handle, the system will send you an errormail.

admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact

The @same-as makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.

Keep in mind that for .net-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

.org Contacts

.info Contacts

.biz Contacts

new-handle (implicit creation of a new contact)

This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created.

ATTENTION

An existing contact (@bizcont or @same-as) (.biz only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle: CNEU-12345
admin-contact-handle: CNEU-12345
tech-contact-handle: CNEU-12345
billing-contact-handle: CNEU-12345

In case you have entered a non-existing contact handle, the system will send you an errormail.

The @same-as makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.

Keep in mind that for .biz-requests the contact handles for (.com/.net/.org/.info)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

Note that for .biz-requests the contacthandles for (.info)-contacts are not allowed. If you referencing to a shortcut like C176269-LRMS, you will get an error.

.mobi Contacts

new-handle (implicit creation of a new contact)

This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COMO-<number>, e.g. COMO-176269.

ATTENTION:

An existing contact (@mobicont or @same-as) (.mobi only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:COMO-176269
admin-contact-handle:COMO-176229
tech-contact-handle:COMO-176269
billing-contact-handle:COMO-176269

In case you have entered a non-existing contact handle, the system will send you an errormail.

The @same-as makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.

Keep in mind that for .mobi-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

.name Contacts

new-handle (implicit creation of a new contact)

This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CNAM-<number>, e.g. CNAM-176269.

ATTENTION:

There is also a new request field called address-3 within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.

An existing contact (@namecont or @same-as) (.name only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:CNAM-176269
admin-contact-handle:CNAM-176229
tech-contact-handle:CNAM-176269
billing-contact-handle:CNAM-176269

In case you have entered a non-existing contact handle, the system will send you an errormail.

The @same-as makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.

Keep in mind that for .name-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

.us Contacts

new-handle (implicit creation of a new contact)

This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COUS-<number>, e.g. COUS-176269.

ATTENTION:

An existing contact (@uscont or @same-as) (.us only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:COUS-176269
admin-contact-handle:COUS-176229
tech-contact-handle:COUS-176269
billing-contact-handle:COUS-176269

In case you have entered a non-existing contact handle, the system will send you an errormail.

The @same-as makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.

Keep in mind that for .us-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

.de Contacts

.cn Contacts

.eu Contacts

.me contacts

Nameserver

Language code

@language - one of the following language codes

DNS / URL-Forwarding

Create a dns-configuration

Introduction

With this request you can create or modify a zonefile at the joker-nameserver.

You can add A-Records, CNAME-Records, MX-Records, a nameservice-based Url-forwarding and a frame-based Url-forwarding. Modifing the TTL is not possible.

The format of this request is a little bit different from the other requests. Please check the given examples for how to specify the different zonefile-records.

ATTENTION:

You have to change the nameservers for a domain to the nameservers of joker.com first!

- a.ns.joker.com
- b.ns.joker.com
- c.ns.joker.com

If you would like to use the joker-nameservice, you will have to use all joker-nameservers.

It is not possible to use the joker-nameservice

• for primary nameservice only

• for secondarynameservice only

All joker-nameservers

• are configured to deny all zone-fetching requests!

• do not query foreign nameservers!

Request Fields

Definition of this request

Example 1: create dns-config (without url-forwarding and without wildcard-matching)

subject: create dns-config [your reference id]

domains0:hansnose.net

A:www:194.33.110.19

A:mail:194.33.110.19

A:mail2:194.33.110.20

A:@:194.33.110.10

MX:www.hansnose.net:70:mail.nrw.net

MX:www.hansnose.net:80:mail2.nrw.net

MX:@:70:mail.hansnose.net

MX:@:80:mail2.hansnose.net

CNAME:www3:some.other.domain.com

Example 2: create dns-config (with wildcard-matching)

subject: create dns-config [your reference id]

domains0:hansnose.net

A:www:194.33.110.19

A:@:194.33.110.19

A:*:194.33.110.20

Example 3: create dns-config (with dns-based url-forwarding)

subject: create dns-config [your reference id]

domains0:hansnose.net

A:www:194.33.110.19

A:@:194.33.110.19

URL:www2:http://www.sone.other.domain.com/index.html

(that means, the url within the browserbar is changing to the target address)

Example 4: create dns-config (with frame-based url-forwarding)

subject: create dns-config [your reference id]

domains0:hansnose.net

A:www:194.33.110.19

A:@:194.33.110.19

FRAME:www2:http://www.sone.other.domain.com/index.html

(that means, the url within the browserbar is not changing to the target address)

Delete a dns-configuration

List a dns-configuration

Domains

Create an order

Introduction

create <tld>-order

Valid values for <tld>: 

• com
• net
• org
• info
• biz
• mobi
• name
• us
• de
• cn
• eu
  
• xxx
  
• asia
  
• me
  

With this request you can register one or more domains.

You have to provide the following information within the request:

• domain name(s),
• owner-contact-handle,
• admin-contact-handle,
• tech-contact-handle,
• billing-contact-handle,
• nameserver information,
• additional services, if required.

You can register up to 501 domains with one request.

If you register more than one domain with a request, all domains registerd with this request will have the same contact and nameserver structure.

There are two new requestfields within this request:

• name
• address-3
  

ATTENTION

Please, refer to the table for the corresponding contact handles.

Request fields

mailsubject: create <tld>-order [your reference id]

Definition of this request

.COM order

Example 1: create com-order with implicit contact-handle-creation of the owner-contact

subject: create com-order [your reference id]

domains0:xn--hans-mller-feb.com
language0:AFR
domains1:minus-10a.com
domains2:minus-10b.com
domains3:minus-10c.com
domains4:minus-10d.com
domains5:minus-10e.com
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net

Example 2: create com-order with implicit nameserver-creation

subject: create com-order [your reference id]

domains0:minus-109.com
domains1:minus-10a.com
domains2:minus-10b.com
domains3:minus-10c.com
domains4:minus-10d.com
domains5:minus-10e.com
period:2
owner-contact-handle:CCOM-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2


Example 3: create com-order with implicit contact-handle-creation of all contacts

subject: create com-order [your reference id]

domains0:minus-109.com
domains1:minus-10a.com
domains2:minus-10b.com
domains3:minus-10c.com
domains4:minus-10d.com
domains5:minus-10e.com
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2

.NET order

Example 1: create net-order with implicit contact-handle-creation of the owner-contact

subject: create net-order [your reference id]

domains0:xn--hans-mller-feb.net
language0:AFR
domains1:minus-10a.net
domains2:minus-10b.net
domains3:minus-10c.net
domains4:minus-10d.net
domains5:minus-10e.net
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net


Example 2: create net-order with implicit nameserver-creation

subject: create net-order [your reference id]

domains0:minus-109.net
domains1:minus-10a.net
domains2:minus-10b.net
domains3:minus-10c.net
domains4:minus-10d.net
domains5:minus-10e.net
period:2
owner-contact-handle:CCOM-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2


Example 3: create net-order with implicit contact-handle-creation of all contacts

subject: create net-order [your reference id]

domains0:minus-109.net
domains1:minus-10a.net
domains2:minus-10b.net
domains3:minus-10c.net
domains4:minus-10d.net
domains5:minus-10e.net
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2

.ORG order

Example 1: create org-order with implicit contact-handle-creation of the owner-contact

subject: create org-order [your reference id]

domains0:xn--hans-mller-feb.org
language0:AFR
domains1:minus-10a.org
domains2:minus-10b.org
domains3:minus-10c.org
domains4:minus-10d.org
domains5:minus-10e.org
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CORG-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net


Example 2: create org-order with implicit nameserver-creation

subject: create org-order [your reference id]

domains0:minus-109.org
domains1:minus-10a.org
domains2:minus-10b.org
domains3:minus-10c.org
domains4:minus-10d.org
domains5:minus-10e.org
period:2
owner-contact-handle:CORG-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CORG-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2


Example 3: create org-order with implicit contact-handle-creation of all contacts

subject: create org-order [your reference id]

domains0:minus-109.org
domains1:minus-10a.org
domains2:minus-10b.org
domains3:minus-10c.org
domains4:minus-10d.org
domains5:minus-10e.org
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2