Buildertrend · OAuth Scopes

Buildertrend OAuth Scopes

OAuth 2.0 searched

Buildertrend publishes 4 OAuth 2.0 scopes via the clientCredentials and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Buildertrend API on a user’s behalf.

Tokens are issued from /api/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

ConstructionConstruction ManagementResidential ConstructionHome BuildersRemodelingSpecialty ContractorsProject ManagementJob CostingEstimatingSchedulingCRMProposalsChange OrdersPurchase OrdersInvoicingClient PortalSubcontractor PortalMobile AppSoftware-as-a-ServiceVertical SaaSConstruction Technology

Scopes: 4 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://login.buildertrend.com/authorize

Token URL
/api/token https://login.buildertrend.com/oauth/token

Flows
clientCredentialsauthorizationCode

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect sign-in scope, requested in the documented PKCE authorize URL.
profile	OpenID Connect profile claims, requested in the documented PKCE authorize URL.
email	OpenID Connect email claim, requested in the documented PKCE authorize URL.
offline_access	Requests a refresh token (refresh tokens rotate; 30 days, or 15 days without use).

📄 Provider scope reference: https://developer.buildertrend.com/apis/open-api

Source

OAuth Scopes

generated: '2026-11-11'
method: searched
source: openapi/buildertrend-openapi.yml
docs: https://developer.buildertrend.com/apis/open-api
schemes:
- name: clientCredentials
  source: openapi/buildertrend-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/token
  scopes: []
  description: Client-credentials tokens carry no scopes; access is the permissions of the linked Buildertrend user.
- name: userSignInPkce
  source: openapi/buildertrend-openapi.yml (info.description, PKCE sign-in example)
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.buildertrend.com/authorize
    tokenUrl: https://login.buildertrend.com/oauth/token
scopes:
- name: openid
  scheme: userSignInPkce
  description: OpenID Connect sign-in scope, requested in the documented PKCE authorize URL.
- name: profile
  scheme: userSignInPkce
  description: OpenID Connect profile claims, requested in the documented PKCE authorize URL.
- name: email
  scheme: userSignInPkce
  description: OpenID Connect email claim, requested in the documented PKCE authorize URL.
- name: offline_access
  scheme: userSignInPkce
  description: Requests a refresh token (refresh tokens rotate; 30 days, or 15 days without use).
note: The API has no resource-level scopes. What a token can read or write is the permissions of the Buildertrend user (linked account for client credentials; the signed-in person for PKCE). The four scopes above are sign-in (OIDC) scopes from the documented authorize URL.

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
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 scope set

curl "https://apis.io/api/v1/scopes/buildertrend-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.