Tokens are used to identify data when it’s sent to and are used in at least 2 primary contexts.

These tokens are actually cryptographically signed payloads that identify the stream and cluster the data is for.

Tokens for streams can be viewed in two different places:

  • Within the UI, in the Token section under the Stream Manage page
  • In the output of current streams

It’s important that the token be treated as a secret value. Anyone with this token can send data to your stream, so you should store it alongside other sensitive information.


Tokens are primarily provided in 3 ways:

  • When sending data via syslog. The token is included with each syslog message to identify which stream it belongs to.
  • When sending data via current send -t. Using this allows sites to distribute the token to their servers without having to to distribute github authentication information normally used with current send
  • When sending data via Logplex. This HTTP based method is used by the Heroku integration and the token is provided as the password of the HTTP Basic Auth encoded username/password in the Authorization header.


In the future, multiple tokens as well as token rotation will be available.