Install Jentic One Beta

Connect the Partner API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Partner API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpartner-api.payfit.com%2Fpayfit" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpartner-api.payfit.com%2Fpayfit" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Partner API.

Retrieve payslips and payroll status for any company entity

Access collaborator records with meal voucher entitlements

Export accounting data in standard and v2 formats for reconciliation

Manage health insurance contract assignments on French employee contracts

Configure provident fund allocations per contract

GET STARTED

Start building with Partner API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Partner API for, with concrete tasks.

★ Payroll Accounting Export

Export structured accounting entries from PayFit for automatic reconciliation with external accounting systems. The Partner API provides both standard and v2 accounting formats covering salary costs, employer contributions, and benefit allocations. Each export maps to a specific payroll period and company entity, enabling month-end close automation without manual data entry.

Retrieve accounting-v2 data for company entity ID abc123 and map journal entries to the current payroll period

Employee Payslip Retrieval

Access individual payslips for any collaborator through the Partner API by specifying company, collaborator, contract, and payslip identifiers. This supports automated payslip distribution, employee self-service portals, and audit compliance workflows. Each payslip contains gross pay, deductions, net pay, and benefit line items tied to the specific contract period.

Retrieve the payslip for collaborator col456 under contract ctr789 for the most recent payroll period in company comp123

French Contract Benefits Management

Configure health insurance and provident fund allocations on French employment contracts through dedicated PUT endpoints. The API accepts contract-level benefit assignments that map to the French social security system, enabling HR platforms to synchronize benefit elections without manual entry in the PayFit interface. Changes take effect on the next payroll cycle.

Update the health insurance contract assignment for French contract ctr789 in company comp123 with the new mutuelle provider details

AI Agent Payroll Data Integration

AI agents connect to the PayFit Partner API through Jentic to retrieve payroll, contract, and accounting data without managing OAuth2 token flows directly. Jentic handles credential isolation and token refresh, letting agents query payroll status or export accounting entries by searching for the relevant operation and executing it with scoped access. This reduces integration from days of OAuth implementation to minutes of intent-based discovery.

Search Jentic for 'retrieve payroll status' operation, load the schema for the PayFit payroll-status endpoint, and execute it for company comp123

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for partner api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/companies/{companyId}/collaborators

List all collaborators in a company

GET

/companies/{companyId}/collaborators/{collaboratorId}/contracts/{contractId}/payslips/{payslipId}

Retrieve a specific payslip

GET

/companies/{companyId}/accounting-v2

Export v2 accounting data

GET

/companies/{companyId}/payroll-status

Check current payroll processing status

GET

/companies/{companyId}/contracts

List all employment contracts

PUT

/companies/{companyId}/contracts-fr/{contractId}/health-insurance

Update health insurance on a French contract

GET

/companies/{companyId}/collaborators

List all collaborators in a company

GET

/companies/{companyId}/collaborators/{collaboratorId}/contracts/{contractId}/payslips/{payslipId}

Retrieve a specific payslip

GET

/companies/{companyId}/accounting-v2

Export v2 accounting data

GET

/companies/{companyId}/payroll-status

Check current payroll processing status

GET

/companies/{companyId}/contracts

List all employment contracts

PUT

/companies/{companyId}/contracts-fr/{contractId}/health-insurance

Update health insurance on a French contract

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PayFit Partner API by hand means implementing its OAuth2 flow with token refresh, setting the partner-api.payfit.com host, and threading company and contract path parameters through every call yourself. Through Jentic you install once, import the PayFit Partner API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

PayFit puts the company id in the URL path (/companies/{companyId}/...), so a rule can pin your agent to one company: it can read collaborators, contracts, payslips, and accounting there. You choose the operations it may call, so writes like updating a contract's health insurance are not included unless you add them.

Credential isolation

Your PayFit OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'retrieve a collaborator's payslip' or 'export company accounting', and Jentic returns the matching PayFit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Partner API through Jentic.

Why is there no official OpenAPI spec for Partner API?

PayFit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Partner API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the PayFit Partner API use?

The Partner API uses OAuth 2.0 authentication. Through Jentic, OAuth tokens are stored encrypted in the credential vault and agents receive scoped access tokens without handling the OAuth flow directly.

Can I retrieve individual payslips through the Partner API?

Yes. The GET endpoint at /companies/{companyId}/collaborators/{collaboratorId}/contracts/{contractId}/payslips/{payslipId} returns a specific payslip. You need the company, collaborator, contract, and payslip identifiers to make the request.

What accounting formats does the Partner API support?

The API provides two accounting export endpoints: /companies/{companyId}/accounting for the standard format and /companies/{companyId}/accounting-v2 for the enhanced v2 format. Both return structured payroll journal entries for a given company entity.

How do I configure health insurance on a French contract through Jentic?

Search Jentic for 'update health insurance contract' to find the PUT /companies/{companyId}/contracts-fr/{contractId}/health-insurance operation. Load the schema to see required fields, then execute with your contract and benefit provider details. Run pip install jentic to get started.

Are there rate limits on the PayFit Partner API?

The OpenAPI spec does not document specific rate limits. As a partner-tier API requiring OAuth2 credentials, access is governed by your partner agreement with PayFit. Contact PayFit partner support for your specific allocation.

Can I limit what my agent is allowed to do with the PayFit Partner API?

Yes. Because you run Jentic One yourself, your own rules decide which PayFit operations and credentials the agent may use. Since the company id sits in the URL path, you can pin the agent to a single company and allow only read operations there, such as listing collaborators and contracts, retrieving payslips, and exporting accounting data. Write operations like updating a contract's health insurance stay off limits unless you explicitly add them.

Partner Api Payfit Partner API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticHR recruitingPayrolloauth219 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Retrieve payroll status, employee contracts, payslips, and accounting data from PayFit company entities. Supports French-specific contract details including health insurance and provident fund configuration.

Use for: I need to retrieve the latest payslips for an employee, I want to export accounting data from PayFit for reconciliation, Get the payroll status for a specific company, List all collaborators and their meal voucher entitlements

Not supported: Does not handle recruiting, time-off requests, or performance reviews - use for payroll data, contracts, and accounting exports only.

Jentic publishes the only available OpenAPI specification for Partner API, keeping it validated and agent-ready. The PayFit Partner API provides programmatic access to company payroll data, employee contracts, collaborator records, and accounting exports for French and international entities. It exposes 19 endpoints covering payslip retrieval, contract management, health insurance configuration, provident fund setup, and meal voucher data across multi-entity company structures.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

10%

Example Density

How richly the API is illustrated with examples.

90%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

85%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Partner API to your agent

Capabilities

Start building with Partner API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Partner Api Payfit Partner API

Jentic AI Readiness Score

Partner API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness