Search code examples
smartsheet-apismartsheet-api-2.0smartsheet-api-1.1

Do I need to be an admin to generate an API access token on free Smartsheet gov?


Do I need to be an admin to generate an API access token on free Smartsheet Gov?

I am currently an editor on smartsheet gov and have sharing permissions, but I cannot generate an access token. Do I need to be made an admin to be able to do this? Or does the plan need to be upgraded to a certain tier?

For regular smartsheet, the business plan allows people to make api calls, but sales told me that Smartsheet Gov is its own product so it's separate from plain smartsheet Business and Enterprise plans.

Any help would be greatly appreciated!!

Still looking through docs but haven't found anything yet.


Solution

  • If you're a "free" (unlicensed) user, then it's expected that you're unable to create an API token, as only licensed users can create API tokens. See here for related Q&A: https://community.smartsheet.com/discussion/44901/api-access-tokens-for-non-licensed-users -- although not specifically about Smartsheet.gov, seems like the same would apply to Smartsheet.gov.

    FYI, this page describes what I mean by "free" user and explains the different types of free users (i.e., unlicensed user vs free collaborator): help.smartsheet.com/articles/520100-user-types#toc-free-user. As far as I know, neither type of "free" user account will be allowed to create API access tokens.

    In response to the additional question you asked in a comment on your original post:

    • An API token is associated with (owned by) the user who logs into the Smartsheet app and creates it. This means that any API calls using that token will be issued by that user account.
    • While it would be possible for a licensed user to generate an API token and then communicate its value to you for you to use in whatever script you're creating -- any API calls that are issued using that token will be issued as the token owner (user account). Amongst other things, this means that those API calls will only be able to access the sheets that the token owner has access to, with the permissions / access rights of that token owner. This could be problematic if/when your script needs to access a sheet that the token owner doesn't have access to, or needs to access a sheet with greater permissions than the token owner possesses.