LINE website screenshot

LINE

LINE is a Japan-based messaging platform operated by LY Corporation, with over 200 million monthly active users across Japan, Taiwan, Thailand and Indonesia, offering messaging, payments, news and a broad ecosystem of services. The LINE Developers platform exposes public APIs for building chatbots and Official Accounts (Messaging API), issuing and rotating credentials (Channel Access Token API), reading delivery and audience analytics (Insight API), building marketing audiences (Manage Audience API), running web apps inside the LINE client (LIFF), and social login via LINE Login v2.1 over OAuth 2.0 and OpenID Connect. LINE publishes nine first-party OpenAPI documents covering 111 operations at github.com/line/line-openapi and generates all six official server SDKs from them. Server API calls authenticate with a channel access token presented as an HTTP Bearer credential and scoped to a single LINE channel.

LINE publishes 9 APIs on the APIs.io network, including Messaging API, Messaging API Webhook, Channel Access Token API, and 6 more. Tagged areas include Messaging, Chatbots, Social Login, Mini Apps, and Marketing.

The LINE catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

LINE’s developer surface includes authentication, CLI, sandbox, changelog, documentation, API reference, getting-started guide, and 37 more developer resources.

71.6/100 exemplar ▬ flat Agent 55/100 agent native Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
AccessFreemiumSelf serveFree trial
10 APIs 2 MCP Servers
MessagingChatbotsSocial LoginMini AppsMarketingWebhookOpenID ConnectAudienceAnalyticsJapan

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 71.6/100 · exemplar
Contract Quality 14.8 / 25
Developer Ergonomics 16.1 / 20
Access Clarity 15.3 / 20
Operational Transparency 10.9 / 13
Contract Governance 5.3 / 12
Discoverability 9.3 / 10
Agent readiness — 55/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/line: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

LINE Messaging API

The core LINE bot API — 73 operations for replying, pushing, multicasting, broadcasting and narrowcasting messages to LINE users, plus rich menus, Flex messages, group and room ...

LINE Messaging API Webhook

The inbound event surface of the Messaging API, published by LINE as an OpenAPI type-definition document. LINE delivers CallbackRequest envelopes to the bot server's configured ...

LINE Channel Access Token API

Issues, verifies and revokes the channel access tokens every other LINE server API consumes. Four generations run concurrently: long-lived tokens from the Developers Console, v2...

LINE Insight API

Seven read operations returning analytics for a LINE Official Account — friend demographics, number of followers, number of message deliveries by day, per-request message event ...

LINE Manage Audience API

Twelve operations for building and managing the marketing audiences a narrowcast targets — creating audiences from uploaded user IDs by JSON or by file, click-based and impressi...

LIFF Server API

Four operations for managing LINE Front-end Framework apps on a LINE Login channel — add, list, update and delete LIFF apps. LIFF apps are web applications that run inside the L...

LINE Module API

Four operations for the module feature, which lets a partner-operated module channel take and release chat control on behalf of a LINE Official Account — detach a module, acquir...

LINE Module Attach API

A single operation that attaches a module channel to a LINE Official Account and returns the resulting bot and scope grant. The only operation across LINE's nine published speci...

LINE Mission Sticker API

A single operation for the Mission Sticker programme, granting a user a sticker reward after they complete a defined mission with a corporate LINE Official Account. Available on...

LINE Login v2.1

End-user authentication and authorization over OAuth 2.0 authorization code grant and OpenID Connect. Authorization runs at access.line.me; token, userinfo, revocation and JWKS ...

Scroll for all 10

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

LINE Messaging API

OPEN COLLECTION

MCP Servers 2

Model Context Protocol servers that expose these APIs to AI agents.

MCP Server

MCP SERVER

MCP Server manifest

First-party Model Context Protocol server published by LY Corporation that wraps the LINE Messaging API so an AI agent can drive a LINE Official Account — pushing and broadcasti...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Line Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Line Rate Limits

10 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

LINE Messaging Webhook Event Surface

AsyncAPI description of the webhook event surface published by the LINE Messaging API to bot servers. The Messaging API delivers webhook events as HTTPS POST requests to the con...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LINE API Rules

4 rules · 1 errors 2 warnings 1 info

SPECTRAL

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Line Authentication

http/oauth2/openIdConnect · 3 schemes

SECURITY

Line Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Line Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Line Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Line Agentic Access

111 operations · 59 acting · 4 human-in-the-loop

111 operations · 59 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 7

MCP servers, agent skills, and machine-readable catalogs

