# Validating against RM schemas in the REST API

**Category:** [ITS](https://discourse.openehr.org/c/its/41)
**Created:** 2021-10-26 21:38 UTC
**Views:** 379
**Replies:** 0
**URL:** https://discourse.openehr.org/t/validating-against-rm-schemas-in-the-rest-api/1992

---

## Post #1 by @pablo

How are we handling differences in API request / response payloads to the schemas for canonical JSON and XML?

Some payloads won't validate against the schemas, for instance, missing contribution.uid on POST /contribution, or contribution.versions being a list of VERSION (API schema) instead of OBJECT_REF (RM schema).

Note in the case of the missing fields, like uids, that can be handled by a relaxed schema setting that as optional, but in the case of the OBJECT_REF to VERSION resolution, that is a totally different schema for the API not a relaxed one.

---


**Canonical:** https://discourse.openehr.org/t/validating-against-rm-schemas-in-the-rest-api/1992
**Original content:** https://discourse.openehr.org/t/validating-against-rm-schemas-in-the-rest-api/1992