Skip to main content
GET
Status / info
Auth: TokenAccount or TokenInstanceRate limit: Global (100/min) • Idempotent: yes

Description

Returns the local status of the Chatwoot integration and complements it with the current state (best-effort). This response includes the chatwoot_api_token in plaintext and the behaviour flags (sign_messages, ignore_groups, start_as_pending, reopen_resolved).

Example

Success response

200 OK
The chatwoot_api_token is returned in plaintext in this response (it is stored encrypted at rest). Since this token usually has broad access to the Chatwoot account, treat the response as sensitive: avoid logging it or caching it on the client.
The sign_messages / ignore_groups / start_as_pending / reopen_resolved flags are persisted locally and reflect the last set. They are always returned, including as false.

Path parameters

string
required
Instance name (e.g., suporte).

Headers

string
required
TokenAccount or TokenInstance.

Behavior

1

Read local data

Queries the chatwoot_integrations table. This step is fast and always works.
2

Complement with the current state (best-effort)

RyzeAPI tries to fetch the current state of the integration with a 10s timeout. On network failure, it falls back to local data.
3

Overwrite volatile fields

When the current state is available, status and last_error are replaced with the live values.
4

Backfill of inbox_id

If the inbox_id became available and the local one is still 0, the database is updated (SetInboxID), useful for eventual-consistency cases right after set.

Errors

If last_error is non-empty, inspect the message, it usually indicates that Chatwoot dropped the session (token rotated, inbox manually removed, etc.). Reactivating with POST /api/chatwoot/set/:instance usually fixes it.

Next

Reactivate / update

Use POST /api/chatwoot/set/:instance to fix credentials or flags.

Deactivate

Remove the integration.