# FAQ¶

## How do I create an access token to post data to Observe?¶

You can do this with a curl command like the following:

$curl -s \ https://${OBSERVE_CUSTOMER}.observeinc.com/v1/login/ingestToken -d \


Where OBSERVE_CUSTOMER is your numeric Customer ID (in this example, from an environment variable.) The response looks like this:

{
"ok":true,
"access_key":"Ga21uay2vAGrzxfZHgJN4gNhuCBC9oKD",
"expiration":"2021-04-03 20:08:39",
"tokenName":"collect-you@your-company.com-2020-02-28"
}


You can also contact your Observe account manager and they will be happy to generate a token for you that will be sent to you via email.

## How do I easily post some data to Observe?¶

Easiest is to use some supported existing collector, like those for fluentd, filebeat, or prometheus. If you want to post some JSON to Observe, you can make an access token, and then post an array of JSON payloads to the https endpoint. The path after the endpoint bit will show up as the path attribute of your collected observations:

$curl -s \ https://collect.observeinc.com/v1/http/your-path-here \ -H 'Authorization: Bearer${OBSERVE_CUSTOMER} ${OBSERVE_TOKEN}' \ -H 'Content-type: application/json' -d '[{"foo":"bar"}]'  Note that the Authorization header needs the token Bearer followed by both your customer ID, and the access token, separated by a space. ## How do I create an access token that can do more than just ingest data?¶ You can do this with curl: $ curl -s \

Note that the curl URL in this case is /v1/login not /v1/login/ingestToken