> ## Documentation Index
> Fetch the complete documentation index at: https://developer.fabric.inc/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a rulesets failure reports

> To view a report of failed compatibility rulesets, use the Get Compatibility Rulesets Failure Report endpoint. The returned `id` allows you to then call the Get Job Detail endpoint for in-depth `ruleset_failure_report` and `ruleset_error_report` details.



## OpenAPI

````yaml dropship_proposals.openapi get /v1/brands/{brand_id}/proposals/{id}/compatibility-rulesets-failure-reports/
openapi: 3.0.0
info:
  title: Proposals API
  version: 1.0.0
  description: |
    Endpoints for managing product proposals and their statuses.
servers:
  - url: https://marketplace-api.fabric.inc
    description: Production server
security:
  - Bearer: []
tags:
  - name: Proposals
    description: Proposal operations
paths:
  /v1/brands/{brand_id}/proposals/{id}/compatibility-rulesets-failure-reports/:
    get:
      tags:
        - Proposals
      summary: Get a rulesets failure reports
      description: >-
        To view a report of failed compatibility rulesets, use the Get
        Compatibility Rulesets Failure Report endpoint. The returned `id` allows
        you to then call the Get Job Detail endpoint for in-depth
        `ruleset_failure_report` and `ruleset_error_report` details.
      parameters:
        - name: brand_id
          in: path
          required: true
          schema:
            type: number
          description: >-
            The unique brand ID. In the Dropship UI this is called the
            **Supplier ID**. To find your Supplier ID, click your supplier name
            in the top nav.
          example:
            - 1249
        - name: id
          in: path
          required: true
          description: >-
            The unique proposal id. This ID is automatically generated when a
            proposal is created.
          schema:
            type: integer
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JobDetail'
components:
  schemas:
    JobDetail:
      type: object
      description: >-
        Represents the details of a background job or process, including its
        status, associated objects, and any generated reports.
      properties:
        id:
          type: integer
          format: int64
          description: The unique identifier for the job.
          example: 1762791
        content_type:
          type: integer
          description: >-
            An identifier for the type of content or operation the job relates
            to.
          example: 9
        object_id:
          type: integer
          format: int64
          description: >-
            The ID of the primary object associated with this job (e.g., a
            proposal or connection ID).
          example: 1298
        connection:
          type: object
          nullable: true
          description: Details of the connection related to this job, if any.
          example: null
        runtime_id:
          type: string
          format: uuid
          description: A unique identifier for the specific execution instance of the job.
          example: 3af6d254-066d-4a19-9f44-78d7f9ed28a2
        module_name:
          type: string
          description: The name of the module or function that executed this job.
          example: create_compatibility_rulesets_failure_report
        created_at:
          type: string
          format: date-time
          description: The timestamp when the job record was created.
          example: '2023-12-07T23:14:23.000Z'
        start_time:
          type: string
          format: date-time
          nullable: true
          description: The timestamp when the job started execution.
          example: null
        finish_time:
          type: string
          format: date-time
          nullable: true
          description: The timestamp when the job finished execution.
          example: null
        description:
          type: string
          nullable: true
          description: A human-readable description of the job.
          example: null
        total_success:
          type: integer
          nullable: true
          description: The total count of successful operations within the job.
          example: null
        total_failure:
          type: integer
          nullable: true
          description: The total count of failed operations within the job.
          example: null
        metadata:
          $ref: '#/components/schemas/MetadataItem'
        error_count:
          type: integer
          description: The number of errors encountered during the job's execution.
          example: 0
        error_logs:
          type: array
          description: A list of detailed error logs generated by the job.
          items:
            type: object
          example: []
    MetadataItem:
      type: object
      description: >-
        Represents a single metadata entry, often linking to external reports or
        files.
      properties:
        id:
          type: integer
          format: int64
          description: The unique identifier for this metadata entry.
          example: 17331237
        content_type:
          type: integer
          description: An identifier for the type of content this metadata relates to.
          example: 124
        object_id:
          type: integer
          format: int64
          description: >-
            The ID of the object this metadata is associated with (e.g., a job
            ID or proposal ID).
          example: 1762791
        type:
          type: string
          description: >-
            The data type of the 'value' field, indicating what kind of data is
            stored.
          example: string
        name:
          type: string
          description: >-
            A descriptive name for this metadata entry (e.g.,
            "ruleset_failure_report").
          example: ruleset_failure_report
        value:
          type: string
          format: uri
          description: The actual value of the metadata, often a URL to a resource.
          example: >-
            https://assets-staging.revcascade.com/temp_files/5d88c779-9bc5-4401-9073-024b106fe00a/Ruleset_Failure_Report_20231207_231424.csv
        created_at:
          type: string
          format: date-time
          description: The timestamp when this metadata entry was created.
          example: '2023-12-07T23:14:24.000Z'
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer

````