Total Expert · OAuth Scopes

Total Expert OAuth Scopes

OAuth 2.0 searched

Total Expert publishes 5 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 Total Expert API on a user’s behalf.

Tokens are issued from https://public.totalexpert.net/v1/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.

CompanyFintechCRMMarketing AutomationMortgageBankingLendingCustomer Engagement

Scopes: 5 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://public.totalexpert.net/v1/authorize

Token URL
https://public.totalexpert.net/v1/token

Flows
clientCredentialsauthorizationCode

Scopes (5)

Scope	Description	Flows
crm	Documented example scope (Vendor OAuth Integration Guide authorize example)	authorizationCode, clientCredentials
leadInteraction	Lead interaction access (documented in the collection token examples)	authorizationCode, clientCredentials
leadSurveyInteraction	Lead survey interaction access (documented example in the Vendor OAuth Integration Guide)	authorizationCode, clientCredentials
loanInteraction	Loan interaction access (documented in the collection token examples)	authorizationCode, clientCredentials
postLeads	Post leads access (documented example in the Vendor OAuth Integration Guide)	authorizationCode, clientCredentials

📄 Provider scope reference: https://public.totalexpert.net/v1/docs/OAuth+Authorization+Guide.pdf

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: openapi/total-expert-openapi.yml
docs: https://public.totalexpert.net/v1/docs/OAuth+Authorization+Guide.pdf
notes: >-
  Total Expert does not publish a full scope registry. The /v1/authorize
  endpoint takes a required space-delimited `scope` parameter, and the token
  response echoes the granted `scope` list. The scope strings below are the
  ones the provider documents: crm, leadSurveyInteraction and postLeads appear
  in the Vendor OAuth Integration Guide examples; leadInteraction and
  loanInteraction appear in the Postman collection token examples. Integrations
  are provisioned scopes per client by Total Expert.
schemes:
- name: oauth2
  source: openapi/total-expert-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://public.totalexpert.net/v1/token
  - flow: authorizationCode
    authorizationUrl: https://public.totalexpert.net/v1/authorize
    tokenUrl: https://public.totalexpert.net/v1/token
  description: OAuth 2.0. Obtain a token from POST /v1/token using HTTP Basic (client_id:client_secret
    base64-encoded) plus a grant_type body. Access tokens are bearer tokens, expires_in 3600.
scopes:
- scope: crm
  description: Documented example scope (Vendor OAuth Integration Guide authorize example)
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/total-expert-openapi.yml
- scope: leadInteraction
  description: Lead interaction access (documented in the collection token examples)
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/total-expert-openapi.yml
- scope: leadSurveyInteraction
  description: Lead survey interaction access (documented example in the Vendor OAuth Integration
    Guide)
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/total-expert-openapi.yml
- scope: loanInteraction
  description: Loan interaction access (documented in the collection token examples)
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/total-expert-openapi.yml
- scope: postLeads
  description: Post leads access (documented example in the Vendor OAuth Integration Guide)
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/total-expert-openapi.yml