Reference

calendar_reauth_required

The stored calendar credential no longer works. The customer has to reconnect.

401HTTP 401 · Calendar Reauth Required

What it means

The stored calendar credential no longer works. The customer has to reconnect.

Do not retry

The identical request will fail the same way every time. Change it first.

What causes it

  • The refresh token was revoked — a password change or an access review will do it.
  • The grant expired, or the workspace admin removed the app.

How to fix it

  • Reconnect the calendar in the dashboard. Nothing else clears this.
  • Do not retry. A revoked token is just as revoked in thirty seconds, and retrying only delays telling the customer the one thing that fixes it.
  • Surface this one in your own UI rather than logging it — it needs a person.

What the response looks like

401 application/problem+json
{
  "error": {
    "code": "calendar_reauth_required",
    "message": "The stored calendar credential no longer works. The customer has to reconnect",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/calendar_reauth_required",
  "title": "Calendar Reauth Required",
  "status": 401,
  "detail": "The stored calendar credential no longer works. The customer has to reconnect",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Still stuck

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.

Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.

Building on it? Start on the free plan — no card — and call the same API the dashboard uses.

Start free