Buildertrend Authentication API

Exchange your app's consumer key and secret for an access token. For a user sign-in token (PKCE), which comes from Buildertrend's sign-in service rather than this API, see the introduction above.

GitHub OpenAPI

Operations 1

POST /token Get an access token #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/buildertrend:buildertrend-authentication-api"
All apis
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.

Get an API 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 Specification

buildertrend-authentication-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Buildertrend Authentication API
  version: '1'
  description: 'Operations tagged Authentication across 2 of this provider''s published API definitions: buildertrend-open-api-reference.yml, buildertrend-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://developer.buildertrend.com/api
security:
- clientCredentials: []
tags:
- name: Authentication
  description: Exchange your app's consumer key and secret for an access token. For a user sign-in token (PKCE), which comes from Buildertrend's sign-in service rather than this API, see the introduction above.
paths:
  /token:
    post:
      tags:
      - Authentication
      operationId: getToken
      summary: Get an access token
      description: 'A standard OAuth 2.0 client credentials grant (RFC 6749 section 4.4). A request has two

        parts:


        - **Your credentials, in the `Authorization` header** (HTTP Basic). The username is your

        app''s consumer key and the password is its consumer secret. The header value is

        `Basic ` followed by `:` base64-encoded, not the plain

        text. Most HTTP clients build it for you; with curl, pass

        `-u "$CONSUMER_KEY:$CONSUMER_SECRET"`.

        - **`grant_type=client_credentials`, in the form body.** Every request needs it, however

        you send your credentials. It names the kind of grant; it is not a credential.


        If your HTTP client can''t do Basic auth, send the key and secret as `client_id` and

        `client_secret` form fields next to `grant_type` instead. Use one method for the

        credentials, not both.


        The token lasts 30 minutes (`expires_in: 1799`). It is opaque, not a JWT, so don''t decode

        it; use `expires_in`. There is no refresh token; request a new one when it expires. The

        secret is sent only here, never on an API call.'
      security:
      - consumerCredentials: []
      requestBody:
        required: true
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              required:
              - grant_type
              properties:
                grant_type:
                  type: string
                  enum:
                  - client_credentials
      responses:
        '200':
          description: Token issued.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TokenResponse'
        '400':
          description: '`unsupported_grant_type` (grant_type missing or not `client_credentials`), or `invalid_request` (wrong method or path).'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OAuthError'
        '401':
          description: '`invalid_client`: the key or secret is wrong. Check you have not swapped the key and the secret.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OAuthError'
    servers:
    - url: https://developer.buildertrend.com/api
components:
  schemas:
    TokenResponse:
      type: object
      required:
      - access_token
      - token_type
      - expires_in
      properties:
        access_token:
          type: string
          example: EXAMPLEtoken28CharsAbc123XyZ
        token_type:
          type: string
          example: Bearer
        expires_in:
          type: integer
          description: Seconds until the token expires.
          example: 1799
    OAuthError:
      type: object
      required:
      - error
      properties:
        error:
          type: string
          enum:
          - invalid_client
          - unsupported_grant_type
          - invalid_request
  securitySchemes:
    clientCredentials:
      type: oauth2
      description: 'Exchange your app''s consumer key and secret at `POST /token`, then send the returned token as `Authorization: Bearer <token>`.'
      flows:
        clientCredentials:
          tokenUrl: /api/token
          scopes: {}
    consumerCredentials:
      type: http
      scheme: basic
      description: Consumer key as the username, consumer secret as the password.
x-refined-from:
- buildertrend-open-api-reference.yml
- buildertrend-openapi.yml