An HTTP 200 response tells you about the HTTP exchange; by itself, it does not establish that a post was saved in a public state or that a reader can open it. For a WordPress example, verify the response body, the post’s ID and status, a fresh read of that record, and its public URL. Other APIs and content systems may use different fields and rules, so check the documentation for the API you use.
What does HTTP 200 actually tell you?
HTTP status and publishing outcome are separate layers of evidence. The WordPress REST API uses HTTP response codes to indicate API errors, but its reference also says the API uses JSON for requests and responses, including error responses. The response body can therefore carry information you would miss by looking only at the numeric status. See the WordPress REST API reference.
As an Amazon Associate I earn from qualifying purchases.
There is also a WordPress.com-specific wrinkle: its post-creation documentation describes an optional http_envelope parameter that forces the outer HTTP status to 200 while putting the real status code and headers in a JSON envelope. When using that option, inspect the envelope rather than assuming the outer status represents the underlying result. This documented behavior applies to that WordPress.com option, not to APIs generally. See WordPress.com’s create-a-post documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
What evidence shows a WordPress post was saved?
A WordPress post record exposes its own fields, including an id, a status, and a link. The ID identifies the record for a follow-up read; the status describes its publishing state; and the link gives you the post URL to check. These fields answer different questions, so none should be substituted for the others.
#1 Best Overall
The WordPress REST API documents these post status values: publish, future, draft, pending, and private. A response containing a post record is not enough to conclude that it is publicly viewable: interpret the returned status against the outcome you intended. The fields and create/retrieve endpoints are documented in the WordPress Posts reference.
How do you verify the post in WordPress?
- Inspect the whole create response. Read the response body as well as the HTTP status. If your WordPress.com request uses
http_envelope, check the envelope for the real status code and headers. - Record the returned post ID, link, and status. Confirm that the response identifies the expected post and that its status matches the result you intended. WordPress’s documented post statuses include
publish,future,draft,pending, andprivate. - Read the post again by ID. The WordPress API documents
GET /wp/v2/posts/<id>for retrieving a post. Check the returned record and its current status rather than relying only on the creation response. - Check whether that status is meant to show publicly. WordPress documents a
publicproperty for a status, defined as whether posts with that status should be shown on the site front end. Consult the WordPress Statuses reference when interpreting status visibility. - Test the returned link as a reader. Where appropriate, open or request the post URL without credentials. State exactly what you tested—for example, whether the URL opened for an unauthenticated request.
What does a public-link check prove—and what does it not?
A successful reader-side request is useful evidence that the tested URL was reachable in that context at that moment. It is not a universal guarantee of access for every reader or network, nor proof that search engines have indexed the post or that caches and other delivery layers have updated everywhere. Password protection, site configuration, visibility settings, and intermediate delivery behavior can affect what a reader sees. The WordPress API references describe the post fields and endpoints, but do not promise universal availability from a link check.
Rank #2
Keep the conclusion proportional to the check: report that the post record has the expected status, and separately report whether its URL opened without credentials. If you have only inspected the creation response, you have not yet established either the current saved state or reader access.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat if the API is not WordPress?
Do not assume another CMS or publishing API has WordPress’s status, public, id, or link fields, or the same meanings for HTTP responses. Use that API’s documentation to identify its application-level success signal, how to retrieve a created record, what state makes it public, and how to obtain and test the public URL. The evidence to distinguish remains the same in principle—HTTP exchange, application result, saved state, and reader access—but the exact fields and semantics are platform-specific.
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.
