TeamOhana · Authentication Profile

Teamohana Authentication

Authentication

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

CompanyHR TechHeadcount ManagementHeadcount PlanningWorkforce PlanningHuman ResourcesTalent AcquisitionFinanceSCIMSoftware-as-a-Service
Methods: http Schemes: 1 OAuth flows: API key in: header

Security Schemes

Authorization http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/teamohana-openapi-original.json
docs: https://api.teamohana.us/faq/index.html
notes: >-
  Bearer token authentication via the Authorization header
  (`Authorization: Bearer YOUR_API_KEY`). Per the API FAQ, the SCIM API and the
  Headcount API use SEPARATE API keys — ensure the correct key is used for each
  surface. Keys are provisioned by TeamOhana; contact support to obtain them.
summary:
  types:
  - http
  api_key_in:
  - header
schemes:
- name: Authorization
  type: http
  scheme: bearer
  bearer_format: api-key
  sources:
  - openapi/teamohana-openapi-original.json

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact 
curl "https://apis.io/api/v1/security/teamohana-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.