Skip to main content
Create a Public API key in Settings → API with line:send. Add line:read to query receipts. Existing keys do not gain either permission automatically. The organization must have a configured LINE channel and an enabled LINE module. The recipient must be an organization contact with exactly one linked personal LINE account that follows the official account. Missing links, unfollowed accounts and multiple active links return 409 resource_state_conflict with a reason in error.details.reason. Group messages are not supported.

Send text

This operation sends a real LINE message. Use the authorized recipient and text, with a unique, nonsecret Idempotency-Key for each intended send.
Text is sent literally, without Automation template expansion. The limit is 5000 UTF-16 code units; some emoji count as two units. LINE user IDs, channel credentials, organization IDs and arbitrary recipient overrides are not accepted. A 201 creates a send receipt. Always inspect status:

Query and retry

Replace the path ID with the send response’s id. This reads receipts created by the Public API or MCP, not inbox history. Messages also appear in the CRM LINE inbox. Repeating the same Idempotency-Key and body returns the same receipt’s current status with Idempotency-Replayed: true, without another send. A different body using the same key returns 409 idempotency_conflict. These receipts do not expire; deleting an inbox message or contact does not allow another send. After one minute, preparation that never started dispatch is failed with dispatch_not_started and cannot send later. A started dispatch without a recorded outcome is unknown. LINE HTTP 429 (rate limit or monthly quota) is a definite refusal: failed with provider_rejected. Wait for the limit to clear or resolve the quota, then use a new key. A timeout or provider 5xx remains unknown.

MCP

Use brightalk_send_line_message with:
Use brightalk_get_line_message with { "message_id": "the returned id" } to read the result. Read-only mode hides the send tool. Enable action mode and provide a key with line:send to send messages.

Conflict reasons

A 409 resource_state_conflict includes error.details.reason. These conflicts occur before a receipt is claimed, so correct the cause and retry with the same key.