← All posts
Guide

LINE API Playground Is Ending: Move Tests to curl

LINE plans to discontinue API Playground in the Messaging API reference on November 30, 2026. The Messaging API itself is not being discontinued. LINE recommends trying requests with tools such as curl, using the examples in each endpoint’s reference. Replace your browser-based testing instructions—not your working API integration—and start with a read-only request before testing message sends.

Key takeaways

  • The change removes a browser testing feature, not the Messaging API.
  • Keep request templates separate from live channel access tokens.
  • A successful bot-information lookup does not prove message delivery or webhook reception.
  • Moving tests does not require changing sender identity or switching to UnifyPort.

What LINE is discontinuing

The November 13 announcement in LINE’s 2026 news describes API Playground as the reference feature that sends requests to selected endpoints and displays responses in the browser. LINE cites usage and security requirements for continued operation as the reasons for ending it, and explicitly says the Messaging API is unaffected.

As of this article’s check on November 19, the discontinuation is scheduled, not an already completed outage. The notice concerns this specific reference tool; do not extend it to every LINE development tool.

Look for internal onboarding pages, troubleshooting instructions, and screenshots that say “click Try.” Replace those steps with a reviewed request example, the required credential source, and instructions for interpreting the response. Existing application code does not need rewriting solely because that button is going away.

Replace the first test with a read-only lookup

The Messaging API reference documents GET /v2/bot/info for basic LINE Official Account information, authenticated with a channel access token. It is a useful first check because it does not send a customer message.

Before running it:

  1. Select the intended test channel and record which Official Account it represents.
  2. Load its token into LINE_CHANNEL_ACCESS_TOKEN through your protected local environment. This is an example variable name, not a LINE API field.
  3. Use a trusted terminal with command tracing disabled. Do not paste live tokens into shared documents, screenshots, or recorded sessions.
  4. If credential selection is unclear, use the channel access token location guide. Do not reissue a working credential merely to replace the test tool.

Illustrative shell request, not executed for this article:

printf 'Authorization: Bearer %s\n' "$LINE_CHANNEL_ACCESS_TOKEN" |
  curl --silent --show-error --include \
    --header @- \
    'https://api.line.me/v2/bot/info'

Here the authorization header is supplied through standard input instead of being written literally into the command. That is not a complete secret-management solution: the environment and terminal still need protection. Do not enable verbose tracing or upload unredacted diagnostics.

Inspect the HTTP status and response body, then compare the returned account information with your intended sender. A successful response for the wrong account is a failed configuration check. No HTTP response means the API result has not been established; distinguish that from a returned API error.

If the request differs from the reference, compare the final method, host, and path using the LINE endpoint URL checklist, rather than changing credentials and payloads simultaneously.

Keep three test results separate

TestWhat it can establishWhat it does not establish
Read bot informationThis request authenticated and returned an account identityCustomer delivery or working webhooks
Deliberate send to a consenting testerThe observed result of that specific sending operationDelivery to every other recipient
Incoming message through the webhookThe observed receiving path for that eventThat all outbound operations work

If you need a send test, choose the method and test recipient deliberately from the official reference. Do not turn a saved production request into a connectivity probe. Keep automatic retries out of the initial manual check; a lost response can leave an uncertain result. The separate LINE retry-key guide covers supported-send retry design.

For your replacement runbook, retain the operation, test-channel label, observation time, HTTP status, and a redacted response summary. Keep access tokens and customer content out of shared evidence. These are recommended records, not new LINE response fields.

Where UnifyPort fits—and where it does not

UnifyPort is a separate unofficial interface, not a replacement host for LINE API Playground. Its text-send reference documents POST /v1/messages with X-Api-Key authentication and the fields account_id, to, and message. A LINE channel access token and a native Messaging API request cannot simply be pasted into that contract.

If you already use UnifyPort, maintain separate test instructions for its API and incoming events. If you need the LINE Official Account sender and its official capabilities, continue using the Messaging API. The removal of a testing UI is not a reason to migrate accounts or change production webhooks.

FAQ

Is LINE Messaging API shutting down on November 30?

No. LINE’s notice schedules the removal of API Playground and explicitly says the Messaging API itself is unaffected.

Do I need a new token for curl?

Changing the HTTP client alone is not a token-rotation requirement. Use a valid channel access token for the intended channel and protect it outside the saved request template.

Does a successful bot-info request prove my bot can receive messages?

No. Test inbound webhook reception separately. Likewise, account information is not evidence that a customer received a sent message.

Next step and sources

Replace one internal “Try” instruction with the read-only check from the official Messaging API reference, then document separate send and receive checks.

Official sources checked on 2026-11-19:

UnifyPort API

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.