REST API Response: (403) Forbidden

[howard53]

aircraft.66ghz.com

The error messages that I’m having issues with are as follows:

"When testing the REST API, an unexpected result was returned:

REST API Endpoint: https://aircraft.66ghz.com/wp-json/wp/v2/types/post?context=edit
REST API Response: (403) Forbidden
(please share the FULL error message you see, if applicable)"

How do I correct this error?

[anon95807532]

Hi howard53,

When 403, it’s because you are not authenticated from within the API. Your endpoint is related to editing a post, so meaning you need to have authenticated for the right to edit the post before reaching this.

Meanwhile, you also need to know that even if you logged in admin panel, you’re still considered unauthenticated in the REST API request, as you need to set some kind of token or authentication header in each request as per WordPress specification.

You might want to look that up here:

Authentication – REST API Handbook | Developer.WordPress.org

If you’re developing an application, you might also want to know about the security feature here on InfinityFree, which might be in your way if you attempt curl elsewhere, or outside of your existing session to the server.

Why do I see ?i=1 at the end of a URL

When you first open your website, you may see the extra characters like ?i=1 at the end of your URL. This article explains more about what causes it, and what you can do about it. What causes the ?i=1 suffix? This extra URL parameter is caused by a security system we use to protect your website. This security system ensures that your website can only be accessed through regular web browsers. What does the ?i=1 suffix do? The ?i=1 suffix is a counter. When you first load your website, some Ja…

Cheers!

[ChrisPAR]

I’m also suspecting the security system, I’ve shared my observations in a similar post:

Options missing when creating new blog posts on Wordpress

I could replicate the issue on a clean WordPress installation, on all default themes. What was interesting is that the feature would sometimes appear, and then disappear again. Having a look at the console, I noticed that it didn’t show up when some requests where failing, which I believe are internal REST API calls failing because of the security system (this is mentioned in the following article): One of the requests failing is wp-json/wp/v2/taxonomies, the request for taxonomies (tags and …

[howard53]

Thanks so much for responding so quickly, I’m looking into your suggestion as we speak. Again thanks

Howard53