Supports batch creation of events.
Dataset names are case insensitive. POST requests to “MyDatasET” will land in the same dataset as “mydataset”. Names may contain URL-encoded spaces or other special characters, but not URL-encoded slashes. For example, “My%20Dataset” will show up in the UI as “My Dataset”.
The first event received for a dataset determines the casing of the displayed name. All subsequent variations in casing will use the originally specified case.
A Honeycomb Configuration Key is required to use this API. A Configuration Key can be found in the API Keys section of the environment configuration, which can be found under Environment Settings -> API Keys -> Configuration tab. Check out our documentation to find your API Keys.
More information can be found in Manage Environments.
Included when sending events in a file. Size limitations may be addressed by compressing request bodies with gzip or zstd compression. Be sure to set the Content-Encoding to gzip or zstd when compressing the request body. If sending plaintext, omit this header; "plaintext" is included to simplify the example with curl.
gzip, zstd The dataset slug.
The array should contain one or more JSON objects representing Events. Each Event contains its payload under the data key. Values of time and/or samplerate can be included as well.
The JSON payload should have the structure:
[{ "data": { "key1": "value1", "key2": 2.0 } }, ... ]
Size limitations may be addressed by compressing request bodies with gzip or zstd compression.
An empty 202 response indicates that the event has been queued for processing.
Should be in RFC3339 high precision format (for example, YYYY-MM-DDTHH:MM:SS.mmmZ). May be a Unix epoch (seconds since 1970) with second or greater precision (for example, 1452759330927). Optional. If not set, defaults to the time that the API receives the event.