Archive

Please note that the only data access to data stored in the Archive layer is via s3 file access, typically by specifying files as the file for a call to publish.

/write

Save data to the archive.

• rights: publish
• verbs: POST

Parameter	Type	Required
items	JSON map[]	Yes. Each item must be a JSON map that can contain arbitrary keys and structure.
publish	boolean	No. When true, will attempt to publish data to the data lake after archiving it.
async	boolean	No. Default true. Set to false to receive synchronous error messages in a debugging context.
rules	TransformRuleSet	No. Used only when publish is true.

curl

curl https://test-m1.minusonedb.com/write \
-d 'items=[{"property1" : {"ip" : "127.0.0.1"}, "session" : null, "event": {"id": "key98765", "time": 946702800, "type": "sessionStart"}}]&publish=true' \
-H "m1-auth-token: $myToken"

m1 client

m1 test-m1 write \
-items '[{"property1":{"ip":"127.0.0.1"},"session":null,"event":{"id":"key98765","time":946702800,"type":"sessionStart"}}]' \
-publish true

No response when successful.

In a production setting, if you are publishing data immediately after archiving, we recommend you set publish-permissive to true.

Each archived item will have the origin ip address and reception time appended to it. See property-ip and property-received system parameter documentation for more details.

When geo is enabled, geographic metadata will be appended to each item based on the available ip address.