How do I get a new connector token without relinking?

You don't need a new one. A connector token doesn't expire or change, and it stays the same when a connector is relinked. If calls with one token start failing, the cause is almost always the request or the customer's credentials, not the token.

If requests with one connector token fail

Match the error you're getting:

Every call returns 401

Cause: the API key is missing, malformed, or belongs to the other environment. Fix: check that the header reads Authorization: Bearer <BINDBEE_API_KEY> with a single space, and that the key matches the connector's environment.

Calls return 403

Cause: the token is being used against a different API category, such as an HRIS token on an ATS endpoint. Fix: call the endpoint for the connector's own category.

The connector shows Relink Needed

Cause: your customer's credentials in their HR system have expired or changed. Fix: relink the existing connector. The connector token stays the same after the relink. See "How do I fix a connector that shows 'Relink Needed'?".

A call fails once while other connectors work

Cause: a temporary error. Fix: retry the request. If it keeps failing, send us the full request you're making (with your API key and token removed) and we'll trace it.

When you do need a new token

A new connector token only comes from a new connector, which means your customer goes through the connection flow again and every record gets a new Bindbee ID. Relinking the existing connector is the better option whenever the credentials have changed.