Harver · Authentication Profile

Harver Authentication

Authentication

Harver secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyHRHR TechRecruitingHiringTalent IntelligencePre-Employment AssessmentCandidate ExperienceApplicant Tracking
Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

OAuth2ClientCredentials oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://api.harver.com/docs
docs: https://api.harver.com/docs#tag/oauth
summary:
  types: [oauth2]
  oauth2_flows: [clientCredentials]
  token_type: Bearer
  access_token_ttl_seconds: 3600
notes: >-
  The Harver Public API uses OAuth2 client_credentials. The client_id and
  client_secret are provisioned by Harver per environment (Test / Production);
  the API is available only to Harver customers. Security schemes are not
  declared in the components of the published OpenAPI, so this profile is
  captured from the documented authentication section rather than derived.
schemes:
- name: OAuth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  token_url: https://api.harver.com/oauth/token
  token_url_test: https://api.harver-test.com/oauth/token
  grant_type: client_credentials
  content_type: application/x-www-form-urlencoded
  request_body:
    grant_type: client_credentials
    client_id: '{provided by Harver}'
    client_secret: '{provided by Harver}'
  usage: 'Authorization: Bearer {access_token}'
  scopes: []
environments:
- name: Production
  base_url: https://api.harver.com
- name: Test
  base_url: https://api.harver-test.com