How Jentic Works
From API assessment to production deployment in four simple steps.
PLATFORM
CAPABILITIES
TOOLS
GET STARTED
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.
Jentic publishes the only available OpenAPI specification for 100Hires API, keeping it validated and agent-ready. The 100Hires API connects to the 100Hires applicant tracking system, exposing endpoints to create candidate profiles, attach them to job openings or talent pools, and inspect the workflow stages defined in a hiring pipeline. It is a focused integration surface intended for syncing candidate data from external sources such as job boards, sourcing tools, and Zapier-style automations into a 100Hires workspace. Authentication is handled with an API key passed in the Authorization header, and all four endpoints exchange JSON payloads under the /zapier base path.
Jentic publishes the only available OpenAPI specification for 15Five Public API, keeping it validated and agent-ready. 15Five is a continuous performance management platform that helps managers and employees track objectives, run weekly check-ins, gather feedback through reviews, and recognise teammates with High Fives. The Public API exposes 11 read and write operations across users, objectives, high fives, questions, answers, and reports so that performance data can be pulled into other HR systems or surfaced to AI agents. It is a focused performance-management surface rather than a full HRIS, designed for syncing engagement and goal-setting data with downstream tools.
Jentic publishes the only available OpenAPI specification for 15Five Public API, keeping it validated and agent-ready. The 15Five Public API exposes performance management data including users, weekly check-in reports, objectives, recognitions (high fives), and the question and answer history that drives 15Five's continuous performance feedback loop. It supports listing and reading users and reports, creating and listing objectives, posting and listing high fives, and pulling questions and answers used in check-ins.
Jentic publishes the only available OpenAPI specification for 1FIT Zapier Webhook API, keeping it validated and agent-ready. The 1FIT Zapier Webhook API connects external automation tools to a personal trainer's 1FIT account, letting third-party systems register a Zapier connection, validate it, and post lifecycle events into 1FIT through a user-scoped webhook URL. It accepts a fixed set of event types covering client and prospect creation, client activation and deletion, check-in submissions, activity logs, and completed workouts. Authentication is a JWT bearer token, and every event uses a shared envelope with an event name, timestamp, and event-specific data block.
API for managing Account in <a href="https://www.5centscdn.net" target="_blank">5centsCDN</a>. The API exposes 11 endpoints secured with apiKey authentication.
API for managing Live Streams in <a href="https://www.5centscdn.net" target="_blank">5centsCDN</a>. The API exposes 173 endpoints secured with apiKey authentication.
API for managing Transcoding in <a href="https://www.5centscdn.net" target="_blank">5centsCDN</a>. The API exposes 15 endpoints secured with apiKey authentication.
API for managing Zones in <a href="https://www.5centscdn.net" target="_blank">5centsCDN</a>. The API exposes 178 endpoints secured with apiKey authentication.
The 7shifts API is the full developer interface to 7shifts, a team management platform built for restaurants. This third-party-published spec covers 138 endpoints across companies, locations, departments, roles, employees, schedules, shifts, time punches, time off, labor settings, and engagement features. Restaurant operators, payroll integrations, and POS partners use it to provision locations, assign shifts, capture clock-ins and clock-outs, and pull labor data for payroll runs. Authentication supports OAuth 2.0, marketing API keys, and basic auth depending on the integration type.
Jentic publishes the only available OpenAPI specification for 7shifts Restaurant Scheduling API, keeping it validated and agent-ready. This curated v2 spec covers twelve core endpoints from the 7shifts platform — companies, locations, departments, roles, users, shifts, schedules, time punches, and labor settings — focused on the operations a typical restaurant integration needs without the full surface of the partner API. Authentication uses OAuth 2.0 with tokens issued through the /oauth2/token endpoint.
API for acuityscheduling.com. The API exposes 9 endpoints secured with basic authentication.
Jentic publishes the only available OpenAPI specification for the ADP API, keeping it validated and agent-ready. The ADP API exposes 9 endpoints across HR, payroll, time and attendance, organisation data, recruiting, and worker lifecycle events. Use it to retrieve worker rosters, pay statements, time cards, organisation departments, work locations, and job applicants, and to subscribe to worker hire and termination events. Authentication is OAuth 2.0 with mutually authenticated SSL client certificates issued by ADP.
Jentic publishes the only available OpenAPI specification for Adzuna API, keeping it validated and agent-ready. Adzuna aggregates job listings from across the web and exposes them through a country-scoped REST API covering search, category breakdowns, salary histograms, top-company rankings, and geo-distributed listings. Each endpoint takes a country code (e.g. gb, us, de) and returns structured job data drawn from thousands of sources, making it suitable for job boards, salary research, and labour-market analytics. Authentication uses an app_id and app_key pair appended as query parameters.
**Internal IDs:** The following terms are used to reference IDs that identify resources in AlayaCare: - account_id - client_user_id **External IDs:** External IDs are required to be unique. No other assumptions are made regarding their form; they are treated as strings. The following terms are used to reference IDs that identify resources in systems external to AlayaCare: - external_client_id - ex. The API exposes 5 endpoints secured with basic authentication.
Jentic publishes the only available OpenAPI specification for allGeo API, keeping it validated and agent-ready. allGeo is a workforce management platform for distributed and field teams, and the API covers work orders, job sites, devices, time clock entries, and SMS or push messaging. Authentication is bearer-token based with explicit login and refresh endpoints, and the API is scoped to operational data — not payroll calculation or invoicing. The endpoint set is small enough to learn in a session yet covers the core daily operational events of a field workforce.
Deliver monetary rewards and incentives to employees, customers, survey participants, and more through the Tremendous API. For organizational tasks, like managing your organization and it's members within Tremendous, please see the Tremendous Organizational API. The API exposes 36 endpoints secured with bearer authentication.
Jentic publishes the only available OpenAPI specification for Arbeitsagentur Jobsuche API, keeping it validated and agent-ready. The Arbeitsagentur Jobsuche API exposes job listings from the German Federal Employment Agency (Bundesagentur für Arbeit), one of the largest single sources of vacancies in the German-speaking labour market. The API supports filtered searches by keyword, location, occupation, and other facets, with both web and mobile-app variants. It also exposes employer logo retrieval keyed by a hashed employer identifier.
Jentic publishes the only available OpenAPI specification for Ashby API, keeping it validated and agent-ready. Ashby is an applicant tracking system (ATS) used by high-growth companies to manage the entire hiring funnel — sourcing, applications, interviews, offers, and analytics. The API exposes 157 RPC-style endpoints covering applications, candidates, jobs, interview schedules, feedback, offers, and approvals, secured with HTTP basic authentication using an API key. Endpoint naming follows a dot-notation convention (e.g. application.list, candidate.create) and all calls use POST.
Rev.ai provides quality speech-text recognition via a RESTful API. All public methods and objects are documented here for developer reference. For a real-time speech to text solution, use Rev.ai's [Streaming API](/docs/streaming). Base Endpoint The base url for this version of the API is > `https://api.rev.ai/speechtotext/v1` All endpoints described in this documentation are relative to this base . The API exposes 7 endpoints secured with bearer authentication.
Apideck ATS is a unified API that maps a single schema for jobs, applicants, applications, offers, and activities onto downstream applicant tracking systems such as Greenhouse, Lever, Workable, SmartRecruiters, and BambooHR. The 12 operations cover the recruiting hand-off most apps need: read open roles, read candidate records, post applications, and write offers. Apideck routes each call through Apideck Vault, so per-customer ATS credentials stay in Apideck's vault rather than being passed to the calling app.
Jentic publishes the only available OpenAPI specification for BambooHR API, keeping it validated and agent-ready. Access and manage the full employee lifecycle through 164 endpoints spanning employee records, time-off requests, benefits administration, payroll data, goals tracking, applicant tracking, and training management. Supports company-scoped multi-tenant access with OAuth 2.0 or HTTP Basic authentication for programmatic HR automation.
Jentic publishes the only available OpenAPI specification for Bilflo API, keeping it validated and agent-ready. Bilflo is a back-office platform for staffing and recruitment agencies, exposing endpoints for client records, contract jobs, client contacts, addresses, agreements, and configurable company settings such as workers' comp codes, payment terms, and pay-bill items. The API also covers dashboards and custom fields used to extend the underlying client and job model. Authentication is by bearer token, scoped to the agency's Bilflo tenant.
The Bob API is HiBob's HR platform interface for managing employees, onboarding, time-off, attendance, reports, and company configuration. Across 94 endpoints, integrators can search and read employees, create and terminate employees, set start dates and welcome wizards, manage avatars and tasks, configure custom fields and named lists, submit and inspect time-off requests, query who's-out today, and import attendance. Authentication accepts a Bearer-style API token in the Authorization header or HTTP Basic for service users, and a sandbox host (api.sandbox.hibob.com) is available for testing.
Jentic publishes the only available OpenAPI specification for Bonusly API, keeping it validated and agent-ready. Bonusly is an employee recognition and rewards platform that lets coworkers give each other small bonuses tied to company values. The API exposes 23 endpoints covering bonuses, users, redemptions, achievements, webhooks, and analytics. Use it to send bonuses programmatically, deactivate users when they leave, redeem points for rewards, and pull hashtag trends and leaderboards into HR dashboards.
Jentic publishes the only available OpenAPI specification for Breezy HR API, keeping it validated and agent-ready. Breezy HR is an applicant tracking system whose v3 API exposes 28 endpoints across companies, positions (jobs), candidates, conversations, documents, resumes, and webhook endpoints. Recruiters use it to publish and update positions, source and update candidates, move candidates through pipeline stages, exchange messages with candidates, and attach resumes and supporting documents. Webhook endpoints let downstream systems react to candidate or position changes in near real time. Authentication is a bearer token obtained from POST /signin or generated in the Breezy dashboard.
Jentic publishes the only available OpenAPI specification for Bullhorn Resume Parsing API, keeping it validated and agent-ready. The Bullhorn Resume Parsing API converts uploaded CVs and resume documents into structured candidate records inside the Bullhorn ATS, then lets recruiting workflows build out the candidate's education history, work history, primary skills, and attached files. It is scoped to the candidate intake path: parse a resume, create the candidate entity, enrich it with related sub-entities, and attach the original document. The API is part of Bullhorn's broader staffing platform and uses Bullhorn's standard OAuth 2.0 authorization-code flow with a per-corporation REST base URL.
Jentic publishes the only available OpenAPI specification for Bullhorn Resume Parsing API, keeping it validated and agent-ready. The Bullhorn Resume Parsing API turns inbound resume documents into structured Bullhorn candidate records and lets recruiting tools enrich those candidates with education history, work history, primary skills, and original file attachments. The API runs against Bullhorn's per-corporation REST host and uses Bullhorn's standard OAuth 2.0 authorization-code flow. It is the same surface published under the bullhorn.github.io vendor entry, scoped to the candidate intake path.
Jentic publishes the only available OpenAPI specification for BusyBusy API, keeping it validated and agent-ready. BusyBusy is a workforce time tracking and field operations platform for construction trades. This is the full surface — 512 endpoints covering time entries, projects, members, equipment, certifications, budgets, attachments, and back-office configuration. Use this spec when an integration needs deep coverage; the lighter busybusy spec curates a smaller set of common resources.
The busybusy REST API exposes time tracking, project management, and safety data for construction companies that run on busybusy. It covers time entries, projects, members, cost codes, certifications, and API keys, with read access on every resource and create access on time entries, projects, certifications, and API keys. It is used to sync busybusy data into payroll, ERP, and BI systems and to create time entries from external tools. Authentication is a Bearer API key sent in the Authorization header.
Jentic publishes the only available OpenAPI specification for BusyBusy REST API, keeping it validated and agent-ready. BusyBusy is a workforce time tracking and project management platform for construction and field service teams. This curated REST surface covers programmatic management of API keys, equipment, certifications, cost codes, budget data, and authoritative signatures. It is the lighter of two BusyBusy specs in the Jentic corpus, focused on the most commonly used resources for time and cost reporting integrations.
Jentic publishes the only available OpenAPI specification for the Calm Partner API, keeping it validated and agent-ready. Calm's B2B partner API gives employers, benefits platforms, and health plans a way to grant their users access to Calm's meditation and sleep content as part of an employee or member benefit. The API is intentionally narrow with three operations — POST /v0/authorize to issue a partner access token, POST /v0/b2b/users/link to link a partner user ID to a Calm subscription, and DELETE /v0/b2b/users/{partner_user_id} to revoke that link when an employee leaves. Authentication is a JWT bearer token obtained from the authorize endpoint.