Quickbase User Token API
The User Token API from Quickbase — 4 operation(s) for user token.
The User Token API from Quickbase — 4 operation(s) for user token.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/quickbase:quickbase-user-token-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Quickbase User Token API
version: 1.0.0
description: 'Operations tagged UserToken across 2 of this provider''s published API definitions: qb-openapi-v3.json, quickbase-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.quickbase.com/v1
tags:
- name: User Token
paths:
/usertoken/clone:
post:
tags:
- User Token
summary: Clone a user token
description: Clones the authenticated user token. All applications associated with that token are automatically associated with the new token.
operationId: cloneUserToken
parameters:
- $ref: '#/components/parameters/qbRealmHostname'
- $ref: '#/components/parameters/userAgent'
- $ref: '#/components/parameters/authorization'
requestBody:
content:
application/json:
schema:
type: object
properties:
name:
type: string
description: The new name for the cloned user token.
description:
type: string
description: The description for the cloned user token.
example:
name: My cloned user token
description: Cloned from user token A
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties:
active:
description: Whether the user token is active.
type: boolean
apps:
description: The list of apps this user token is assigned to.
type: array
items:
type: object
properties:
id:
description: The unique identifier for this application.
type: string
name:
description: The application's name.
type: string
lastUsed:
description: The last date this user token was used, in the ISO 8601 time format YYYY-MM-DDThh:mm:ss.sssZ (in UTC time zone).
type: string
description:
description: User Token description.
type: string
id:
description: User Token id.
type: integer
name:
description: User Token name.
type: string
token:
description: User Token value.
type: string
example:
active: true
apps:
- id: bpqe82s1
name: My first app
- id: bpqe82s2
name: My second app
lastUsed: '2020-03-27T18:34:12.000Z'
description: Cloned user token
id: 5
name: My cloned user token
token: token
servers:
- url: https://api.quickbase.com/v1
/usertoken/transfer:
post:
tags:
- User Token
summary: Transfer a user token
description: Transfers the specified user token. Application associations will remain intact. For security, permissions must manually be reconciled. Only realm or account admins can use this API.
operationId: transferUserToken
parameters:
- $ref: '#/components/parameters/qbRealmHostname'
- $ref: '#/components/parameters/userAgent'
- $ref: '#/components/parameters/authorization'
requestBody:
content:
application/json:
schema:
required:
- id
- from
- to
type: object
properties:
id:
type: number
description: The id of the user token to transfer
from:
type: string
description: The id of the user to transfer the user token from
to:
type: string
description: The id of the user to transfer the user token to
example:
id: 17658
from: 62341.tr3s
to: 123456.ab1s
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties:
active:
description: Whether the user token is active.
type: boolean
apps:
description: The list of apps this user token is assigned to.
type: array
items:
type: object
properties:
id:
description: The unique identifier for this application.
type: string
name:
description: The application's name.
type: string
lastUsed:
description: The last date this user token was used, in the ISO 8601 time format YYYY-MM-DDThh:mm:ss.sssZ (in UTC time zone).
type: string
description:
description: User Token description.
type: string
id:
description: User Token id.
type: integer
name:
description: User Token name.
type: string
example:
active: true
apps:
- id: bpqe82s1
name: My first app
- id: bpqe82s2
name: My second app
lastUsed: '2020-03-27T18:34:12.000Z'
description: Transferred user token
id: 5
name: My transferred user token
servers:
- url: https://api.quickbase.com/v1
/usertoken/deactivate:
post:
tags:
- User Token
summary: Deactivate a user token
description: Deactivates the authenticated user token. Once this is done, the user token must be reactivated in the user interface.
operationId: deactivateUserToken
parameters:
- $ref: '#/components/parameters/qbRealmHostname'
- $ref: '#/components/parameters/userAgent'
- $ref: '#/components/parameters/authorization'
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties:
id:
description: The user token id.
type: integer
example:
id: 5
servers:
- url: https://api.quickbase.com/v1
/usertoken:
delete:
tags:
- User Token
summary: Delete a user token
description: Deletes the authenticated user token. This is not reversible.
operationId: deleteUserToken
parameters:
- $ref: '#/components/parameters/qbRealmHostname'
- $ref: '#/components/parameters/userAgent'
- $ref: '#/components/parameters/authorization'
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties:
id:
description: The user token id.
type: integer
example:
id: 5
servers:
- url: https://api.quickbase.com/v1
components:
parameters:
authorization:
name: Authorization
in: header
description: The Quickbase authentication scheme you are using to authenticate the request, as described on the [authorization page](../auth).
required: true
schema:
type: string
example: QB-USER-TOKEN xxxxxx_xxx_xxxxxxxxxxxxxxxxxxxxxxx
qbRealmHostname:
name: QB-Realm-Hostname
in: header
description: Your Quickbase domain, for example demo.quickbase.com
required: true
schema:
type: string
example: demo.quickbase.com
userAgent:
name: User-Agent
in: header
description: This is entered by the person or utility invoking the API. You might custom create this or use the default one of your toolkit. Being descriptive here may offer more identification and troubleshooting capabilities.
schema:
type: string
example: FileService_Integration_V2.1
x-refined-from:
- qb-openapi-v3.json
- quickbase-openapi.yml