[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-29 (世界標準時間)。"],[],[],null,["# Overview\n\nThe Google Tasks API lets you search, read, and update Google Tasks content and metadata. This document describes how to use a RESTful calling style and client libraries for various programming languages (currently Java, Python, and PHP) to access and edit Google Tasks data.\n\nSites or applications that want deeper integration with Google Tasks can leverage the Google Tasks API. For example, you could use the Google Tasks API to manage Google task lists in a mobile app, or you could integrate tasks into a more extensive workflow app such as [Au-to-do](http://code.google.com/p/au-to-do/).\n\nGoogle Tasks is built on two basic concepts:\n\nTask List\n: A list containing tasks. Users can have more than one task list to manage their tasks the way they want.\n\nTask\n: A single task containing information such as the title of the task, notes, the due date, and the completed date.\n\n### Tasks API data model\n\nA resource is an individual data entity with a unique identifier. The Google Tasks API operates on two types of resources:\n\nTask List Resource\n: Represents a task list.\n\nTask Resource\n: Represents a task.\n\nThe Tasks API data model is based on groups of resources, called collections:\n\nTask List Collection\n: Each user has at least one `default` Task List.\n\nTask Collection\n: Consists of all the Task Resources within a specific Task List Resource."]]
