> ## Documentation Index > Fetch the complete documentation index at: https://help.texterchat.com/llms.txt > Use this file to discover all available pages before exploring further. # List Channel Health Problems > Retrieve a list of current channel health problems. You can filter by severity, account, or channel, and optionally include already-resolved problems. Useful for monitoring system health and diagnosing issues that may affect messaging performance. **Required token scopes:** none - any valid API token works Problems are sorted by `createdAt` in ascending order. ## OpenAPI ````yaml he/api-reference/openapi.json GET /channels/health/problems openapi: 3.1.0 info: title: Texter API V2 version: 2.0.0 description: >- The **Texter API** lets your developers control the Texter platform programmatically: - Manage and send your WhatsApp template messages - Retrieve chats by ID or by various filters - Assign and resolve conversations - Send session messages into active chats - Manage labels - Monitor and resolve channel health issues - Subscribe to real-time webhook events - Manage quick replies (coming soon) For any questions please contact [Texter Support](https://wa.me/972586640430). contact: name: Texter Support url: https://wa.me/972586640430 servers: - url: https://{projectID}.texterchat.com/server/api/v2 description: Your Texter environment. Replace projectID with your project subdomain variables: projectID: default: demo description: >- Your unique project subdomain. If your environment URL is https://demo.texterchat.com, your projectID is "demo" security: - bearerAuth: [] tags: - name: Manage Templates description: >- Create, localize, submit, update, delete and send WhatsApp template messages, and retrieve approved templates for your connected WhatsApp accounts. **Suggested token for this group** - create one API token with the scopes: *Send template messages*, *View template messages*, *Manage WhatsApp templates*, *Manage all chats*, *List all chats* (the last two also cover the Templates Subscriptions group). Each endpoint below also lists the exact scopes it needs. - name: Templates Subscriptions description: >- Manage recipient subscriptions for WhatsApp template messages - unsubscribe or resubscribe recipients, and list unsubscribed users across all channels or for a specific account. **Suggested token for this group** - scopes: *Manage all chats*, *List all chats*. Each endpoint below also lists the exact scopes it needs. - name: Messages description: >- Retrieve message history from a chat, or send new session messages - text, media, buttons, lists, contact cards and locations - within the active WhatsApp 24-hour session window. **Suggested token for this group** - scopes: *Send session message*, *View all chats*. Each endpoint below also lists the exact scopes it needs. - name: Chats description: >- Fetch chat details, search conversations, update chat properties, assign or resolve chats, and manage their CRM metadata. **Suggested token for this group** - scopes: *Manage all chats*, *List all chats*, *Send session message*. Each endpoint below also lists the exact scopes it needs. - name: Labels description: >- Create and edit labels, assign or remove them from chats, retrieve label data, or delete labels from your inbox. **Suggested token for this group** - scopes: *Manage labels*, *Manage all chats* (needed for managing labels on chats). Each endpoint below also lists the exact scopes it needs. - name: Channels description: >- Monitor and maintain the health of connected messaging channels - retrieve active channel health problems, filter them by severity or account, and mark issues as resolved. **Suggested token for this group** - scopes: *Manage channels*. Each endpoint below also lists the exact scopes it needs. - name: Quick Replies description: >- Manage quick replies - prepared messages agents can send into matching chats with one click. Quick replies marked with `aiQuickReply` client metadata appear as **AI suggestions** in the Texter inbox (see Create Quick Reply for the full flow). **Suggested token for this group** - scopes: *View quick replies*, *Manage quick replies*. Each endpoint below also lists the exact scopes it needs. - name: Files description: >- Generate public access links to media files stored in Texter. **Suggested token for this group** - scopes: *View all files*, *View all chats* (both required). Each endpoint below also lists the exact scopes it needs. - name: Subscribe to Events description: >- Register webhooks for events occurring in your Texter environment. Under the hood this uses **Scenarios** - a workflow automation feature within Texter. To make integration easy, pre-defined templates are provided: import a scenario JSON, plug in your webhook URL and user UID, and the subscription is active. See the **Webhook Events** pages for the payload your URL receives for each event. **Suggested token for this group** - scopes: *View scenarios*, *Create scenarios*, *Delete scenarios*, *Activate/inactivate scenarios*, *Manage scenarios on behalf of user*. Each endpoint below also lists the exact scopes it needs. If the provided templates don't satisfy your needs, contact [Texter Support](https://wa.me/972586640430) and we'll gladly help modify any triggers, conditions or actions for your webhook. - name: Scenarios (Advanced) description: >- Full programmatic control over scenarios for advanced automations: create scenarios from scratch, copy them, edit drafts, publish revisions, inspect execution runs, and discover the available building blocks (events, conditions, loaders, actions). For plain webhook subscriptions, the **Subscribe to Events** group with its ready-made templates is the simpler path. **Suggested token for this group** - scopes: *View scenarios*, *Create scenarios*, *Edit scenarios*, *Delete scenarios*, *Activate/inactivate scenarios*, *Manage scenarios on behalf of user*, *View scenarios runs*. Each endpoint below also lists the exact scopes it needs. paths: /channels/health/problems: get: tags: - Channels summary: List Channel Health Problems description: >- Retrieve a list of current channel health problems. You can filter by severity, account, or channel, and optionally include already-resolved problems. Useful for monitoring system health and diagnosing issues that may affect messaging performance. **Required token scopes:** none - any valid API token works Problems are sorted by `createdAt` in ascending order. operationId: list-channel-health-problems parameters: - name: includeResolved in: query schema: type: string enum: - 'true' - 'false' description: Also include already-resolved problem records - name: severity in: query schema: type: string enum: - warning - error description: Filter by problem severity - name: accountId in: query schema: type: string description: Affected channel account ID - name: channel in: query schema: type: string enum: - whatsapp - messenger - instagram - website_chat - email description: Channel type name - name: skip in: query schema: type: string description: How many results to skip - name: limit in: query schema: type: string description: Maximum results to return responses: '200': description: >- The matching problems and total count. Field-by-field reference: [The Problem object](/he/api-reference/objects/problem) content: application/json: schema: type: object properties: total: type: number problems: type: array items: $ref: '#/components/schemas/Problem' example: total: 1 problems: - _id: 68be7a16475a76a869de5987 accountId: '972509876543' channel: whatsapp createdAt: 1757313558371 impairedFunctionality: send: false receive: false message: WhatsApp app ID is not set name: whatsapp_app_id_error severity: error '400': description: Invalid query content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: data/channel must be equal to one of the allowed values '401': description: Missing or invalid token x-codeSamples: - lang: bash label: All active problems source: >- curl -g "https://YOUR_PROJECT.texterchat.com/server/api/v2/channels/health/problems" \ -H "Authorization: Bearer YOUR_API_TOKEN" - lang: bash label: Errors only source: >- curl -g "https://YOUR_PROJECT.texterchat.com/server/api/v2/channels/health/problems?severity=error" \ -H "Authorization: Bearer YOUR_API_TOKEN" - lang: bash label: One account, incl. resolved history source: >- curl -g "https://YOUR_PROJECT.texterchat.com/server/api/v2/channels/health/problems?accountId=972586640430&includeResolved=true" \ -H "Authorization: Bearer YOUR_API_TOKEN" - lang: bash label: WhatsApp only source: >- curl -g "https://YOUR_PROJECT.texterchat.com/server/api/v2/channels/health/problems?channel=whatsapp" \ -H "Authorization: Bearer YOUR_API_TOKEN" components: schemas: Problem: type: object description: A channel health problem record properties: _id: type: string description: Unique ID of this problem record in Texter example: 68cc1241bafffd81d455e788 channel: type: string enum: - whatsapp - messenger - instagram - website_chat - email - sms description: Messaging channel type accountId: type: string description: >- The account ID in Texter affected by this issue (same ID you see under `chatChannelInfo.accountId` in messages) name: type: string description: Machine-readable problem code (stable identifier for the issue type) example: whatsapp_business_has_limited_messaging_availability caseId: type: string description: >- Provider / Meta case reference, if available. Two problems with the same `name` + `caseId` are considered the same ongoing incident severity: type: string enum: - error - warning description: How severe the issue is impairedFunctionality: type: object additionalProperties: type: boolean description: >- Which capabilities are impacted for this account. `true` = impacted. For WhatsApp you mainly see `send` and `receive`; other channel feature keys (e.g. `attachments`, `templates`) can appear example: send: true receive: false message: type: string description: Human-readable explanation of the issue instruction: type: string description: Recommended remediation. Not present on all problems createdAt: type: number description: When this problem record was created (epoch ms) startedAt: type: number description: >- When the issue actually started affecting the account, if known. Can be earlier than `createdAt` resolvedAt: type: number description: When the issue was resolved. If missing, the problem is still active ErrorResponse: type: object properties: error: type: string description: Human-readable error message required: - error securitySchemes: bearerAuth: type: http scheme: bearer description: >- API token generated in Texter: gear icon → Developers → API Tokens. When creating a token, assign it the scopes required by the endpoints you plan to call - each endpoint lists its required scopes. ````