Problem Statement:

Currently, a 403 Forbidden error returned by the API looks identical whether it's caused by (a) an API token lacking the required permissions, or (b) an attempt to update/retrieve spec-generated content through the standard content API, which is not permitted regardless of token scope. Users troubleshooting the error have no way to tell these two causes apart from the response itself, and may spend time adjusting token permissions when the actual issue is that the target content is spec-generated and must be updated via spec resync instead.

Suggested Enhancement:

Return a distinct, descriptive error code or message when a 403 occurs specifically because the requested content is spec-generated (e.g., "This content is spec-generated and cannot be modified via the content API. Update the API specification file and resync instead."), separate from the generic permissions-based 403.

Customer Benefit:

Reduces troubleshooting time and support tickets by letting developers immediately identify the correct fix path (token permission update vs. spec resync) rather than guessing from documentation alone.