Bindbee

Bindbee Departments API

Organizational departments from connected HRIS and ATS systems.

GitHub OpenAPI

Operations 1

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /hris/departments List departments from the HR system · Bindbee List Departments #
Ask an LLM
“Which departments exist in the connected HRIS?”
“Can I get the org's department list from the HR system?”
Tell an agent
List HRIS departments for connector {connector}.
Show every department in our HR system.

Documentation

📖
Documentation
https://docs.bindbee.dev/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/bindbee/refs/heads/main/openapi/bindbee-departments-api-openapi.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/bindbee:bindbee-departments-api"
All apis 
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

bindbee-departments-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Bindbee Departments API
  description: The Bindbee API provides a unified HRIS and ATS integration layer that allows companies to connect with 50+ HR systems including BambooHR, Workday, ADP, Greenhouse, Lever, and others through a single normalized API. Access employee data, job listings, candidates, payroll, time-off, and departments without managing individual integrations.
  version: v1
  contact:
    name: Bindbee Support
    url: https://docs.bindbee.dev/
  license:
    name: Proprietary
    url: https://bindbee.dev/
  x-generated-from: documentation
servers:
- url: https://api.bindbee.dev/v1
  description: Bindbee Unified API
tags:
- name: Departments
  description: Organizational departments
paths:
  /hris/departments:
    get:
      operationId: listDepartments
      summary: Bindbee List Departments
      description: Returns a list of departments from the connected HRIS system.
      tags:
      - Departments
      security:
      - apiKeyAuth: []
      parameters:
      - name: x-connector-token
        in: header
        required: true
        schema:
          type: string
      responses:
        '200':
          description: List of departments.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DepartmentsResponse'
              examples:
                ListDepartments200Example:
                  summary: Default listDepartments 200 response
                  x-microcks-default: true
                  value:
                    data:
                    - id: dept-abc123
                      name: Engineering
                      parent_id: null
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
components:
  schemas:
    Department:
      title: Department
      description: An organizational department from a connected HRIS system.
      type: object
      properties:
        id:
          type: string
          description: Department ID.
          example: dept-abc123
        name:
          type: string
          description: Department name.
          example: Engineering
        parent_id:
          type:
          - string
          - 'null'
          description: Parent department ID for nested structures.
          example: null
    DepartmentsResponse:
      title: Departments Response
      description: List of departments.
      type: object
      properties:
        data:
          type: array
          description: Array of department records.
          items:
            $ref: '#/components/schemas/Department'
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: Bearer API key in Authorization header. Also pass x-connector-token for the specific integration.