Safe API Post Test for Doc Sansar CMS

Introduction

This is a safe API test post for Doc Sansar CMS. It verifies that external posting now creates content using the correct database structure. The API should always set a valid author, save the article body into the body column, connect the post to a real category through category_id, and sync tags through the post_tag pivot table instead of storing raw tag JSON inside the posts table.

Why this matters

Public pages in a Laravel CMS often expect relationships such as author, category, and tags. If an external API stores category or tags as plain strings in columns that share the same names as relationships, Blade templates can fail when a published post is opened. A safe API must therefore normalize incoming data before saving it and must keep risky external content as draft until an admin reviews it.

Expected result

After this request succeeds, the post should appear in the admin panel as a draft. It should have a valid author, a proper category relation, clean body content, SEO fields, and synchronized tags. The public blog should not break because the post is not directly published and because raw category and tags fields are not filled by the API.

Conclusion

This test confirms that the external posting API is now safer, more scalable, and ready for controlled AI-assisted content workflows.