Ingesting Raw Data

This endpoint should be used, when you are not in control of the request body, such as in the case of calling LogScale via a callback from another system.

http
POST /api/v1/ingest/raw

The body of the HTTP request will be interpreted as a single event, and parsed using the parser attached to the accompanying ingest token. Unless the parser created generates a @timestamp field, the @timestamp of the resulting event will equal @ingesttimestamp.

Note

This endpoint is not suited for ingesting a large number of events, and its usage should be restricted to relatively infrequent calls.

Example

When ingesting raw data, you can choose to authenticate by attaching your ingest token to the header:

Show:
shell
curl -v -X POST $YOUR_LOGSCALE_URL/api/v1/ingest/raw \
    -H "Authorization: Bearer $INGEST_TOKEN" \
    -d 'My raw Message generated at "2016-06-06T12:00:00+02:00"'
Show:
shell
curl -v -X POST $YOUR_LOGSCALE_URL/api/v1/ingest/raw/$INGEST_TOKEN \
    -d 'My raw Message generated at "2016-06-06T12:00:00+02:00"'

Important

When passing the ingest token as part of the URL, the token should not be considered as secret, as it may be logged in LogScale or in any proxy servers which process the request. Thus, CrowdStrike strongly recommends that you authenticate through the request header if possible.