---
schema_version: "1"
id: c296dc52ea76791ec9f33a8f63bc4d6d4b7bb8985f320fceba654d50116a270e
title: Validate Attribute Definitions (POST)
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/insurance_developer_guide/connect_resources_insurance_design_advisor_attribute_validation.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.insurance_developer_guide.meta/insurance_developer_guide/connect_resources_insurance_design_advisor_attribute_validation.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 751adb1f66f180c9e97f731962c07268b40b3aa7bfbb34c40c94780f228f4b23
description: Validate that attribute definitions exist in the org and are active, and return resolution guidance for any attribute that can’t be validated.
---
# Validate Attribute Definitions (POST)

Validate that attribute definitions exist in the org and are active, and return resolution guidance for any attribute that can’t be validated.

Use this resource at design time to confirm that attribute definitions referenced in a product model, constraint model, or request payload exist and are active. For each lookup, specify at least one of attributeId, attributeCode, or attributeName. The API resolves lookups by attribute ID, then attribute code, and then developer name, and returns results in the same order as the request.

A result sets isValid to true when the attribute definition exists and IsActive is true. When the attribute is invalid, instructions contains the resolution guidance. Those per-attribute failures are returned in the response body:

- SF-INS-DSAV-00030 — the attribute definition wasn’t found.
- SF-INS-DSAV-00031 — the attribute definition exists but isn’t active.
- SF-INS-DSAV-00032 — the lookup didn’t include an attribute ID, code, or developer name.

Specify contextDefinitionId when you need to resolve dynamic context attributes, such as names that start with DYN\_\_INS\_\_, against a context definition before the API looks up AttributeDefinition records. The API resolves lookups in bulk. Regardless of how many attributes you specify, it issues at most three queries, one for each identifier type, and then matches every lookup against those results.

Top-level errors are returned in errors when the request can’t be validated per attribute. A missing request body or an empty lookup list returns SF-INS-DSAV-00032 with HTTP status 400. Insufficient access, or Digital Insurance not enabled for the org, returns INSUFFICIENT\_ACCESS with HTTP status 403. An unexpected failure returns INTERNAL\_SERVER\_ERROR with HTTP status 500.

## Resource

/connect/insurance/design-advisor/attribute-validation

## Resource Example

Replace {yourInstance} with the My Domain name of your Salesforce org.

https://{yourInstance}.salesforce.com/services/data/v68.0/connect/insurance/design-advisor/attribute-validation

## Available Version

68.0

## HTTP Methods

POST

## Request Body for POST

### JSON Example

{
  "contextDefinitionId": "11Oxx0000004CXqEAM",
  "attributeLookups": \[
    {
      "attributeId": "0QPxx0000004CAAQ"
    },
    {
      "attributeCode": "Make"
    },
    {
      "attributeName": "Vehicle\_Model"
    },
    {
      "attributeCode": "SF-INS-DSAV-00032"
    },
    {}
  \]
}

### Properties

| Name | Type | Description | Required or Optional | Available Version |
| --- | --- | --- | --- | --- |
| attributeLookups | [Insurance Attribute Input](https://developer.salesforce.com/docs/atlas.en-us.insurance_developer_guide.meta/insurance_developer_guide/connect_requests_ins_attribute_input.htm "Input representation of one attribute definition to validate. Specify at least one of attribute ID, attribute code, or developer name.")\[\] | Attribute definitions to validate. Each entry identifies one attribute definition by ID, code, or developer name. The API confirms that each definition exists in the org and is active. Results are returned in the same order as this list. | Required | 68.0 |
| contextDefinitionId | String | ID of the context definition. When you specify this ID, dynamic context attributes, such as attributes whose names start with DYN\_\_INS\_\_, are resolved against that context definition’s dynamic-attributes catalog before the API looks up AttributeDefinition records. | Optional | 68.0 |

## Response Body for POST

[Insurance Attribute Validation Response](https://developer.salesforce.com/docs/atlas.en-us.insurance_developer_guide.meta/insurance_developer_guide/connect_responses_ins_attribute_validation.htm "Output representation of the per-attribute validation results. Each result reports whether the attribute definition exists and is active, and includes resolution guidance when it isn’t.")