Send Data

Send (ingest), transport, and fetch data from different sources such as Relational database, web logs, batch data, real-time, application logs, streaming data, etc. for later usage with the Axiom API.

You can also collect, load, group, and move data from one or more sources to Axiom where it can be stored and further analyzed.

Before ingesting data, you need to generate an API Token from the Settings->Tokens page on the Axiom Dashboard. See API Tokens documentation for more detail.

Once you have an API token, there are different ways to get your data into Axiom:

  1. Using the Ingest API;
  2. Using a Data Shipper (Logstash, Filebeat, Metricbeat, Fluentd, etc.);
  3. Using the Elasticsearch Bulk API that Axiom supports natively.
  4. Using the Integrations we support
  5. Using Endpoints

Ingest API

Axiom exports a simple REST API that can accept any of the following formats:

Ingest using JSON

  • application/json - single event or json array of events


curl -X 'POST' '$DATASET_NAME/ingest' \
  -H 'Authorization: Bearer $API_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '[
            "tags": {
                "server": "aws",
                "source": "wordpress"

Ingest using NDJSON

  • application/nd-json- structured data processed at a time


curl -X 'POST' '$DATASET_NAME/ingest' \
  -H 'Authorization: Bearer $API_TOKEN' \
  -H 'Content-Type: application/x-ndjson' \
  -d '{"id":1,"name":"machala"}
  {"index": {"_index": "products"}}
  {"timestamp": "2016-06-06T12:00:00+02:00", "attributes": {"key1": "value1","key2": "value2"}}
  {"queryString": "count()"}'

Ingest using CSV

  • text/csv - this should include the header line with field names separated by commas


curl -X 'POST' '$DATASET_NAME/ingest' \
      -H 'Authorization: Bearer $API_TOKEN' \
      -H 'Content-Type: text/csv' \
      -d 'user, name
         foo, bar'

Supported Libraries

If you would like to instead use a language binding, currently our client libraries are available:


Maximum Event Batch Size1000
Maximum Event Fields250
Maximum Array Field Items100

Field Restrictions

There are some restrictions on the field names in Axiom:

  • Field names should not be more than 200 bytes.

  • It must be a valid UTF-8.

timestamp field

  • _time must conform to a valid timestamp or not be present at all. If _time is not present, the server will assign a timestamp. Axiom accepts many date strings and timestamps without knowing the format in advance, including Unix Epoch, RFC3339, and ISO 8601.

Data Shippers

Configure, read, collect, and send logs to your Axiom deployment using a variety of data shippers. Data shippers are lightweight agents that acquire logs and metrics enabling you to ship data directly into Axiom.

integrations iconAWS CloudFrontgo
integrations iconAWS CloudWatch Logsgo
integrations iconElastic Beatsgo
integrations iconFluent Bitgo
integrations iconFluentDgo
integrations iconHeroku Log Drainsgo
integrations iconKubernetesgo
integrations iconLogstashgo
integrations iconLoki Multiplexergo
integrations iconSyslog Proxygo
integrations iconVectorgo


Send logs and metrics from Vercel, Netlify, and other supported integrations we support.

CloudFront overview

Get started with integrations here


Endpoints enable you to easily integrate Axiom into your existing data flow by allowing you to use tools and libraries that you are already familiar with.

You can create an Endpoint for your favorite services like HoneyComb, Jaeger, Grafana Loki, or Splunk and eventually send the logs from these Services directly into Axiom.

CloudFront overview

Get started with endpoints here

Was this page helpful?