Please note that the contents of this offline web site may be out of date. To access the most recent documentation visit the online version .
Note that links that point to online resources are green in color and will open in a new window.
We would love it if you could give us feedback about this material by filling this form (You have to be online to fill it)



The Task Queue REST API

Often, the easiest way to learn how to use an API can be to look at sample code. This page provides links to samples and a number of convenient ways to access the Google App Engine Task Queue.

Google APIs client libraries

The Google App Engine Task Queue is built on HTTP and JSON, so any standard web stack can send requests to it and parse the responses.

However, instead of creating HTTP requests and parsing responses manually, you may want to use the Google APIs Client Libraries. The client libraries provide better language integration, improved security, and support for making calls that require user authorization.

In the tables below, the first column shows each library's stage of development (note that some are in early stages), and links to documentation for the library. The second column links to available samples for each library.

Documentation Samples
Google APIs Client Library for Java (rc) Java samples
Google APIs Client Library for JavaScript (beta) JavaScript samples
Google APIs Client Library for .NET .NET samples
Google APIs Client Library for Objective-C Objective-C samples
Google APIs Client Library for PHP (beta) PHP samples
Google APIs Client Library for Python Python samples

These early-stage libraries are also available:

Documentation Samples
Google APIs Client Library for Go (alpha) Go samples
Google APIs Client Library for Node.js (alpha) Node.js samples
Google APIs Client Library for Ruby (alpha) Ruby samples

In addition to the Google-supported client libraries listed in the table above, a set of third-party Dart libraries (with samples ) is available for the Dart language .

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.