Use this endpoint to validate that tables and fields referenced in the request exist in the configured data sources. This is useful for verifying schema mappings before creating data extraction jobs.
Important: The mappedFields object uses configName (the unique name you assigned to the connection) as the key — not the connection UUID. This differs from other endpoints that use the id path parameter.
The authorization token in the Bearer <token> format.
Important: This header is required if your environment has Access Manager enabled. For more information, refer to the Access Manager documentation.
"Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
Request body for validating schema mappings against configured data sources. Use configName (not the connection UUID) as the key in mappedFields.
Object containing the field mapping configuration. The structure is: { configName: { tableName: [field1, field2, ...] } }. Use the connection's configName as the top-level key.
{
"midaz_onboarding": {
"organization": ["id", "legal_name", "status"],
"ledger": ["id", "organization_id", "name"]
}
}The result of the schema validation.
Response object containing the result of schema validation.
The validation result status. Returns success when all fields are valid, or failure when validation errors are found.
success, failure "success"
A human-readable summary of the validation result.
"All fields validated successfully"
A list of validation errors found during schema validation. Empty when status is success.