Make a REST API request when editing a record

On the GIRITON side, when you modify data in a selected agenda (HR, Shift Plan, Projects, Inserted Attendance, ...), you can in GIRITON in the User menu -> Configuration -> Planned Tasks -> Add, add a Planned Task Send REST API request after a record has changed that will execute the REST API request according to your settings.

You can set the type of request (GET, POST, ...), the destination URL, whether the REST API request should be executed when adding, editing or deleting a record in GIRITON, and what type of records (HR, Shift Plan, Projects, Inserted Attendance, ...) the planned task responds to.

The vast majority of REST API calls will also need an HTTP header, usually with an API key for authentication, you can specify these values as well.

Activated setting Send in batches means that when many records of a given agenda are modified at once on the GIRITON side (for example, shifts have been rescheduled in bulk), a single API request is made. When this option is disabled, one API request is made for each individual record modified.

• Carefully consider the value of this option, if you leave it disabled (i.e. GIRITON will make many REST API calls in a short time in case of bulk modification), you may encounter different limits on the number of API request calls on different systems.

You can even use a simple script to create a body (most often POST) of the request, into which you can insert the values of selected fields of the record being edited from GIRITON. For example, in the screenshot above, Giriton sends the ID of the employee being edited to the foreign system.