Issue Summary

Differences between V1 and V2 for the /content endpoint.

The changes from V1 to V2 will bring unnecessary complexity, increase data storage costs, and are not practical for their app. They have provided details below about the specific endpoints that would be adversely affected by the migration to V2.

The functionality of the V2 API differs from V1. In V1, it could handle the content using the ID, irrespective of the content type, but in V2, it needs to be managed separately for each content type.

Steps to Reproduce

1. Call the mentioned endpoint and check the response;
2.  

Expected Results

There should be an V2 endpoint to allow this.

Actual Results

There are no existing endpoints to manage content using the ID. Using multiple API requests is inefficient and adds complexity, particularly for intricate apps.

Transitioning from V1 to V2 will add unwanted complexity, increase data storage costs, and isn't suitable for the partner's app.

Workaround

Continue to use the V1 endpoints, which are deprecated. This is not a valid workaround for long since these endpoints will soon no longer be accessible.