PayFit

PayFit is a payroll and HR management SaaS, primarily serving France, Spain, and the UK, that exposes company, employee (collaborator), contract, and absence data through its partner API. Nexla connects to the PayFit partner API to ingest company and collaborator records and to write new collaborators, contracts, and absences back into PayFit.

Power end-to-end data operations for your PayFit API with Nexla. Our bi-directional PayFit connector is purpose-built for PayFit, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to PayFit or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your PayFit workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The PayFit partner API authenticates requests with an access token passed as a bearer token in the Authorization header (for example, Authorization: Bearer YOUR-API-KEY). PayFit issues these tokens to registered partners through its OAuth 2.0 flow, and each token is scoped to a single company — the company of the user who completed the OAuth authorization.

To obtain the credentials required to configure a PayFit credential in Nexla:

1. Register as a PayFit partner by following the How to Become a Partner guide in the PayFit developer documentation.

2. Complete the OAuth 2.0 authorization flow described in Authentication with OAuth2 to obtain an access token. Request the scopes your integration needs — for example, collaborators:read to list collaborators, collaborators:write to create collaborators, collaborators:contracts:write to create contracts, and time:write to create absences.

3. Retrieve your Company ID by sending a POST request to the introspection endpoint at https://oauth.payfit.com/introspect with your access token. The JSON response includes the company_id associated with the token. You will supply this Company ID when configuring source and destination endpoints, since one token maps to one company.

4. Store the access token securely. It is sensitive information and grants access to your PayFit company data.

For more information, refer to the PayFit API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key used to authenticate requests to the PayFit API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your PayFit access token in the API Key field. Nexla sends this value as Authorization: Bearer <API Key> on every request to the PayFit partner API, so it must be kept confidential.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the PayFit connector tile, then select the credential that will be used to connect to PayFit, and click Next; or, create a new PayFit credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common PayFit endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Company

Retrieve Company. This endpoint template fetches the company record for the PayFit company associated with your access token.

• Provide the Company ID for the authenticated partner token. This is the company ID returned by the PayFit OAuth introspect endpoint; each API key maps to a single company.

For detailed information about the company resource and its response structure, see the PayFit API documentation.

[Rest API] List Collaborators

Retrieve Collaborators. This endpoint template fetches the list of collaborators (employees) for a PayFit company.

• Provide the Company ID for the authenticated partner token. This is the company ID returned by the PayFit OAuth introspect endpoint; each API key maps to a single company.
• This endpoint is paginated. Nexla automatically pages through the results and stops when no further collaborator records are returned.

Listing collaborators requires the collaborators:read scope on your access token. For detailed information about the collaborators resource and its response structure, see the PayFit API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

PayFit data sources can also be manually configured to ingest data from any valid PayFit partner API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new PayFit data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the PayFit destination, and select the Send to Destination option from the menu. Select the PayFit connector from the list of available destination connectors, then select the credential that will be used to connect to PayFit, and click Next; or, create a new PayFit credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common PayFit endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Collaborator

Creates a new collaborator record for a company and returns its ID (requires the collaborators:write scope).

• Provide the Company ID for the authenticated partner token. This is the company ID returned by the PayFit OAuth introspect endpoint; each API key maps to a single company.
• Each record from your Nexset is sent as a JSON request body to create one collaborator. Ensure the record matches the fields the PayFit API expects for collaborator creation.

For detailed information about the request body and available fields for collaborator creation, see the PayFit Create Collaborator reference.

[Rest API] Create Contract

Creates a new contract for a collaborator (France only, requires the collaborators:contracts:write scope).

• Provide the Company ID for the authenticated partner token and the Collaborator ID of the employee the contract is created for.
• Each record from your Nexset is sent as a JSON request body to create one contract. Ensure the record matches the fields the PayFit API expects for contract creation.

This endpoint is available for France only. For detailed information about the request body and available fields for contract creation, see the PayFit Create Contract reference.

[Rest API] Create Absence

Creates a validated absence for a collaborator's contract and returns the new absence ID (requires the time:write scope).

• Provide the Company ID for the authenticated partner token. This is the company ID returned by the PayFit OAuth introspect endpoint; each API key maps to a single company.
• Each record from your Nexset is sent as a JSON request body to create one absence. Ensure the record matches the fields the PayFit API expects for absence creation.

For detailed information about the request body and available fields for absence creation, see the PayFit Create Absence reference.

Manual configuration

PayFit destinations can also be manually configured to send data to any valid PayFit partner API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured PayFit endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the PayFit endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.