Skip to main content

Prerequisites

  1. API Key created in StackOne Dashboard and copied to a secure location
  2. Basic Authentication Setup - Learn how to properly authenticate with StackOne API using your API key
  3. Required provider integration enabled
  4. Account linked successfully
  5. (Optional) Use an SDK

Getting Account ID

Authentication: When using curl -u "$API_KEY:", encoding is handled automatically. When setting the Authorization header manually, base64 encode {api_key}:, your key followed by a colon. See Authentication for details.
  1. List your linked accounts to find the account ID:
  1. From the response, copy the id value for your desired provider account.
Filter by provider using the providers query parameter:

Making your first request

Check whether a user can read a specific resource. Replace the placeholder values with your own account ID, user identifier, and resource ID.

Example response

Reading the response

  • user.permissions: the full set of permissions this user holds on the resource. Always present.
  • allowed: only present when you sent an action. true if the action is in user.permissions.
  • resource.type: the resolved resource type used for the check.

When allowed is false

When the user doesn’t have access, the response returns 200 with an empty user.permissions array and allowed: false:
This is not an error. It’s a valid response indicating the user does not have the requested access.

Next steps

Check Permissions reference

Full request/response schema, resource ID formats, and error codes

List Resource Types

Discover which resource types the connected provider supports