[[["容易理解","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 overview\n\n| **Note:** As of Looker 22.4, the [Looker API 4.0 is generally available](/looker/docs/api-4-ga). The API 3.1 is deprecated.\n\nLooker's API provides access to the vast majority of Looker functionality over a convenient JSON-oriented REST API. It includes a diversity of endpoints, from simple running of queries in a variety of formats, to managing users, content, schedules, instance configurations, and more.\n\nThe API can be used as a part of many use cases. Some examples include internal operational tools, highly custom customer-facing embedded analytics, mobile app integrations, specialized Looker administrative tools, and more.\n\nUsing the API\n-------------\n\nYou can use the API either directly via HTTPS requests or through the convenience of a language-specific SDK.\n\nIn addition, the API provides for a few authentication modes, which may help inform your architectural choices. Backend services can authenticate with API credentials, can use the API with a service account, and can conveniently impersonate API requests on behalf of end users. Alternatively, frontend clients can leverage [OAuth authentication (Authorization Code PKCE)](https://oauth.net/2/pkce/), without the need to handle sensitive client secrets.\n\nHere is a sample of the most common ways that the API is used end-to-end:\n\n- Backend only\n - Authenticate with [API credentials](/looker/docs/api-auth): Common for command-line scripts, administrative tasks, or sandbox environments\n- Frontend and backend\n - Provide an application server with single service account and credentials, and make API calls through the service account\n - Provide an application server with single service account and credentials, but use Looker's `sudo` or `login_as_user` functionality to make calls on behalf of the end user\n - Authenticate with an application server, use sudo/login_as_user, send the resulting token back to the user, and make frontend API calls with [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)\n- Frontend only\n - Authenticate with [OAuth](/looker/docs/api-cors), and make frontend API calls with CORS\n - Implicit authentication and invocation from within Looker extensions\n\nTry it out\n----------\n\nWant to see the API in action before writing any code? These demos can help:\n\n- [Atom Fashion](https://atomfashion.io/) is a demo data-driven web app (requires Google account to log in).\n- Explore API endpoints and make sample API calls against your Looker instance using the [API Explorer](/looker/docs/api-explorer)."]]
