You are here: Home > Manage IPs and ASNs > RIPE Database > Syncupdates

Synchronous Updates in the RIPE Database

Synchronous Updates, or Syncupdates, is a way to interact with the RIPE Database directly over HTTPS and get an immediate result. It supports queries and updates and allows you to submit multiple objects in a single update.

For quick access, you can use the Syncupdates web form (requires authentication). When setting up a script or application to interact with the RIPE Database over HTTPS, use this URL: https://syncupdates.db.ripe.net

Syncupdates accepts the following parameters (query params for GET, form params for POST):

  • DATA
    This variable should contain the actual update message.
  • NEW
    This variable can be either yes or no. If it contains yes, the update will fail if it contains changes to existing objects.
  • HELP
    This variable can be either yes or no. If it contains yes, the help message of the whois server will be given as the output.

Multiple objects are accepted in the body, and any required passwords must also be supplied in the body using the “password:” attribute. When using the web form, your SSO account can be used for authentication.

After composing the input and sending it as a POST or a GET request, the server will return the usual http response headers and the body if an acknowledgement exists.

The first line of the response will give the result of the transaction, in the form of:

HTTP/1.1 (code) (message)

where (code) is a three-digit number which is a code for the message. The first digit of the code denotes the type of message. The rest of the digits are unique for all messages:

  • 2XX denotes a successful transaction
  • 4XX denotes that the request could not be understood by the server due to malformed syntax

If the code begins with 2, there will be an acknowledgement in the body of the response, in the form of text/plain.

These are the actual codes returned by Syncupdates:

  • 200 OK (successful)
  • 400 Bad Request (invalid HTTP request, URL or parameters)

Examples of GET requests:

curl -4 -v -d "HELP=yes" https://syncupdates.db.ripe.net
curl -4 -v https://syncupdates.db.ripe.net/?HELP=yes

Example of a POST request:

curl -v -4 -X POST -H "Content-Type: multipart/form-data; boundary=--------------------------466af99a9520" --data-binary @form.txt https://syncupdates.db.ripe.net

----------------------------466af99a9520
Content-Disposition: form-data; name="DATA"

organisation:   ORG-TS1-TEST
org-name:       RIPE NCC Training Services
org-type:       LIR
address:        Singel 258, 1016 AB Amsterdam
phone:          +31205354444
fax-no:         +31205354444
e-mail:         training _at_ example _dot_ org
admin-c:        TS1-TEST
tech-c:         TS1-TEST
abuse-c:        AA2-TEST
ref-nfy:        auto _at_ example _dot_ net
notify:         xnotify _at_ example _dot_ org
mnt-ref:        TEST-DBM-MNT
mnt-by:         TEST-DBM-MNT
source:         TEST
password:   some clear text
----------------------------466af99a9520--