Integration 1 C
Updated over a week ago

Preparing to create an integration

To start working with the API, you need to generate an API key. This can be done in Settings -> API Keys (under Security) -> Generate.

If you want to create/edit employee compensation via API - provide the appropriate permission in the key generation window.

PeopleForce API has a limitation in the number of requests per minute. To get acquainted with current requirements follow the link. Take this limitation into account to avoid errors.

All resources that return the list of records have unified pagination. You can familiarize yourself with the format by clicking the following link.

You can import the OpenAPI configuration into Postman or other HTTP client for convenient work with the API.

You can see an example of API response for each endpoint in the corresponding block:

Qe1rRRABRiyE58lktVnae8kQ0qXSIac_-MF9gWrDReAqpqTL7ULhe8M-dCaQSkap3da_Hzm0uuGOyGnompM74RthBAzeCuy_HD9YlRfURM-fKvYqt_ozoCoBCFY8c-dtbPOnlheO2vF2Nm5xR1tQH9I (451×232)

Step 1: Preparing PeopleForce for data transfer

PeopleForce API has a limitation in the number of requests per minute. To get acquainted with current requirements follow the link. Take this limitation into account to avoid errors.

All resources that return the list of records have unified pagination. You can familiarize yourself with the format by clicking the following link.

You can import the OpenAPI configuration into Postman or other HTTP client for convenient work with the API.

You can see an example of API response for each endpoint in the corresponding block:

Step 2: Transfer employee information

Create a database of current employees with required fields from personal information, work information, etc. After creating an account, to display position, salary and employment data, and especially the chronology of changes, you need to further enter this data by referring to the points below (points 2-4).

You can also use synchronization to update employee information in PeopleForce or terminate an employee in the system.

Additionally, you can transfer other employee information that is not listed here. More actions are available and spelled out in the documentation.

Step 3: Transfer absences: vacation, sick leave and other types of absences

Before setting up this type of integration, make sure absence types and policies are created in the system and assigned to employees. If there are any issues with this - please contact your CS manager.

Data transfer from PeopleForce to 1C:

Requests can be filtered by dates, employees, statuses, etc. by passing corresponding parameters.

Data transfer from 1C to PeopleForce:

Before creating requests, employees already have

Among the mandatory parameters to create a vacation request is the leave type - leave_type_id. To get it, use the endpoint

Please note - requests created via API should be matched in the same way as regular requests - via PeopleForce web interface. For one-time addition of historical data use the corresponding import.

Step 4: Transfer employee assets

Create an asset and assign the asset to the employee

Optional: Webhooks to get real-time changes from PeopleForce

Webhooks allow you to receive all changes in PeopleForce without having to request them separately. For example, if any fields in an employee's profile change, we will send the corresponding event with up-to-date information on the employee.

For detailed information about a webhook, as well as sample data, select the desired webhook in the navigation menu on the left:

Please note - requests created via API should be coordinated in the same way as regular requests - via PeopleForce web interface. For one-time addition of historical data, use the corresponding import.

Did this answer your question?