[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Looker API and SDK support policies\n\n| **Note:** As of Looker 22.4, the [Looker API 4.0 is generally available](/looker/docs/api-4-ga). In Looker 23.18, the [Looker API 3.1 has been removed](/looker/docs/api-3x-deprecation).\n\nLooker provides multiple [API versions](/looker/docs/api-intro) and multiple [language SDKs](/looker/docs/api-intro/api-sdk) that use those APIs. This document describes the status and support policies for the Looker API versions and language SDKs.\n\nSupport levels\n--------------\n\nLooker API versions and SDKs have varying levels of support:\n\n- [Looker supported](#looker_supported)\n- [Community supported](#community_supported)\n- [Not supported](#not_supported)\n\nThe support levels are described in the following sections.\n\n### Looker supported\n\nLooker supports these API versions and language SDKs. Support tickets can be filed with Looker Support and conform to [Looker Support guidelines](https://looker.com/trust-center/legal/customers/support#terms-of-support-services). Only API 4.0 is Looker supported.\n\n### Community supported\n\nThis level only applies to language SDKs. Issues are filed and managed in the OpenSource repository that is used for that SDK.\n\nA language SDK can be at the community support level for several reasons:\n\n- It lacks the features required to achieve the Looker supported level.\n- It needs more support and automation infrastructure (automated testing, packaging, documentation, examples, etc.) before it can be fully supported by Looker.\n- It is based on deprecated technology.\n- It has not been tested by enough different users to be deemed ready to move out of \"alpha\" status.\n\n### Not supported\n\nNo support is provided. API versions 3.0 and 3.1 are unsupported.\n\nAPI versions\n------------\n\nThe following table lists the three documented API versions as of Looker 22.4 and shows their support levels.\n\nAny future API versions will be introduced as alpha and then move through the beta, stable, and deprecated lifecycles.\n\nLanguage SDKs\n-------------\n\nLooker's [language SDKs](/looker/docs/api-sdk) have evolved throughout Looker's lifetime and are produced with a variety of tools and techniques. All SDKs directly or indirectly use Looker's [API specification documents](https://github.com/looker-open-source/sdk-codegen#the-parts-of-the-looker-sdk). The support status of the language SDKs is described in the following table.\n\n### Tooling legend\n\n- **codegen** --- Generated by Looker's [SDK codegen project](https://github.com/looker-open-source/sdk-codegen) and uses a [hand-written run-time library for each SDK](https://github.com/looker-open-source/sdk-codegen/blob/main/docs/byosdk.md#run-time-library).\n- **Swagger** --- Generated by the [Swagger code generator](https://swagger.io/docs/open-source-tools/swagger-codegen/) OpenSource tool. For programming languages not directly supported by Looker's code generator, we have provided a legacy generator option in the codegen repository that should simplify the custom generation. This \"legacy\" generator uses the OpenSource [OpenAPI code generator](https://github.com/OpenAPITools/openapi-generator), which is the replacement for the Swagger code generator.\n- **Hand written** --- All source code is written by hand with no code generation involved.\n\n### SDK versioning\n\nLooker recently adopted a versioning scheme that matches language SDKs with the Looker release that was used to generate them. For example, this means an SDK that was produced using Looker 21.10 specifications will have a version that starts with 21.10.\\*.\n\n#### Language SDKs\n\nThe most recent language SDKs (produced by Looker codegen) match Looker release versions. For example, the Python and TypeScript SDKs match their respective Looker release versions.\n\nAs we move our older language SDKs to codegen, or publish existing codegen SDKs to their package managers, the SDK version will be set to match the Looker release version.\n\n#### Runtime library package versions\n\nThe TypeScript SDK depends on a separate runtime library (RTL) package, written by Looker, that generically supports REST APIs. Because it is not specific to any Looker release, this package is versioned independently of the language SDKs that use it.\n\nWhen other language SDKs are published to package managers, their RTLs may become a separate package. Any separate RTL package will use semantic versioning rather than matching Looker release versions."]]
