Honeybadger

​

🚀 Quickstart

curl "https://api.nango.dev/proxy/v2/projects" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"

import { Nango } from '@nangohq/node';

const nango = new Nango({ apiKey: '<NANGO-API-KEY>' });

const res = await nango.get({
    endpoint: '/v2/projects',
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>'
});

console.log(res.data);

​

📚 Honeybadger integration guides

• How do I link my account?
  Find your region, copy your personal auth token and connect it in the Connect UI.

​

🧩 Pre-built syncs & actions for Honeybadger

​

API gotchas

• Call only API v2 endpoints (/v2/...) with this connection: the v2 personal auth token does not work with API v3 (/v3/...), which refuses HTTP Basic with 401 unsupported_auth_scheme and needs a Bearer user or account API token. See Authentication.
• Set the region connection config field to the host the account signs in to: app.honeybadger.io for the US region, eu-app.honeybadger.io for the EU region. EU accounts are separate accounts from US ones. See Data residency.
• Check X-RateLimit-Remaining when a call answers 403: after 360 requests per hour, the API answers 403 (Forbidden) instead of 429, the same status it uses for a permissions problem. X-RateLimit-Reset is the Unix timestamp in seconds when the counter resets. See Data API.
• Read the error reason from the errors field: failed calls answer { "errors": "Reason for error" }, with 403 for a permissions problem and 422 for an invalid request. See Data API.
• Do not parse a body from a successful PUT: updates answer 204 with no response body, while POST creations answer 201 with the created resource. See Data API.