LINE · API Governance Rules
LINE — line openapi rules
Spectral linting rules defining API design standards and conventions for LINE.
0 Rules
Published by LINE
Served by the provider at https://github.com/line/line-openapi/blob/fa5577c9ea874d2dbd8fadc85a4cb3a1b29d8cbe/.spectral.yaml; the copy below was fetched from there.
Spectral Ruleset
# harvested from https://github.com/line/line-openapi/blob/fa5577c9ea874d2dbd8fadc85a4cb3a1b29d8cbe/.spectral.yaml on 2026-10-09 — a Spectral ruleset published in the provider's own GitHub repository (line/line-openapi); found by GitHub code search, fetched verbatim
x-method: harvested
x-stamped: 2026-10-09
x-source-url: https://github.com/line/line-openapi/blob/fa5577c9ea874d2dbd8fadc85a4cb3a1b29d8cbe/.spectral.yaml
extends:
- '@ibm-cloud/openapi-ruleset'
- 'spectral:oas'
rules:
# `oas3-unused-component` doesn't care about discriminator.
# https://github.com/stoplightio/spectral/issues/1271
oas3-unused-component: off
# We can't clarify the contact point at this time.
info-contact: off
# https://github.com/IBM/openapi-validator/blob/main/docs/ibm-cloud-rules.md
# some API end points doesn't have a version number in path.
ibm-major-version-in-path: off
# we're using kebab case.
ibm-operationid-casing-convention: off
ibm-parameter-casing-convention: off
ibm-property-casing-convention: off
ibm-path-segment-casing-convention: off
ibm-operationid-naming-convention: off
# This rule doesn't match to our API specs.
ibm-enum-casing-convention: off
# This rule doesn't match to our API specs.
ibm-response-status-codes: off
# Can't care both description and summary at this time.
# TODO We may write summary field in the future.
ibm-operation-summary: off
# We're using `format: uri`. But it's not allowed by '@ibm-cloud/openapi-ruleset'.
ibm-schema-type-format: off
# I can't understand why it's needed.
ibm-requestbody-name: off
# we don't use ibm-cloud's pagination style
ibm-pagination-style: off
# description-mentions-json is meaningless
ibm-schema-description: off
ibm-collection-array-property: off
ibm-error-response-schemas: off
ibm-array-attributes: off
ibm-string-attributes: off
ibm-integer-attributes: off
ibm-required-array-properties-in-response: off
ibm-required-enum-properties-in-response: off
ibm-accept-and-return-models: off
overrides:
# TODO Response detail wasn't documented yet.
- files:
- "module.yml#/paths/~1v2~1bot~1channel~1detach"
- "module.yml#/paths/~1v2~1bot~1chat~1{chatId}~1control~1acquire"
- "module.yml#/paths/~1v2~1bot~1chat~1{chatId}~1control~1release"
- "shop.yml#/paths/~1shop~1v3~1mission"
rules:
ibm-request-and-response-content: off
# blob response
- files:
- "messaging-api-blob.yml#/paths/~1v2~1bot~1message~1{messageId}~1content/get"
- "messaging-api-blob.yml#/paths/~1v2~1bot~1message~1{messageId}~1content~1preview/get"
- "messaging-api-blob.yml#/paths/~1v2~1bot~1richmenu~1{richMenuId}~1content/get"
- "messaging-api-blob.yml#/paths/~1v2~1bot~1richmenu~1{richMenuId}~1content/post"
- "messaging-api-blob.yml#/paths/~1v2~1bot~1message~1{messageId}~1content~1transcoding/get"
rules:
ibm-string-attributes: off
ibm-content-type-is-specific: off
# empty response
- files:
- "messaging-api.yml#/paths"
- "manage-audience.yml#/paths/~1v2~1bot~1audienceGroup~1upload"
- "manage-audience.yml#/paths/~1v2~1bot~1audienceGroup~1{audienceGroupId}"
- "manage-audience.yml#/paths/~1v2~1bot~1audienceGroup~1authorityLevel/put"
- "manage-audience-blob.yml#/paths"
- "channel-access-token.yml#/paths/~1oauth2~1v2.1~1revoke"
- "channel-access-token.yml#/paths/~1v2~1oauth~1revoke"
- "messaging-api-blob.yml#/paths/~1v2~1bot~1richmenu~1{richMenuId}~1content"
rules:
ibm-request-and-response-content: off
# enum with null issue.
- files:
- "manage-audience.yml#/paths/~1v2~1bot~1audienceGroup~1{audienceGroupId}"
rules:
oas3-valid-media-example: off
# e.g. spectral lint messaging-api.yml --ruleset=.spectral.yaml
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for spectral rules
4 MCP tools reach this
find_rulesBrowse and filter every ruleset in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/line-line-openapi-spectral-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.