What role should I give users to access the tables on the Rest API Explorer?

[peterraeves]

We are in the midst of creating an inbound web service, which an external customer could use to create incidents. Now, the customer asked for example code, which they could use. My first reaction was to create a user and give that user the 'rest_api_explorer' role so they could play around with the API and create sample code all by themselves. Now, I noticed that users with the 'rest_api_explorer' role cannot access the tables in the Import Set API...

I also noticed that the specific user we created could not create records in the Import Set. What role should they be given to create records in the staging table?

[Sanjeev Kumar1]

Hi,

you can use SOAP

and

rest_api_explorer and rest_service

[peterraeves]

- I do not want to use SOAP.

- rest_api_explorer is used to explore the REST API, hence the name, so it has no point to use in combination with SOAP...

- rest_service is deprecated...

[lss123]

I found that users trying the Import Set API got "no matches found" when trying to select a table.   By giving them the "import_transformer" role, they can view the list of tables.   I haven't verified if this gives them the ability to create records in staging tables, but I suspect it's either this or one of the other import_xxxx roles (I'd bet the import_admin role will do it).

[peterraeves]

That's indeed what I ended up doing.