LINE Push Returns 200 but No Message? Check Recipient Eligibility
A LINE Messaging API push request can return HTTP 200 even when the user will not receive the message. LINE explicitly lists deleted accounts, users who blocked the sending Official Account, and non-friends outside the documented exception. Before sending again, verify the sending channel, recipient ID, and recipient’s relationship with that account. A successful HTTP response is not proof of recipient delivery—or proof that someone blocked you.
Key takeaways
- Diagnose the actual push request, not your webhook server’s HTTP response.
- A non-friend who messaged the Official Account in a one-to-one chat can receive push messages within seven days of that message.
- That exception is not a general sending window for every visitor, group participant, or website login.
- Stop automatic resends after a known success; investigate eligibility and preserve delivery uncertainty.
Why LINE push can succeed without being received
The LINE Messaging API reference lists three conditions for push sending:
| Destination | Documented condition |
|---|---|
| Individual user | Has added the sending LINE Official Account as a friend |
| Group or multi-person chat | The Official Account has joined that chat |
| Individual non-friend | Sent a message to that Official Account in a one-to-one chat within the preceding seven days |
The same reference warns that 200 can be returned without delivery when the user deleted their LINE account, blocked the sending Official Account, or has not added it as a friend and does not qualify for the exception.
These are possible explanations, not a diagnosis encoded in the success response. Do not add a “customer blocked us” badge merely because a user reports a missing message. Also keep the conditions destination-specific: a group interaction is not evidence of a qualifying one-to-one message.
For delayed support work, record the relevant incoming-message time separately from job creation and dispatch time. As a recommended application safeguard, evaluate the non-friend condition again when dispatching. Starting an AI task while the condition holds does not reserve future sending eligibility.
Inspect one send from channel to recipient
Use a single operation as the unit of investigation. These are recommended diagnostic records, not additional LINE API fields.
1. Locate the response that actually matters
Confirm that the 200 came from the outbound push request. A successful webhook acknowledgement only describes intake at your server. A successful call to your own queue API may only mean a task was stored.
Preserve the outbound method, endpoint, time, status, and x-line-request-id. LINE’s development guidelines recommend logging this request evidence. Exclude access tokens and avoid copying customer message bodies into ordinary logs.
2. Verify the sender and destination together
Check which channel access token your deployed worker selected, which Official Account that channel represents, and where the destination ID originated. Production and test accounts can have similar names; a screenshot of the intended configuration is not evidence of what the worker used.
LINE’s user-ID guide distinguishes API user IDs from display names and searchable LINE IDs. It also scopes user IDs by provider. If a destination came from LINE Login or another integration, use the provider-mismatch checklist before trusting the mapping. A website login alone does not establish friendship with the sending Official Account.
3. Establish the relevant relationship
For an individual, review the available evidence of friendship or a qualifying recent one-to-one incoming message to this Official Account. Old CRM activity, a page view, or a message to a different account is not equivalent evidence.
If the relationship is unclear, leave it unknown. Do not repeatedly send probes to infer whether the person blocked the account. LINE’s development guidelines prohibit mass messaging to the same user; diagnosis should not become unwanted outreach.
4. Separate accepted, rejected, and unknown requests
| Observation | Next decision |
|---|---|
Push returned 200, recipient reports no message | Inspect identity and eligibility; do not automatically resend |
| A non-success API response exists | Investigate that actual response rather than treating it as this 200 case |
| Request timed out without a response | Preserve unknown acceptance and use the separate retry workflow |
Only your webhook returned 200 | Find whether an outbound request was ever dispatched |
For timeout handling, see the LINE retry-key guide. Retry protection addresses uncertain request acceptance; it does not change recipient eligibility or make a successful request deliverable.
Run a controlled check, not a resend loop
With a consenting test user, verify the exact Official Account in the LINE app, confirm the intended friend relationship, and send one recognizable test message through the same deployed channel. Compare the HTTP record with what the tester actually sees in the chat—not only with a notification banner.
If that works, it establishes a working path for that test user at that time. It does not prove another customer’s relationship, explain every earlier missing message, or justify replaying old jobs.
Use local tests for delayed-job logic: a non-friend’s qualifying message falls outside the seven-day condition before dispatch; a stored destination belongs to the wrong integration; and an accepted operation is presented to a retry worker. Expected results are a held job, an identity review, and no duplicate send respectively. These are proposed tests, not reported production results.
Keep the UnifyPort evidence separate
UnifyPort’s unofficial interface provides a separate connected-account path. Its text-send contract uses account_id, to, and message, and returns status: accepted in the documented success example. That is not a delivery receipt and does not recover a previous Official Account push.
The provider event matrix maps LINE delivery and read events, but explicitly does not guarantee every account or deployment emits every mapped event. Apply an observed receipt only to its identified messages; absence is not proof of blocking or failure. Never attach a receipt from a different account to an official push merely because the display names match.
Keep the official Messaging API when the sender must remain the Official Account. Switching sender identity is not an automatic recovery action and does not remove the recipient’s choices.
FAQ
Does HTTP 200 prove the customer blocked the Official Account?
No. It does not prove delivery or identify the reason for non-delivery. LINE documents several possible conditions.
Can I push to someone who has not added the account as a friend?
LINE documents an exception for users who sent that Official Account a one-to-one message within seven days. Do not generalize it to website visits or group interactions.
Should I send again when no message appears?
Not automatically after known acceptance. First verify the sender, recipient, eligibility, and evidence. A timeout is a different case from an observed 200.
Next step and sources
Start with one affected push and compare it with the official push conditions. For an existing UnifyPort integration, review the separate send contract before assigning delivery labels.
Official sources checked on 2026-11-18:
Turn messaging integration into a stable product pipeline.
Start by sending through one API, then bring every inbound message back into your business system with standard events.