openapi: 3.0.0 info: version: '2015-07-09' x-release: v4 title: 'AWS CodePipeline Executions #X Amz Target=CodePipeline 20150709.AcknowledgeThirdPartyJob API' description: CodePipeline

Overview

This is the CodePipeline API Reference. This guide provides descriptions of the actions and data types for CodePipeline. Some functionality for your pipeline can only be configured through the API. For more information, see the CodePipeline User Guide.

You can use the CodePipeline API to work with pipelines, stages, actions, and transitions.

Pipelines are models of automated release processes. Each pipeline is uniquely named, and consists of stages, actions, and transitions.

You can work with pipelines by calling:

Pipelines include stages. Each stage contains one or more actions that must complete before the next stage begins. A stage results in success or failure. If a stage fails, the pipeline stops at that stage and remains stopped until either a new version of an artifact appears in the source location, or a user takes action to rerun the most recent artifact through the pipeline. You can call GetPipelineState, which displays the status of a pipeline, including the status of stages in the pipeline, or GetPipeline, which returns the entire structure of the pipeline, including the stages of that pipeline. For more information about the structure of stages and actions, see CodePipeline Pipeline Structure Reference.

Pipeline stages include actions that are categorized into categories such as source or build actions performed in a stage of a pipeline. For example, you can use a source action to import artifacts into a pipeline from a source such as Amazon S3. Like stages, you do not work with actions directly in most cases, but you do define and interact with actions when working with pipeline operations such as CreatePipeline and GetPipelineState. Valid action categories are:

Pipelines also include transitions, which allow the transition of artifacts from one stage to the next in a pipeline after the actions in one stage complete.

You can work with transitions by calling:

Using the API to integrate with CodePipeline

For third-party integrators or developers who want to create their own integrations with CodePipeline, the expected sequence varies from the standard API user. To integrate with CodePipeline, developers need to work with the following items:

Jobs, which are instances of an action. For example, a job for a source action might import a revision of an artifact from a source.

You can work with jobs by calling:

Third party jobs, which are instances of an action created by a partner action and integrated into CodePipeline. Partner actions are created by members of the Amazon Web Services Partner Network.

You can work with third party jobs by calling:

x-logo: url: https://twitter.com/awscloud/profile_image?size=original backgroundColor: '#FFFFFF' termsOfService: https://aws.amazon.com/service-terms/ contact: name: Mike Ralphson email: mike.ralphson@gmail.com url: https://github.com/mermade/aws2openapi x-twitter: PermittedSoc license: name: Apache 2.0 License url: http://www.apache.org/licenses/ x-providerName: amazonaws.com x-serviceName: codepipeline x-origin: - contentType: application/json url: https://raw.githubusercontent.com/aws/aws-sdk-js/master/apis/codepipeline-2015-07-09.normal.json converter: url: https://github.com/mermade/aws2openapi version: 1.0.0 x-apisguru-driver: external x-apiClientRegistration: url: https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_ct x-apisguru-categories: - cloud x-preferred: true servers: - url: http://codepipeline.{region}.amazonaws.com variables: region: description: The AWS region enum: - us-east-1 - us-east-2 - us-west-1 - us-west-2 - us-gov-west-1 - us-gov-east-1 - ca-central-1 - eu-north-1 - eu-west-1 - eu-west-2 - eu-west-3 - eu-central-1 - eu-south-1 - af-south-1 - ap-northeast-1 - ap-northeast-2 - ap-northeast-3 - ap-southeast-1 - ap-southeast-2 - ap-east-1 - ap-south-1 - sa-east-1 - me-south-1 default: us-east-1 description: The CodePipeline multi-region endpoint - url: https://codepipeline.{region}.amazonaws.com variables: region: description: The AWS region enum: - us-east-1 - us-east-2 - us-west-1 - us-west-2 - us-gov-west-1 - us-gov-east-1 - ca-central-1 - eu-north-1 - eu-west-1 - eu-west-2 - eu-west-3 - eu-central-1 - eu-south-1 - af-south-1 - ap-northeast-1 - ap-northeast-2 - ap-northeast-3 - ap-southeast-1 - ap-southeast-2 - ap-east-1 - ap-south-1 - sa-east-1 - me-south-1 default: us-east-1 description: The CodePipeline multi-region endpoint - url: http://codepipeline.{region}.amazonaws.com.cn variables: region: description: The AWS region enum: - cn-north-1 - cn-northwest-1 default: cn-north-1 description: The CodePipeline endpoint for China (Beijing) and China (Ningxia) - url: https://codepipeline.{region}.amazonaws.com.cn variables: region: description: The AWS region enum: - cn-north-1 - cn-northwest-1 default: cn-north-1 description: The CodePipeline endpoint for China (Beijing) and China (Ningxia) security: - hmac: [] tags: - name: '#X Amz Target=CodePipeline 20150709.AcknowledgeThirdPartyJob' paths: /#X-Amz-Target=CodePipeline_20150709.AcknowledgeThirdPartyJob: parameters: - $ref: '#/components/parameters/X-Amz-Content-Sha256' - $ref: '#/components/parameters/X-Amz-Date' - $ref: '#/components/parameters/X-Amz-Algorithm' - $ref: '#/components/parameters/X-Amz-Credential' - $ref: '#/components/parameters/X-Amz-Security-Token' - $ref: '#/components/parameters/X-Amz-Signature' - $ref: '#/components/parameters/X-Amz-SignedHeaders' post: operationId: AcknowledgeThirdPartyJob description: Confirms a job worker has received the specified job. Used for partner actions only. responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/AcknowledgeThirdPartyJobOutput' examples: AcknowledgeThirdPartyJob200Example: summary: Default AcknowledgeThirdPartyJob 200 response x-microcks-default: true value: status: ACTIVE '480': description: ValidationException content: application/json: schema: $ref: '#/components/schemas/ValidationException' examples: AcknowledgeThirdPartyJob480Example: summary: Default AcknowledgeThirdPartyJob 480 response x-microcks-default: true value: example-value '481': description: InvalidNonceException content: application/json: schema: $ref: '#/components/schemas/InvalidNonceException' examples: AcknowledgeThirdPartyJob481Example: summary: Default AcknowledgeThirdPartyJob 481 response x-microcks-default: true value: example-value '482': description: JobNotFoundException content: application/json: schema: $ref: '#/components/schemas/JobNotFoundException' examples: AcknowledgeThirdPartyJob482Example: summary: Default AcknowledgeThirdPartyJob 482 response x-microcks-default: true value: example-value '483': description: InvalidClientTokenException content: application/json: schema: $ref: '#/components/schemas/InvalidClientTokenException' examples: AcknowledgeThirdPartyJob483Example: summary: Default AcknowledgeThirdPartyJob 483 response x-microcks-default: true value: example-value requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/AcknowledgeThirdPartyJobInput' examples: AcknowledgeThirdPartyJobRequestExample: summary: Default AcknowledgeThirdPartyJob request x-microcks-default: true value: jobId: '500123' nonce: example-value clientToken: example-value parameters: - name: X-Amz-Target in: header required: true schema: type: string enum: - CodePipeline_20150709.AcknowledgeThirdPartyJob summary: Amazon CodePipeline Acknowledge Third Party Job x-microcks-operation: delay: 0 dispatcher: FALLBACK tags: - '#X Amz Target=CodePipeline 20150709.AcknowledgeThirdPartyJob' components: schemas: JobNotFoundException: {} AcknowledgeThirdPartyJobInput: type: object required: - jobId - nonce - clientToken title: AcknowledgeThirdPartyJobInput properties: jobId: allOf: - $ref: '#/components/schemas/ThirdPartyJobId' - description: The unique system-generated ID of the job. nonce: allOf: - $ref: '#/components/schemas/Nonce' - description: A system-generated random number that CodePipeline uses to ensure that the job is being worked on by only one job worker. Get this number from the response to a GetThirdPartyJobDetails request. clientToken: allOf: - $ref: '#/components/schemas/ClientToken' - description: The clientToken portion of the clientId and clientToken pair used to verify that the calling entity is allowed access to the job and its details. description: Represents the input of an AcknowledgeThirdPartyJob action. InvalidClientTokenException: {} ValidationException: {} InvalidNonceException: {} Nonce: type: string minLength: 1 maxLength: 50 ThirdPartyJobId: type: string minLength: 1 maxLength: 512 AcknowledgeThirdPartyJobOutput: type: object properties: status: allOf: - $ref: '#/components/schemas/JobStatus' - description: The status information for the third party job, if any. description: Represents the output of an AcknowledgeThirdPartyJob action. ClientToken: type: string minLength: 1 maxLength: 256 JobStatus: type: string enum: - Created - Queued - Dispatched - InProgress - TimedOut - Succeeded - Failed parameters: X-Amz-Signature: name: X-Amz-Signature in: header schema: type: string required: false X-Amz-Algorithm: name: X-Amz-Algorithm in: header schema: type: string required: false X-Amz-Security-Token: name: X-Amz-Security-Token in: header schema: type: string required: false X-Amz-Content-Sha256: name: X-Amz-Content-Sha256 in: header schema: type: string required: false X-Amz-Date: name: X-Amz-Date in: header schema: type: string required: false X-Amz-SignedHeaders: name: X-Amz-SignedHeaders in: header schema: type: string required: false X-Amz-Credential: name: X-Amz-Credential in: header schema: type: string required: false securitySchemes: hmac: type: apiKey name: Authorization in: header description: Amazon Signature authorization v4 x-amazon-apigateway-authtype: awsSigv4 externalDocs: description: Amazon Web Services documentation url: https://docs.aws.amazon.com/codepipeline/ x-hasEquivalentPaths: true