Scroll for all 7

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: line
name: LINE
description: LINE is a Japan-based messaging platform operated by LY Corporation, with over 200 million monthly active users
  across Japan, Taiwan, Thailand and Indonesia, offering messaging, payments, news and a broad ecosystem of services. The
  LINE Developers platform exposes public APIs for building chatbots and Official Accounts (Messaging API), issuing and rotating
  credentials (Channel Access Token API), reading delivery and audience analytics (Insight API), building marketing audiences
  (Manage Audience API), running web apps inside the LINE client (LIFF), and social login via LINE Login v2.1 over OAuth 2.0
  and OpenID Connect. LINE publishes nine first-party OpenAPI documents covering 111 operations at github.com/line/line-openapi
  and generates all six official server SDKs from them. Server API calls authenticate with a channel access token presented
  as an HTTP Bearer credential and scoped to a single LINE channel.
type: Index
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: true
  try_now: false
  public: true
  label: Self-serve signup, free tier metered on messages sent
  confidence: high
  source:
  - plans/line-plans-pricing.yml
  - authentication/line-authentication.yml
  generated: '2026-08-13'
  method: searched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/line.png
tags:
- Messaging
- Chatbots
- Social Login
- Mini Apps
- Marketing
- Webhook
- OpenID Connect
- Audience
- Analytics
- Japan
tags_raw:
- Messaging
- Chatbots
- Social Login
- Mini Apps
- Marketing
- Webhooks
- OpenID Connect
- Audience
- Analytics
- Japan
url: https://raw.githubusercontent.com/api-evangelist/line/refs/heads/main/apis.yml
created: '2026-05-11'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- aid: line:line-messaging-api
  name: LINE Messaging API
  description: The core LINE bot API — 73 operations for replying, pushing, multicasting, broadcasting and narrowcasting messages
    to LINE users, plus rich menus, Flex messages, group and room membership, profiles, followers, message quota, delivery
    statistics, coupons, memberships and webhook endpoint configuration. Supports idempotent retries via the X-Line-Retry-Key
    header on the four metered send operations. Binary content (message media, rich menu images) is served from api-data.line.me
    rather than api.line.me.
  humanURL: https://developers.line.biz/en/docs/messaging-api/
  baseURL: https://api.line.me
  tags:
  - Messaging
  - Chatbots
  - Rich Menu
  - Webhook
  tags_raw:
  - Messaging
  - Chatbots
  - Rich Menu
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/line-messaging-api-openapi.yml
  - type: Overlay
    url: overlays/line-messaging-api-overlay.yaml
  - type: Documentation
    url: https://developers.line.biz/en/docs/messaging-api/
  - type: APIReference
    url: https://developers.line.biz/en/reference/messaging-api/
  - type: GettingStarted
    url: https://developers.line.biz/en/docs/messaging-api/getting-started/
  - type: AsyncAPI
    url: asyncapi/line-messaging-webhook.yml
  - type: Webhooks
    url: openapi/line-webhook-openapi.yml
- aid: line:line-webhook
  name: LINE Messaging API Webhook
  description: The inbound event surface of the Messaging API, published by LINE as an OpenAPI type-definition document. LINE
    delivers CallbackRequest envelopes to the bot server's configured HTTPS endpoint, carrying an events[] array of 20+ polymorphic
    event types (message, follow, unfollow, join, leave, postback, beacon, accountLink, membership, videoPlayComplete and
    others) over 60 component schemas. Every delivery is signed with a Base64 HMAC-SHA256 of the raw body in the x-line-signature
    header.
  humanURL: https://developers.line.biz/en/reference/messaging-api/#webhooks
  baseURL: https://api.line.me
  tags:
  - Webhook
  - Event
  tags_raw:
  - Webhooks
  - Events
  properties:
  - type: OpenAPI
    url: openapi/line-webhook-openapi.yml
  - type: AsyncAPI
    url: asyncapi/line-messaging-webhook.yml
  - type: Overlay
    url: overlays/line-webhook-overlay.yaml
  - type: Documentation
    url: https://developers.line.biz/en/docs/messaging-api/receiving-messages/
  - type: Spectral
    url: rules/line-asyncapi-spectral-rules.yml
  note: baseURL records the platform host that originates the delivery. The published spec declares servers[] as https://example.com
    because the receiving endpoint is owned by the bot developer, not by LINE.
- aid: line:line-channel-access-token-api
  name: LINE Channel Access Token API
  description: 'Issues, verifies and revokes the channel access tokens every other LINE server API consumes. Four generations
    run concurrently: long-lived tokens from the Developers Console, v2.0 short-lived tokens, v2.1 JWT-assertion tokens that
    support concurrent validity and zero-downtime rotation, and v3 stateless 15-minute tokens. Eight operations.'
  humanURL: https://developers.line.biz/en/docs/basics/channel-access-token/
  baseURL: https://api.line.me
  tags:
  - Authentication
  - Tokens
  properties:
  - type: OpenAPI
    url: openapi/line-channel-access-token-openapi.yml
  - type: Overlay
    url: overlays/line-channel-access-token-overlay.yaml
  - type: Documentation
    url: https://developers.line.biz/en/docs/basics/channel-access-token/
  - type: Authentication
    url: authentication/line-authentication.yml
