For Developers

Automate your conversions using the RebaseData API

Get started

Our universal database conversion API allows to convert a wide variety of database formats into certain output formats. If you need support or you have feedback, don't hesitate to contact us.

Our API is located at https://www.rebasedata.com/api/v1/convert . The API is only accessible via HTTPS.

Authentication

RebaseData allows to convert most of the databases for free. In order to convert the other databases, you need to become a customer. As a customer, you can specify your customerKey as query string parameter.

Request

You specify the files you want to convert in the body of HTTP-POST requests. You should use the multipart-form-data encoding. The variable to use for one or multiple files is files[] . For a list of supported input files, please see our converters. Be aware that files are recognized by their extension.

By appending the query string variable outputFormat , you can specify different output formats. Currently, we support the following output formats:

  • csv (default; for each table, a .CSV file is returned)
  • xlsx (for each table, a .XLSX file is returned)
  • mysql (one mysqldump file with all the tables is returned)
  • sqlite (one sqlite database file with all the tables is returned)

By appending the errorResponse query string variable, you can choose between different responses in case the conversion failed:

  • json (default; the response will be a JSON structure containing an error key)
  • zip (the response will be a ZIP archive which contains an error.txt file that contains the error message)

Response

In case the conversion succeeded, the Content-Type header of the response will be application/zip . The body of the response will have be a ZIP-archive that contains the output files.

In case the conversion failed and the parameter errorResponse was not specified or json, the Content-Type header of the response will be application/json . The response will be a JSON structure with a key error that specifies the error message.

In case the conversion failed and the parameter errorResponse was zip, the Content-Type header of the response will be application/zip . The response will be a ZIP archive with a file error.txt containing the error message.