Freshteam · Authentication Profile

Freshteam Authentication

Authentication

Freshteam secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

Human ResourcesHRISApplicant TrackingATSRecruitingEmployee ManagementOnboardingTime OffHR SoftwareEnd of Life
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/freshteam-openapi.yml
summary:
  types:
  - http
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: 'Freshteam uses a per-account API token passed as a Bearer credential.
    An admin generates it in the Freshteam UI under profile icon > API Settings >
    Your API Key, then sends it on every request as `Authorization: Bearer [example key]`.
    Although Freshworks documents the flow under an OAuth 2.0 heading, in practice
    the token is a long-lived static account key rather than a short-lived
    per-user-authorized token.'
  sources:
  - openapi/freshteam-openapi.yml
  - https://developers.freshteam.com/api/
notes: >-
  Requests target the account-specific base https://{domain}.freshteam.com/api,
  where {domain} is the customer subdomain. As Freshworks sunsets Freshteam,
  new subscriptions and renewals are halted from March 7, 2026; API tokens
  remain valid only for existing accounts during their remaining term.