App Engine target. The job will be pushed to a job handler by means
of an HTTP request via an
http_method
such as HTTP POST, HTTP GET, etc. The job is acknowledged by means
of an HTTP response code in the range [200 - 299]. Error 503 is
considered an App Engine system error instead of an application
error. Requests returning error 503 will be retried regardless of
retry configuration and not counted against retry counts. Any other
response code, or a failure to receive a response before the
deadline, constitutes a failed attempt.
For more information about services, versions, and instances see An
Overview of App
Engine <https://cloud.google.com/appengine/docs/python/an-overview-of-app-engine>,
Microservices Architecture on Google App
Engine <https://cloud.google.com/appengine/docs/python/microservices-on-app-engine>,
App Engine Standard request
routing <https://cloud.google.com/appengine/docs/standard/python/how-requests-are-routed>,
and App Engine Flex request
routing <https://cloud.google.com/appengine/docs/flexible/python/how-requests-are-routed>.
Http target. The job will be pushed to the job handler by means of
an HTTP request via an
http_method
such as HTTP POST, HTTP GET, etc. The job is acknowledged by means
of an HTTP response code in the range [200 - 299]. A failure to
receive a response constitutes a failed execution. For a redirected
request, the response returned by the redirected request is
considered.
This message has oneof_ fields (mutually exclusive fields).
For each oneof, at most one member field can be set at the same time.
Setting any member of the oneof automatically clears all other
members.
Configuration for a job.
The maximum allowed size for a job is 1MB.
This message has oneof_ fields (mutually exclusive fields).
For each oneof, at most one member field can be set at the same time.
Setting any member of the oneof automatically clears all other
members.
Contains information needed for generating an OAuth
token <https://developers.google.com/identity/protocols/OAuth2>__.
This type of authorization should generally only be used when
calling Google APIs hosted on *.googleapis.com.
Contains information needed for generating an OpenID Connect
token <https://developers.google.com/identity/protocols/OpenIDConnect>__.
This type of authorization can be used for many scenarios, including
calling Cloud Run, or endpoints where you intend to validate the
token yourself.
By default, if a job does not complete successfully (meaning that an
acknowledgement is not received from the handler, then it will be
retried with exponential backoff according to the settings in
RetryConfig.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Package types (2.16.0)\n\nVersion latestkeyboard_arrow_down\n\n- [2.16.0 (latest)](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types)\n- [2.15.1](/python/docs/reference/cloudscheduler/2.15.1/google.cloud.scheduler_v1beta1.types)\n- [2.14.1](/python/docs/reference/cloudscheduler/2.14.1/google.cloud.scheduler_v1beta1.types)\n- [2.13.5](/python/docs/reference/cloudscheduler/2.13.5/google.cloud.scheduler_v1beta1.types)\n- [2.12.0](/python/docs/reference/cloudscheduler/2.12.0/google.cloud.scheduler_v1beta1.types)\n- [2.11.3](/python/docs/reference/cloudscheduler/2.11.3/google.cloud.scheduler_v1beta1.types)\n- [2.10.0](/python/docs/reference/cloudscheduler/2.10.0/google.cloud.scheduler_v1beta1.types)\n- [2.9.1](/python/docs/reference/cloudscheduler/2.9.1/google.cloud.scheduler_v1beta1.types)\n- [2.8.0](/python/docs/reference/cloudscheduler/2.8.0/google.cloud.scheduler_v1beta1.types)\n- [2.7.3](/python/docs/reference/cloudscheduler/2.7.3/google.cloud.scheduler_v1beta1.types)\n- [2.6.4](/python/docs/reference/cloudscheduler/2.6.4/google.cloud.scheduler_v1beta1.types)\n- [2.5.1](/python/docs/reference/cloudscheduler/2.5.1/google.cloud.scheduler_v1beta1.types)\n- [2.4.0](/python/docs/reference/cloudscheduler/2.4.0/google.cloud.scheduler_v1beta1.types)\n- [2.3.4](/python/docs/reference/cloudscheduler/2.3.4/google.cloud.scheduler_v1beta1.types)\n- [2.2.0](/python/docs/reference/cloudscheduler/2.2.0/google.cloud.scheduler_v1beta1.types)\n- [2.1.1](/python/docs/reference/cloudscheduler/2.1.1/google.cloud.scheduler_v1beta1.types)\n- [2.0.0](/python/docs/reference/cloudscheduler/2.0.0/google.cloud.scheduler_v1beta1.types)\n- [1.3.2](/python/docs/reference/cloudscheduler/1.3.2/google.cloud.scheduler_v1beta1.types)\n- [1.2.1](/python/docs/reference/cloudscheduler/1.2.1/google.cloud.scheduler_v1beta1.types) \nAPI documentation for `scheduler_v1beta1.types` package. \n\nClasses\n-------\n\n### [AppEngineHttpTarget](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.AppEngineHttpTarget)\n\nApp Engine target. The job will be pushed to a job handler by means\nof an HTTP request via an\nhttp_method\nsuch as HTTP POST, HTTP GET, etc. The job is acknowledged by means\nof an HTTP response code in the range \\[200 - 299\\]. Error 503 is\nconsidered an App Engine system error instead of an application\nerror. Requests returning error 503 will be retried regardless of\nretry configuration and not counted against retry counts. Any other\nresponse code, or a failure to receive a response before the\ndeadline, constitutes a failed attempt.\n\n### [AppEngineRouting](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.AppEngineRouting)\n\nApp Engine Routing.\n\nFor more information about services, versions, and instances see `An\nOverview of App\nEngine \u003chttps://cloud.google.com/appengine/docs/python/an-overview-of-app-engine\u003e`**,\n`Microservices Architecture on Google App\nEngine \u003chttps://cloud.google.com/appengine/docs/python/microservices-on-app-engine\u003e`** ,\n`App Engine Standard request\nrouting \u003chttps://cloud.google.com/appengine/docs/standard/python/how-requests-are-routed\u003e`**,\nand `App Engine Flex request\nrouting \u003chttps://cloud.google.com/appengine/docs/flexible/python/how-requests-are-routed\u003e`**.\n\n### [CreateJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.CreateJobRequest)\n\nRequest message for\nCreateJob.\n\n### [DeleteJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.DeleteJobRequest)\n\nRequest message for deleting a job using\nDeleteJob.\n\n### [GetJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.GetJobRequest)\n\nRequest message for\nGetJob.\n\n### [HttpMethod](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.HttpMethod)\n\nThe HTTP method used to execute the job.\n\n### [HttpTarget](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.HttpTarget)\n\nHttp target. The job will be pushed to the job handler by means of\nan HTTP request via an\nhttp_method\nsuch as HTTP POST, HTTP GET, etc. The job is acknowledged by means\nof an HTTP response code in the range \\[200 - 299\\]. A failure to\nreceive a response constitutes a failed execution. For a redirected\nrequest, the response returned by the redirected request is\nconsidered.\n\nThis message has `oneof`_ fields (mutually exclusive fields).\nFor each oneof, at most one member field can be set at the same time.\nSetting any member of the oneof automatically clears all other\nmembers.\n\n.. _oneof: \u003chttps://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields\u003e\n\n### [Job](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.Job)\n\nConfiguration for a job.\nThe maximum allowed size for a job is 1MB.\n\nThis message has `oneof`_ fields (mutually exclusive fields).\nFor each oneof, at most one member field can be set at the same time.\nSetting any member of the oneof automatically clears all other\nmembers.\n\n.. _oneof: \u003chttps://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields\u003e\n\n### [ListJobsRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.ListJobsRequest)\n\nRequest message for listing jobs using\nListJobs.\n\n### [ListJobsResponse](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.ListJobsResponse)\n\nResponse message for listing jobs using\nListJobs.\n\n### [OAuthToken](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.OAuthToken)\n\nContains information needed for generating an `OAuth\ntoken \u003chttps://developers.google.com/identity/protocols/OAuth2\u003e`__.\nThis type of authorization should generally only be used when\ncalling Google APIs hosted on \\*.googleapis.com.\n\n### [OidcToken](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.OidcToken)\n\nContains information needed for generating an `OpenID Connect\ntoken \u003chttps://developers.google.com/identity/protocols/OpenIDConnect\u003e`__.\nThis type of authorization can be used for many scenarios, including\ncalling Cloud Run, or endpoints where you intend to validate the\ntoken yourself.\n\n### [PauseJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.PauseJobRequest)\n\nRequest message for\nPauseJob.\n\n### [PubsubTarget](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.PubsubTarget)\n\nPub/Sub target. The job will be delivered by publishing a\nmessage to the given Pub/Sub topic.\n\n### [ResumeJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.ResumeJobRequest)\n\nRequest message for\nResumeJob.\n\n### [RetryConfig](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.RetryConfig)\n\nSettings that determine the retry behavior.\n\nBy default, if a job does not complete successfully (meaning that an\nacknowledgement is not received from the handler, then it will be\nretried with exponential backoff according to the settings in\nRetryConfig.\n\n### [RunJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.RunJobRequest)\n\nRequest message for forcing a job to run now using\nRunJob.\n\n### [UpdateJobRequest](/python/docs/reference/cloudscheduler/latest/google.cloud.scheduler_v1beta1.types.UpdateJobRequest)\n\nRequest message for\nUpdateJob."]]