- aid: line:line-insight-api
  name: LINE Insight API
  description: Seven read operations returning analytics for a LINE Official Account — friend demographics, number of followers,
    number of message deliveries by day, per-request message event statistics (impressions, clicks, per-link breakdown), statistics
    per aggregation unit, and rich menu insight totals and daily series.
  humanURL: https://developers.line.biz/en/reference/messaging-api/#get-insight
  baseURL: https://api.line.me
  tags:
  - Analytics
  - Insight
  properties:
  - type: OpenAPI
    url: openapi/line-insight-openapi.yml
  - type: Overlay
    url: overlays/line-insight-overlay.yaml
  - type: APIReference
    url: https://developers.line.biz/en/reference/messaging-api/#get-insight
- aid: line:line-manage-audience-api
  name: LINE Manage Audience API
  description: Twelve operations for building and managing the marketing audiences a narrowcast targets — creating audiences
    from uploaded user IDs by JSON or by file, click-based and impression-based audiences derived from earlier sends, renaming,
    deleting, and reading audience data and shared Business Manager audiences. Uploads are asynchronous jobs limited to ten
    concurrent operations per audience.
  humanURL: https://developers.line.biz/en/reference/messaging-api/#manage-audience-group
  baseURL: https://api.line.me
  tags:
  - Marketing
  - Audience
  properties:
  - type: OpenAPI
    url: openapi/line-manage-audience-openapi.yml
  - type: Overlay
    url: overlays/line-manage-audience-overlay.yaml
  - type: APIReference
    url: https://developers.line.biz/en/reference/messaging-api/#manage-audience-group
  note: The by-file variants (createAudienceForUploadingUserIds, addUserIdsToAudience) must be sent to https://api-data.line.me,
    not api.line.me.
- aid: line:line-liff-api
  name: LIFF Server API
  description: Four operations for managing LINE Front-end Framework apps on a LINE Login channel — add, list, update and
    delete LIFF apps. LIFF apps are web applications that run inside the LINE client's in-app browser and can read the logged-in
    user's profile, obtain an ID token, send messages into the current chat and open the scanner.
  humanURL: https://developers.line.biz/en/reference/liff-server/
  baseURL: https://api.line.me
  tags:
  - Mini Apps
  - LIFF
  properties:
  - type: OpenAPI
    url: openapi/line-liff-openapi.yml
  - type: Overlay
    url: overlays/line-liff-overlay.yaml
  - type: APIReference
    url: https://developers.line.biz/en/reference/liff-server/
  - type: Documentation
    url: https://developers.line.biz/en/docs/liff/
  - type: CLI
    url: cli/line-cli.yml
- aid: line:line-module-api
  name: LINE Module API
  description: Four operations for the module feature, which lets a partner-operated module channel take and release chat
    control on behalf of a LINE Official Account — detach a module, acquire chat initiative, release it, and list the bots
    a module is attached to.
  humanURL: https://developers.line.biz/en/docs/partner-docs/module/
  baseURL: https://api.line.me
  tags:
  - Modules
  - Partner
  properties:
  - type: OpenAPI
    url: openapi/line-module-openapi.yml
  - type: Overlay
    url: overlays/line-module-overlay.yaml
  - type: Documentation
    url: https://developers.line.biz/en/docs/partner-docs/module/
- aid: line:line-module-attach-api
  name: LINE Module Attach API
  description: A single operation that attaches a module channel to a LINE Official Account and returns the resulting bot
    and scope grant. The only operation across LINE's nine published specifications that uses HTTP Basic authentication, and
    the only one served from manager.line.biz rather than api.line.me.
  humanURL: https://developers.line.biz/en/docs/partner-docs/module-technical-attach-channel/
  baseURL: https://manager.line.biz
  tags:
  - Modules
  - Partner
  properties:
  - type: OpenAPI
    url: openapi/line-module-attach-openapi.yml
  - type: Overlay
    url: overlays/line-module-attach-overlay.yaml
  - type: Documentation
    url: https://developers.line.biz/en/docs/partner-docs/module-technical-attach-channel/
