Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
An HTTP 200 response confirms that the request received a successful HTTP response; it does not, by itself, confirm that a post was saved in a public state or that readers can open it. To verify a WordPress post, inspect the response data, check the post record and its status, then test its returned link as a reader. Other APIs may use different fields and rules, so follow the documentation for the API you use.
What an HTTP 200 tells you—and what it does not
HTTP status and publishing state are separate pieces of evidence. WordPress’s REST API documentation says that it uses HTTP response codes to indicate API errors and that JSON is used for requests and responses, including error responses. A 200 therefore needs to be interpreted alongside the response body and the API’s documented behavior.
There is a WordPress.com-specific wrinkle: its post-creation documentation describes an optional http_envelope parameter. When enabled, this option forces the outer HTTP status to 200 and puts the real HTTP status and headers in a JSON envelope. For requests using that option, inspect the envelope rather than assuming the outer 200 is the underlying result. WordPress.com: Create a post
Check the saved WordPress post record
The WordPress REST API’s post schema includes an id, a status, and a link. The status is meaningful: the documented values include publish, future, draft, pending, and private. A returned post record is stronger evidence than the HTTP code alone, but you still need to check whether its status matches the outcome you intended.
#1 Best Overall
WordPress also documents a status property called public, which indicates whether posts with that status should be shown on the site’s front end. Use the status documentation to interpret visibility rather than assuming that any successfully created record is public. WordPress REST API: Statuses
Verify the post in a follow-up read
After creation, retrieve the post by its returned ID and inspect the current record. The documented WordPress endpoint is GET /wp/v2/posts/<id>; the API reference explains the post fields and retrieval endpoint. Confirm that the response identifies the expected post and that its current status is the one you intended. WordPress REST API: Posts
- Send the create request and inspect the response body, not just the HTTP status.
- Record the returned post ID and link, and check the post’s
status. - Request the post by ID with
GET /wp/v2/posts/<id>and verify the current record and status. - Check that the status is intended to be public, using WordPress’s documented status visibility property.
Test the public link separately
The post’s link field gives you a URL to check. Open or request that URL in a public context—without credentials, where appropriate—to see whether an unauthenticated reader can reach the post. Record what you actually tested: a reachable link is evidence of access in that context, not proof of search-engine indexing, immediate cache propagation, or availability to every reader.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Visibility can also depend on passwords, site configuration, and delivery behavior between the site and a reader. The WordPress references describe the API and post fields, but do not establish a universal guarantee that a returned link will be publicly accessible in every circumstance. The REST API overview covers its response format, errors, and public and private data. WordPress REST API Handbook: Reference
Rank #3
Apply the same principle to other APIs
The WordPress fields and endpoints above are a documented example, not a universal API convention. For another CMS or publishing service, consult its own documentation for how it represents creation results, saved status, identifiers, and public URLs. A successful HTTP exchange, a saved record, and reader access are distinct checks; the exact fields and steps vary by API.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
