Sign in
App User Authentication

Using App User Authentication

To use App User Authentication, first obtain an App User, typically by using the configuration panel in the user interface, or else by using the App User API Resource. Once you have the token, you can apply it to any eligible action by prefixing the URL with /key/{appUser} as follows:

/v1/key/!Ms7V3$Zdnd63j5HFacIPFEvFAuwNqTUZW$AsVOmaQFf$vIC!F8dJjdgiDnJXXOt/example/request/path

(There is not really anything at /v1/example3; this section only demonstrates how generally to use App User Authentication.)

get/v1/key/{appUser}/example3

Path parameters

appUserstring required

The App User token. As with Session Bearer tokens, these tokens only contain URL-safe characters, so no escaping is required.

Response

OK

successboolean required

Example response

{
  "success": true
}

Changes

Changed in 2 of the 54 revisions of this API.2

  • 022694254f0d1See the full diff
    • ○

      api operation id Using App User Authentication removed and replaced with useAppUserAuthentication

      api-operation-id-removed

  • e8c2858fd4eb1See the full diff
    • ○

      api operation id useAppUserAuthentication removed and replaced with Using App User Authentication

      api-operation-id-removed

    This revision also has 11 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog