Tracking deploys

Honeybadger can keep track of application deployments, and link errors to the version which the error occurred in. Here’s a simple curl script to record a deployment:

HONEYBADGER_ENV="production" \
HONEYBADGER_REVISION="$(git rev-parse HEAD)" \
HONEYBADGER_REPOSITORY="$(git config --get remote.origin.url)" \
HONEYBADGER_API_KEY="Your project API key" \
  && curl -g "https://api.honeybadger.io/v1/deploys?deploy[environment]=$HONEYBADGER_ENV&deploy[local_username]=$USER&deploy[revision]=$HONEYBADGER_REVISION&deploy[repository]=$HONEYBADGER_REPOSITORY&api_key=$HONEYBADGER_API_KEY"

Be sure that the same revision is also configured in the honeybadger-js library. Read more about deploy tracking in the API docs.

If you are using our EU stack, you should use eu-api.honeybadger.io instead of api.honeybadger.io for the curl command.

Tracking deploys from Laravel Forge

If you are deploying your site with Laravel Forge, you can notify Honeybadger of deployments via Deployment Notifications. Use this format for your webhook URL:

https://api.honeybadger.io/v1/deploys/forge?api_key=YOUR_HONEYBADGER_API_KEY_HERE&environment=production

If you are using our EU stack, you should use eu-api.honeybadger.io instead of api.honeybadger.io in the webhook URL.

Deploying with GitHub Actions

If your CI/CD pipeline is hosted with GitHub Actions, you can use the Honeybadger Deploy Action to notify our API about deployments.