In order to use the Files API, an API client needs to be registered by an organization admin. When the client requests a bearer token, the client ID and secret need to be passed in either in the request body as parameters, or via basic auth with the client ID as the username and the secret as the password.

Properties:

  • allow_implicit_grant - (read-only)
  • created_at - (read-only)
  • creator_id - (read-only)
  • explicit_authorization_required - true/false, if true user will be shown prompts asking for permission for the client to access the user&39;s data.
  • id - (read-only)
  • name - (required)
  • organization_id - (read-only)
  • origins - comma-separated list of allowable origins
  • redirect_uris - comma-separated list o allowable redirect URIs
  • secret - (read-only)
  • updated_at (read-only)
  • whitelist_enabled - true/false, if true, only whitelisted users and groups will be able to use the client

GET and POST

GET, PUT, and DELETE

In order to add a user or group to a client&39;s whitelist, a client_authorization record needs to be created.

Properties:

  • client_id - the id of the client this
  • created_at - (read-only)
  • entity_id - the id of the user or group
  • entity_type - "user" or "group"
  • id - (read-only)
  • updated_at - (read-only)

GET and POST

GET and DELETE

Query Parameters (for GET):

  • client_id
  • entity_id
  • entity_type
Video player

Video

×

Reset your Password Password resets are handled on the Support Site

×