# List replication rules

List all replication rules

Endpoint: GET /har/api/v1/replication/rules
Version: 1.0
Security: x-api-key

## Query parameters:

  - `space_ref` (string)
    Reference to the scope in which the registry exists.

## Response 200 fields (application/json):

  - `data` (object, required)
    A list of replication rules

  - `data.itemCount` (integer, required)
    The total number of items
    Example: 1

  - `data.pageCount` (integer, required)
    The total number of pages
    Example: 100

  - `data.pageIndex` (integer, required)
    The current page

  - `data.pageSize` (integer, required)
    The number of items per page
    Example: 10

  - `data.rules` (array, required)
    A list of Replication Rules

  - `data.rules.allowedPatterns` (array, required)

  - `data.rules.blockedPatterns` (array, required)

  - `data.rules.createdAt` (string, required)

  - `data.rules.destination` (any, required)

  - `data.rules.destinationType` (string, required)
    Enum: "Local", "Jfrog", "GCP"

  - `data.rules.identifier` (string, required)

  - `data.rules.modifiedAt` (string, required)

  - `data.rules.parentRef` (string, required)

  - `data.rules.source` (any, required)

  - `data.rules.sourceType` (string, required)
    Enum: "Local", "Jfrog", "GCP"

  - `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"


