What is Data Validation

Data validation can be thought of in two halves:

1. The validation that Edlink performs in order to arrive at a normalized, consistent set of data.
2. The validation that you can define to ensure that the data you receive from the LMS or SIS meets your specific requirements.

Default Data Validation

By default, Edlink validates and normalizes data that we receive from the LMS or SIS. We do this to ensure consistency and predicability across our APIs. Here are some examples of things we normalize by default:

• Dates and times
• Roles, grade levels, and other enumerated values
• Organizational structure (classes, courses, schools, etc.)
• Referential integrity (e.g. ensuring that an enrollment belongs to a valid person)

When retrieving data from our API, you can expect it to meet the format of our model defined in API Reference. Any additional properties that do not fit into the model will be ignored, or placed in the custom properties field.

Additional Data Validation

In addition to the default validation, you can also define custom validation rules for your data. This involves defining rules about your desired data format (e.g. email address cannot be empty). Rules can be defined at the application level (and apply to all integrations) or at the integration level (and apply to a specific integration). These rules run every time any data (or configuration) changes in Edlink.