Web API 403 error with account-type permissions

(0) Share

Report

Posted on by RK2021

I have successfully implemented a GET web API call on the accounts table, for which the user has global permissions.

However when making the same call to the contacts table, 403 is returned. The only difference is that the table permissions are account type, not global.

I just want to understand whether the table permission has to be global or if I need to add anything to the call when it's account type, such as a filter? Both account and contact tables have fields set to * in settings.

Thanks

Robert

Categories:

WEB API

All responses (1)

Answers (0)

Fubar 7,960 Super User 2025 Season 1 on at

Like (0)

Report

Re: Web API 403 error with account-type permissions

It is not clear exactly what you have setup from your description, or what the API call is that you are making .

In a nutshell...
If the portal user just needs to access their own record, then a Table Permission on with Scope = Self.

If the Portal User needs to access a record where there is a Lookup column populated with that Portal User (their contact record), then a Table Permission for the table that has the lookup with scope = Contact

If the Portal User needs to access a record where there is a Lookup column populated with that Portal User's parent Account , then a Table Permission for the table that has the lookup with scope = Account.

Beyond the above, you would use Scope = Parent (in the new interface child permissions), which gives access to child records based on the portal user already having access to the parent record.

Edit: for things to be secure, Global scope should be used sparingly often just for Reading and appending configuration data such as a a table of categories or types that users need to see all values to be able to select an appropriate one from the list.