> ## Documentation Index > Fetch the complete documentation index at: https://developers.logicgate.ai/llms.txt > Use this file to discover all available pages before exploring further. # Validates all analysis values for a given record id > Runs through all Analysis Fields tied to the given Record id and compares values for each input. This results in verifying confidence is filled out and that values are in the scope of: minimum < most likely < maximum. Must have quantify access and permission to Record. ## OpenAPI ````yaml GET /api/v1/analyses/latest/records/{recordId}/validate openapi: 3.1.0 info: title: Risk Cloud API description: >- The Risk Cloud API is a collection of RESTful API endpoints that empower you and your team to directly integrate, automate, and build with the Risk Cloud. Risk Cloud API endpoint payloads are JSON based, with some endpoints supporting exports in CSV and XSLX formats for flexible integration. This API documentation showcases our Risk Cloud API v1, containing a variety of endpoints with continued support for enabling integrations with the Risk Cloud. Visit the [LogicGate Risk Cloud Developer Portal](https://www.logicgate.com/developer/) to get started with building your custom integration with quick start guides, usage guides, release notes, and more. Or download the [v1 OpenAPI specification](/legacy-openapi.json). Explore our [Risk Cloud API v2](https://docs.logicgate.com/v2/index.html) endpoints and documentation as well. [Risk Cloud API v2](https://docs.logicgate.com/v2/index.html) is our collection of API-First endpoints that are tailor made for our developer users, offer concise and highly documented details, are supported by a [Postman collection](https://www.postman.com/logicgate-postman/workspace/logicgate-risk-cloud-api/collection/29257227-de8d264b-6eeb-4177-bea6-2da0a8cabffc) and [v2 OpenAPI specification](https://github.com/LogicGateTech/openapi), and contain our latest API endpoint releases. contact: name: developer-relations@logicgate.com email: developer-relations@logicgate.com version: v2026.11.0 servers: - url: https://{subdomain}.logicgate.com description: Your Risk Cloud environment. variables: subdomain: description: Your Risk Cloud environment's subdomain (e.g. `qa`). default: your-instance security: - ApiToken: [] - basic: [] tags: - name: Authentication description: >- Getting Started: How to create an [API Access Token](https://www.logicgate.com/developer/risk-cloud-api-authentication/) to begin integrating with the Risk Cloud API - name: Attachment description: Endpoints for uploading, downloading, and retrieving record attachments. - name: Field description: Endpoints for creating, updating, and querying fields. - name: Principal description: >- Endpoints for the authenticated principal to view and manage their own details. - name: Record Audit description: Endpoints for retrieving record audit history and productivity data. - name: Step description: Endpoints for retrieving steps and the steps a user can access. - name: Table Report description: Endpoints for retrieving and managing table reports. - name: User Group description: Endpoints for managing user groups and their membership. externalDocs: description: Developer Portal url: https://www.logicgate.com/developer/ paths: /api/v1/analyses/latest/records/{recordId}/validate: get: tags: - Analysis summary: Validates all Analysis values for a given Record id. description: >- Runs through all Analysis Fields tied to the given Record id and compares values for each input. This results in verifying confidence is filled out and that values are in the scope of: minimum < most likely < maximum. Must have quantify access and permission to Record. operationId: getAnalysisValidationsForRecord parameters: - name: recordId in: path description: The ID of the record to get analysis validations for. required: true schema: type: string responses: '200': description: Success content: application/json: schema: $ref: >- #/components/schemas/AnalysisValidationResult_BasicAnalysisSummary '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/AppStatusResponse_BasicAnalysisSummary' components: schemas: AnalysisValidationResult_BasicAnalysisSummary: type: object properties: valid: type: boolean description: >- A flag whether this result is valid or not. Is used to determine whether a Record has any invalid Analysis Field values. errorMessages: type: array description: >- A list of error messages if the result is not valid. These error messages have a field id property, denoting which field has an invalid value, and a message property, describing the issue the aforementioned field is having. items: $ref: '#/components/schemas/AnalysisErrorMessage_BasicAnalysisSummary' required: - errorMessages - valid AppStatusResponse_BasicAnalysisSummary: type: object properties: type: type: string format: uri title: type: string status: type: integer format: int32 detail: type: string instance: type: string format: uri properties: type: object additionalProperties: {} AnalysisErrorMessage_BasicAnalysisSummary: type: object properties: analysisType: type: string description: >- The analysis type assigned to the invalid field. This analysis type will have an issue that needs to be resolved via one of its estimates field values. analysisEstimate: type: string description: >- The analysis estimate assigned to the invalid field. This analysis estimate field that was found to be invalid. fieldId: type: string description: >- The id of the invalid Field. This field will have an issue that needs to be resolved to run a proper FAIR analysis. sectionId: type: string description: >- The id of the section containing the field. This is used to link the user to the proper page and section of the record. parentId: type: string description: >- The id of the parent section of the section represented by sectionId. This is used to link the user to the proper page and section of the record. fieldValue: type: string description: >- The text value of the invalid field. This is used to inform the user how to fix the error. comparedAnalysisEstimate: type: string description: >- The analysis estimate that the invalid field was compared against. This is used to demonstrate why the field was determined to be invalid. comparedFieldId: type: string description: >- The id of the field whose value was compared against to determine if this field's value was invalid. This can be null if the field is invalid because it is empty. comparedSectionId: type: string description: >- The id of the compared field's section. This can be null if the field is invalid because it is empty. comparedParentId: type: string description: >- The id of the parent section of the compared field's section. This can be null if the field is invalid because it is empty. comparedFieldValue: type: string description: >- The value of the compared field. This can be null if the field is invalid because it is empty. message: type: string description: >- An error message for the invalid Field. This message contains details as to what is wrong with the associated Field id. required: - analysisEstimate - analysisType - comparedAnalysisEstimate - comparedFieldId - comparedFieldValue - comparedParentId - comparedSectionId - fieldId - fieldValue - message - parentId - sectionId securitySchemes: ApiToken: type: http scheme: bearer bearerFormat: API Token basic: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.