Overview
As customers migrate to the Verato MDM Cloud platform, they may observe a change in API behavior related to how attributes are validated during postIdentity operations. This change may cause some API requests to be rejected.
This article outlines:
What changes to expect
Why certain API errors may occur
The updates customers must make to ensure continued API compatibility
How Verato Support and Customer Success can assist
This information applies to all customers who have completed or are in the process of migrating to Verato MDM Cloud.
1. API Errors for Unsupported Attributes in Standard Clusters
Why This Happens
The MDM Cloud platform enforces stricter validation rules on incoming postIdentity requests. If an API request includes attributes that are not supported, the MDM Cloud platform will reject the request.
On the current platform, unsupported attributes were often silently ignored. This behavior was unintentional and allowed invalid attributes to be included in requests without generating an error.
Importantly, these invalid attributes were never stored, even on the current platform—meaning they provided no value but also never surfaced an issue.
Common Symptoms
Customers may report:
API errors indicating an attribute is not allowed for a specific cluster
Requests that previously appeared to succeed now failing after migration
Required Customer Action
Customers must:
Review their integration payloads
Ensure only supported attributes—as defined in the Verato API documentation—are included
Remove or correct any unsupported fields being sent
2. API Errors for Custom Clusters Due to Missing or Unregistered Custom Attributes
Why This Happens
In MDM Cloud, all custom attributes must be explicitly registered in the MDM Console for the appropriate domain and environment(s).
API errors occur when customers include a custom attribute in a postIdentity request that is not registered in the environment’s metadata.
This happens when custom attributes were either:
Never populated on the legacy platform (and therefore not migrated or auto-registered), or
Never defined in the MDM Console.
In both cases, MDM Cloud rejects the request because the attribute is not recognized.
Common Symptoms
Customers may report:
Errors such as “attribute not supported,” “unknown attribute,” or “cluster does not support this attribute”
Failures only for attributes within custom clusters
Errors beginning immediately after migration
Required Customer Action
To resolve the issue, customers must provide:
The complete list of custom attributes expected within each custom cluster
Confirmation of which environments these attributes should be registered in
Verato Action
Once the customer provides this information, Verato will:
Register the missing custom attributes
Validate the cluster structure
Confirm successful API processing
What Customers Should Expect Going Forward
Verato will continue to strengthen validation, consistency, and data integrity across the MDM Cloud platform. During this transition, customers can expect:
Support for reviewing and validating API payload structures
Assistance registering missing custom attributes
Guidance to align integrations with updated API requirements
Continued improvements to reduce migration friction
If customers encounter unexpected API validation errors, encourage them to:
Capture the payload causing the issue
Provide the environment details
Submit the details to Verato Support
Comments
0 comments
Article is closed for comments.