- aid: line:line-shop-api
  name: LINE Mission Sticker API
  description: A single operation for the Mission Sticker programme, granting a user a sticker reward after they complete
    a defined mission with a corporate LINE Official Account. Available only to corporate customers who have submitted the
    required application.
  humanURL: https://developers.line.biz/en/docs/partner-docs/mission-stickers/
  baseURL: https://api.line.me
  tags:
  - Stickers
  - Partner
  properties:
  - type: OpenAPI
    url: openapi/line-shop-openapi.yml
  - type: Overlay
    url: overlays/line-shop-overlay.yaml
  - type: Documentation
    url: https://developers.line.biz/en/docs/partner-docs/mission-stickers/
- aid: line:line-login-api
  name: LINE Login v2.1
  description: End-user authentication and authorization over OAuth 2.0 authorization code grant and OpenID Connect. Authorization
    runs at access.line.me; token, userinfo, revocation and JWKS endpoints are on api.line.me. ID tokens are ES256-signed
    JWTs with pairwise subject identifiers, PKCE is supported with S256 only, and JARM response modes (jwt, query.jwt, form_post.jwt)
    are accepted. Scopes are openid, profile and email. LINE publishes no OpenAPI for this surface — the machine-readable
    contract is the OIDC discovery document.
  humanURL: https://developers.line.biz/en/docs/line-login/
  baseURL: https://api.line.me
  tags:
  - Social Login
  - OpenID Connect
  - Authentication
  tags_raw:
  - Social Login
  - OpenID Connect
  - OAuth
  properties:
  - type: OpenIDConnect
    url: well-known/line-openid-configuration.json
  - type: OAuthScopes
    url: scopes/line-scopes.yml
  - type: Documentation
    url: https://developers.line.biz/en/docs/line-login/
  - type: APIReference
    url: https://developers.line.biz/en/reference/line-login/
  - type: GettingStarted
    url: https://developers.line.biz/en/docs/line-login/integrate-line-login/
common:
- type: AgenticAccess
  url: agentic-access/line-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/line-vulnerability-disclosure.yml
- type: Security
  url: security/line-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/line-domain-security.yml
- type: Authentication
  url: authentication/line-authentication.yml
- type: OAuthScopes
  url: scopes/line-scopes.yml
- type: Packages
  url: packages/line-packages.yml
- type: SDKs
  url: packages/line-packages.yml
- type: CLI
  url: cli/line-cli.yml
- type: Components
  url: components/line-components.yml
- type: Sandbox
  url: sandbox/line-sandbox.yml
- type: Conventions
  url: conventions/line-conventions.yml
- type: Idempotency
  url: conventions/line-conventions.yml
- type: ErrorCatalog
  url: errors/line-problem-types.yml
- type: RateLimits
  url: rate-limits/line-rate-limits.yml
- type: Plans
  url: plans/line-plans-pricing.yml
- type: Lifecycle
  url: lifecycle/line-lifecycle.yml
- type: StatusPage
  url: https://api.line-status.info/
- type: Deprecation
  url: lifecycle/line-lifecycle.yml
- type: ChangeLog
  url: changelog/line-changelog.yml
- type: Conformance
  url: conformance/line-conformance.yml
- type: DataModel
  url: data-model/line-data-model.yml
- type: WellKnown
  url: well-known/line-well-known.yml
- type: SecurityTxt
  url: well-known/line-security.txt
- type: MCPServer
  name: MCP Server
  url: https://github.com/line/line-bot-mcp-server
- type: MCPServer
  name: MCP Server manifest
  url: mcp/line-mcp.yml
- type: ToolCrosswalk
  url: mcp/line-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/line-llms.txt
- type: LlmsText
  url: https://developers.line.biz/llms.txt
- type: LinkedIn
  url: https://www.linkedin.com/company/linecorp
- type: Website
  url: https://line.me
- type: DeveloperPortal
  url: https://developers.line.biz/en/
- type: Documentation
  url: https://developers.line.biz/en/docs/
- type: APIReference
  url: https://developers.line.biz/en/reference/messaging-api/
- type: GettingStarted
  url: https://developers.line.biz/en/docs/messaging-api/getting-started/
- type: Support
  url: https://developers.line.biz/en/faq/
- type: Blog
  url: https://techblog.lycorp.co.jp/en/
- type: OpenAPI Repository
  url: https://github.com/line/line-openapi
- type: GitHubOrganization
  url: https://github.com/line
- type: SignUp
  url: https://developers.line.biz/console/
- type: Pricing
  url: https://developers.line.biz/en/docs/messaging-api/pricing/
- type: TermsOfService
  url: https://developers.line.biz/en/terms-and-policies/
- type: PrivacyPolicy
  url: https://www.lycorp.co.jp/en/company/privacypolicy/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 42
  pass: local-v1