Contents
I am trying to create a new choice (radio buttons) field using REST API request in my SharePoint Online environment and this is the code I’m using: However, I get ‘403 Forbidden’ as a response.
Are there any problems using rest in SharePoint?
I’m having a problems using REST to POST to a SharePoint List named Employees. I can get my code to GET data from the list, but when I try to POST data to the list it does not work.
How to avoid 403 error when using rest?
Alternatively you could use an API call to gain a formdigest value and use that in your header as per below. Credit where due i took this from an answer Vadim Gremyachev provided to the question here https://stackoverflow.com/questions/32435432/sharepoint-2013-via-rest-api-error-403-forbidden-when-trying-to-create-item
Why is 403 forbidden on post method of / REST / API 2?
If you’ve already registered, sign in. Otherwise, register and sign in. This issue also occurs with using ` /rest/auth/latest/session`. This is using AP.request to send the AJAX call (so CORS is not a factor). But the same POST request works with Postman (with only content-type json in the header).
401 Unauthorized. The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8).
How to solve 403 forbidden on post method of Jira?
Solved: 403 Forbidden on POST method of /rest/api/2/issue I am using the /rest/api/2/issue API of JIRA. I am successfully able to use Get for below URL
The first thing to check in this (and many other cases) is the Log files. It can be any error, e.g. your Login page is failing and trying to display an error page. Anonymous users not having access to the master page. I would suggest to take the reference of the below site. It worked well for me without issues. I’ve had this as well on my WebApp.
How to enable custom login in SharePoint Foundation?
If you have a custom login page that is using the Default MasterPage, then you might run into this issue. Option 1 is to give anonymous users access to the site (Visit Central Admin, click “Authentication Providers” on the “Application Management > Manage web applications” page; select the zone and select Anonymous Access checkbox.