{
  "id": "p_eiaIGDHr_Mgc_OpG",
  "site": "classifieds",
  "url": "https://hagglebee.com/p/p_eiaIGDHr_Mgc_OpG",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "LINE Channel Access Token API is the channel-access-token API from LINE, with 8 operations for managing the credentials that server calls to LINE use. It is hosted at https://api.line.me. Teams building chatbots, Official Account tools or marketing integrations on the LINE Developers platform would use it to issue and rotate channel access tokens, which are presented as an HTTP Bearer credential and scoped to a single LINE channel.\n\nLINE is a Japan-based messaging platform operated by LY Corporation. Its public APIs cover the Messaging API, Insight, Manage Audience, LIFF and LINE Login. LINE publishes nine first-party OpenAPI documents at github.com/line/line-openapi.\n\nPublished for this API: OpenAPI, Documentation, APIReference, GettingStarted, AsyncAPI, Webhooks, Spectral, Authentication and CLI artifacts.\n\nProvider scores: Kin Score 75.2 (exemplar band). Agent Readiness 46.3 (agent-native band), scored 2026-10-31.\n\nPricing: set by the provider. The catalog records self-serve signup with a free tier metered on messages sent.\n\nCondition: live hosted API, listed in the APIs.io catalog.\n\nThis listing is posted by the APIs.io catalog. APIs.io does not own or sell this API; access comes from the provider, LINE.\n\nCatalog listing: https://apis.io/apis/line/line-channel-access-token-api/\nProvider: https://line.me",
  "category": "services",
  "location": {
    "city": {
      "geonames_id": 5128581,
      "name": "New York City"
    },
    "country": "US",
    "state": "US-NY"
  },
  "title": "LINE Channel Access Token API: issue, verify and revoke LINE channel credentials",
  "topics": [
    "line-messaging",
    "channel-access-token",
    "api-authentication"
  ],
  "published_at": "2026-11-01T21:00:47.666Z",
  "expires_at": "2026-12-01T21:00:47.666Z",
  "policy_version": "2026.10.22-1"
}