# Create a new module execution

Create a new module execution.

Endpoint: POST /iacm/api/modules/{moduleId}/executions
Version: 1.0
Security: x-api-key

## Path parameters:

  - `moduleId` (string, required)
    The unique identifier for the associated module
    Example: "Impedit fugiat officiis sunt ullam."

## Request fields (application/json):

  - `account` (string, required)
    Account is the internal customer account ID.
    Example: "a"

  - `org` (string, required)
    Org is the organisation identifier.
    Example: "fyc"

  - `pipeline` (string, required)
    The unique identifier for the associated pipeline
    Example: "Laudantium neque incidunt quasi."

  - `pipelineExecutionId` (string, required)
    The unique identifier for the associated pipeline execution
    Example: "Ad qui iusto autem voluptatem."

  - `pipelineStageId` (string, required)
    The unique identifier for the associated pipeline stage
    Example: "Fugit praesentium quia."

  - `project` (string, required)
    Project is the project identifier.
    Example: "j"

## Response 200 fields (application/json):

  - `account` (string, required)
    Account is the internal customer account ID.
    Example: "t"

  - `created` (integer, required)
    Created is the unix timestamp at which the resource was originally created in milliseconds.
    Example: 6563471650358445000

  - `metadata` (object)
    Example: {"pipeline":"Dignissimos inventore quis voluptas impedit id incidunt.","pipeline_execution_id":"Quis debitis esse.","pipeline_execution_number":"Ut repellendus.","pipeline_name":"Tempora officiis dolorem.","pipeline_stage_id":"Dolor tempora facere unde maxime eos.","trigger":{"Iusto qui reprehenderit qui voluptates.":"Et nam sit voluptatem quae error.","Quia quas est voluptas accusamus.":"Doloremque inventore necessitatibus accusamus dolorem est."}}

  - `metadata.pipeline` (string)
    The unique identifier of any associated pipeline
    Example: "Dignissimos inventore quis voluptas impedit id incidunt."

  - `metadata.pipeline_execution_id` (string)
    The unique identifier for any associated pipeline execution
    Example: "Quis debitis esse."

  - `metadata.pipeline_execution_number` (string)
    The unique number for any associated pipeline execution
    Example: "Ut repellendus."

  - `metadata.pipeline_name` (string)
    The name of any associated pipeline
    Example: "Tempora officiis dolorem."

  - `metadata.pipeline_stage_id` (string)
    The unique identifier for the associated pipeline stage
    Example: "Dolor tempora facere unde maxime eos."

  - `metadata.trigger` (object)
    Trigger info for any associated pipeline execution
    Example: {"Iusto qui reprehenderit qui voluptates.":"Et nam sit voluptatem quae error.","Quia quas est voluptas accusamus.":"Doloremque inventore necessitatibus accusamus dolorem est."}

  - `moduleId` (string, required)
    The unique identifier for the associated module
    Example: "Et ut."

  - `org` (string, required)
    Org is the organisation identifier.
    Example: "w"

  - `project` (string, required)
    Project is the project identifier.
    Example: "xw"

  - `status` (string, required)
    The overall status of the execution
    Example: "Laudantium et corporis cumque ea."

## Response 400 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 401 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 403 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 404 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 408 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 409 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 423 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 499 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 500 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true

## Response 502 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?

  - `timeout` (boolean, required)
    Is the error a timeout?
    Example: true