# ReTriggerWebhookExecution

Retrigger Webhook Execution

Endpoint: GET /har/api/v1/registry/{registry_ref}/webhooks/{webhook_identifier}/executions/{webhook_execution_id}/retrigger
Version: 1.0
Security: x-api-key

## Path parameters:

  - `registry_ref` (string, required)
    Reference to the scope in which the registry exists.

Format depends on the scope:

- Account-level: account_id/registry_name/+
- Organization-level: account_id/org_id/registry_name/+
- Project-level: account_id/org_id/project_id/registry_name/+

The /+ suffix is used internally to route scoped requests.
It must be included exactly as shown in the URL.

  - `webhook_identifier` (string, required)
    Unique webhook identifier.

  - `webhook_execution_id` (string, required)
    Unique webhook execution identifier.

## Response 200 fields (application/json):

  - `data` (object, required)
    Harness Regstries Webhook Execution

  - `data.created` (integer)

  - `data.duration` (integer)

  - `data.error` (string)

  - `data.id` (integer)

  - `data.request` (object)
    Harness Regstries HTTP Webhook Request

  - `data.request.body` (string)

  - `data.request.headers` (string)

  - `data.request.url` (string)

  - `data.response` (object)
    Harness Regstries HTTP Webhook Response

  - `data.response.body` (string)

  - `data.response.headers` (string)

  - `data.response.status` (string)

  - `data.response.statusCode` (integer)

  - `data.result` (string)
    refers to webhook execution
    Enum: "SUCCESS", "RETRIABLE_ERROR", "FATAL_ERROR"

  - `data.retriggerOf` (integer)

  - `data.retriggerable` (boolean)

  - `data.triggerType` (string)
    refers to trigger
    Enum: "ARTIFACT_CREATION", "ARTIFACT_DELETION"

  - `data.webhookId` (integer)

  - `status` (string, required)
    Request processing status indicator
    Enum: "SUCCESS", "FAILURE", "ERROR"

## Response 400 fields (application/json):

  - `code` (string, required)
    The HTTP error code
    Example: "404"

  - `details` (object)
    Additional context and details about the error.
May include field-specific validation errors or debugging information.
    Example: {"field":"registry_identifier","reason":"Registry does not exist in the specified project","value":"invalid-registry"}

  - `message` (string, required)
    Human-readable error message explaining what went wrong
    Example: "Registry not found"