TeamOhana website screenshot

TeamOhana

TeamOhana is an HR-technology company that provides a headcount management and planning platform serving as a single source of truth for a company's people budget. It connects Finance, HR, and Talent Acquisition teams around real-time, approved headcount so organizations can plan, track, and control hiring against budget in one collaborative workflow rather than across disconnected spreadsheets. The platform integrates with HRIS, ATS, and financial planning systems (Workday, SAP SuccessFactors, Bamboo HR, HiBob, UKG, Personio, Namely, Greenhouse-class ATS, and Pigment). Its Public API exposes SCIM 2.0 user provisioning plus Headcount, Discovery, and Scenario endpoints for planning and reporting. TeamOhana is backed by Sierra Ventures and runs a security program that is SOC 2 and ISO 27001 certified (verified via its public trust center).

TeamOhana publishes 4 APIs on the APIs.io network, including Discovery API, Headcount API, Scenario API, and 1 more. Tagged areas include Company, HR Tech, Headcount Management, Headcount Planning, and Workforce Planning.

TeamOhana’s developer surface includes authentication, documentation, API reference, pricing, engineering blog, signup flow, support, and 19 more developer resources.

48.5/100 developing ▬ flat Agent 26/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyHR TechHeadcount ManagementHeadcount PlanningWorkforce PlanningHuman ResourcesTalent AcquisitionFinanceSCIMSoftware-as-a-Service

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/teamohana: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

TeamOhana Discovery API

The Discovery API from TeamOhana — 3 operation(s) for discovery.

TeamOhana Headcount API

The Headcount API from TeamOhana — 2 operation(s) for headcount.

TeamOhana Scenario API

The Scenario API from TeamOhana — 2 operation(s) for scenario.

TeamOhana SCIM API

The SCIM API from TeamOhana — 3 operation(s) for scim.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Rate Limits 1

Documented rate limits and quota policies.

Teamohana Rate Limits

1 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Teamohana Authentication

http · 1 scheme

SECURITY

Teamohana Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Teamohana Trust Center

SOC 2, ISO 27001

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Teamohana Agentic Access

14 operations · 5 acting

14 operations · 5 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: teamohana
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/teamohana.png
name: TeamOhana
description: TeamOhana is an HR-technology company that provides a headcount management and planning platform serving as a
  single source of truth for a company's people budget. It connects Finance, HR, and Talent Acquisition teams around real-time,
  approved headcount so organizations can plan, track, and control hiring against budget in one collaborative workflow rather
  than across disconnected spreadsheets. The platform integrates with HRIS, ATS, and financial planning systems (Workday,
  SAP SuccessFactors, Bamboo HR, HiBob, UKG, Personio, Namely, Greenhouse-class ATS, and Pigment). Its Public API exposes
  SCIM 2.0 user provisioning plus Headcount, Discovery, and Scenario endpoints for planning and reporting. TeamOhana is backed
  by Sierra Ventures and runs a security program that is SOC 2 and ISO 27001 certified (verified via its public trust center).
url: https://raw.githubusercontent.com/api-evangelist/teamohana/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- sierra-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- HR Tech
- Headcount Management
- Headcount Planning
- Workforce Planning
- Human Resources
- Talent Acquisition
- Finance
- SCIM
- Software-as-a-Service
tags_raw:
- Company
- Hr Tech
- Headcount Management
- Headcount Planning
- Workforce Planning
- Human Resources
- Talent Acquisition
- Finance
- SCIM
- SaaS
apis:
- aid: teamohana:teamohana-discovery-api
  name: TeamOhana Discovery API
  description: The Discovery API from TeamOhana — 3 operation(s) for discovery.
  humanURL: https://api.teamohana.us/faq/index.html
  baseURL: https://api.teamohana.us
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/teamohana-discovery-api-openapi.yml
  - type: Documentation
    url: https://api.teamohana.us/faq/index.html
  - type: APIReference
    url: https://api.teamohana.us/faq/index.html
- aid: teamohana:teamohana-headcount-api
  name: TeamOhana Headcount API
  description: The Headcount API from TeamOhana — 2 operation(s) for headcount.
  humanURL: https://api.teamohana.us/faq/index.html
  baseURL: https://api.teamohana.us
  tags:
  - Headcount
  properties:
  - type: OpenAPI
    url: openapi/teamohana-headcount-api-openapi.yml
  - type: Documentation
    url: https://api.teamohana.us/faq/index.html
  - type: APIReference
    url: https://api.teamohana.us/faq/index.html
- aid: teamohana:teamohana-scenario-api
  name: TeamOhana Scenario API
  description: The Scenario API from TeamOhana — 2 operation(s) for scenario.
  humanURL: https://api.teamohana.us/faq/index.html
  baseURL: https://api.teamohana.us
  tags:
  - Scenario
  properties:
  - type: OpenAPI
    url: openapi/teamohana-scenario-api-openapi.yml
  - type: Documentation
    url: https://api.teamohana.us/faq/index.html
  - type: APIReference
    url: https://api.teamohana.us/faq/index.html
- aid: teamohana:teamohana-scim-api
  name: TeamOhana SCIM API
  description: The SCIM API from TeamOhana — 3 operation(s) for scim.
  humanURL: https://api.teamohana.us/faq/index.html
  baseURL: https://api.teamohana.us
  tags:
  - SCIM
  properties:
  - type: OpenAPI
    url: openapi/teamohana-scim-api-openapi.yml
  - type: Documentation
    url: https://api.teamohana.us/faq/index.html
  - type: APIReference
    url: https://api.teamohana.us/faq/index.html
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: OpenAPI
  url: openapi/_original/teamohana-openapi-original.json
- type: Authentication
  url: authentication/teamohana-authentication.yml
- type: Conventions
  url: conventions/teamohana-conventions.yml
- type: RateLimits
  url: rate-limits/teamohana-rate-limits.yml
- type: ErrorCatalog
  url: errors/teamohana-problem-types.yml
- type: Conformance
  url: conformance/teamohana-conformance.yml
- type: DataModel
  url: data-model/teamohana-data-model.yml
- type: Lifecycle
  url: lifecycle/teamohana-lifecycle.yml
- type: StatusPage
  url: https://status.teamohana.us/
- type: X-MCPServerCandidate
  url: mcp/teamohana-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/teamohana-llms.txt
- type: Overlay
  url: overlays/teamohana-openapi-overlay.yaml
- type: AgenticAccess
  url: agentic-access/teamohana-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Documentation
  url: https://api.teamohana.us/faq/index.html
- type: APIReference
  url: https://api.teamohana.us/faq/index.html
- type: TrustCenter
  url: security/teamohana-trust-center.yml
- type: Compliance
  url: https://trust.teamohana.com/
- type: DomainSecurity
  url: security/teamohana-domain-security.yml
- type: Integrations
  url: https://www.teamohana.com/features/integrations
- type: Pricing
  url: https://www.teamohana.com/pricing
- type: Blog
  url: https://www.teamohana.com/blogs
- type: PrivacyPolicy
  url: https://www.teamohana.com/privacy-policy
- type: TermsOfService
  url: https://www.teamohana.com/terms-and-conditions
- type: SignUp
  url: https://www.teamohana.com/book-demo
- type: Support
  url: https://www.teamohana.com/contact-us
- type: Website
  url: https://teamohana.com/
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 13
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/teamohana"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/teamohana/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/teamohana/evidence"

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.

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