Issue Summary

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Try to create or read a content property on a draft page or blog post using the V2 REST API
2. Receive something back like: 404 / Could not find <entity> with id [...]

Expected Results

This functionality should be possible, as it is possible with V1. 

Actual Results

Receive back a 404, or in some cases a 500.

Workaround

Continue to use V1, which is not a long term solution as these endpoints are marked for deprecation, and the recommended replacement is V2.