There are various ways to bring your data into Treasure Data. Depending on the format of your data, or the languages you are using, you might consider several options.

If no solution is found in the client libraries, you might need to write a client for one of the following APIs that corresponds to the programming language or data format you are using.

There are several Public Import APIs available in each region. The API you use will depend on your data format and the sites and endpoints for your region.

This topic contains:

Determine Your Import API Method

  1. Select your data format from one of the following.


    You can use the Treasure Data Import API if you have batches of data in gzipped msgpack format or you are using fluentd. This API is also known as the "Stream Import" API, and uses api-import subdomain.

    Most client libraries — as well as td-agent, td toolbelt, and fluentd collector daemon — use this API.


    You can use the Postback API if you have small batches of JSON format data. This API is also known as the "JS/ Mobile SDK/ Postback" API and uses the in subdomain. It expects frequent, small payloads. The JavaScript, Android and iOS SDKS use this API.

    Other External Systems or Formats

    If your data is held by a third party, accessed by API or via file export, you can use the Treasure Data Bulk Import API. This API combines the api subdomain and v3/bulk_import/* paths. Treasure Data’s embulk-based integrations use this API. Learn more about Treasure Data’s powerful integrations.

  2. Choose the appropriate URL from a list of Sites and Endpoints.

  • No labels