Contract amendments

Amending a contract lets you update specific parts of a contract after it signing. You can change terms such as payment details, role, or scope of work. Some fields cannot be changed, such as the contract type or or the original start date.

Amendments let you adjust terms within existing contracts while keeping both parties aligned. Each amendment defines the updated terms of work and requires signatures from both sides before it becomes effective.

The general steps to amend a contract through the API are:

What you can and cannot amend

The following table shows which parts of a contract can and cannot be amended:

You can make amendments to	You can not make amendments to
✅ Job title	✘ Country of tax residence
✅ Payment details (rate, invoice cycle, payment due date)	✘ Start date (original start date must remain but an amendment may be added)
✅ Contract currency	✘ Contract type
✅ Work schedule	✘ Client entity information
✅ Scope of work
✅ End of contract (end date and notice period)
✅ Special clauses
✅ Employee personal details (full legal name, passport number, etc.)

Structure of the request payload

The Amend contract endpoint accepts a request body that defines the contract fields you want to update.

Here is an example of a request body payload:

{
  "data": {
    "payment_due_type": "REGULAR",
    "scale": "biweekly",
    "amount": 6000,
    "cycle_end": 7,
    "frequency": "biweekly",
    "job_title_id": 2,
    "seniority_id": 2,
    "currency_code": "EUR",
    "first_payment": 2000,
    "scope_of_work": "Design a system",
    "cycle_end_type": "DAY_OF_WEEK",
    "effective_date": "2025-09-20",
    "job_title_name": "3D Designer",
    "payment_due_days": 14,
    "first_payment_date": "2025-10-10",
    "pay_before_weekends": true
  }
}

The table below provides a full list of the amendable contract fields available through the API:

Name	Type	Format	Description	Example
`payment_due_type`	string	enum	Determines when the payment is due. If you select `REGULAR`, the payment is determined by the `payment_due_days` parameter. If you select `WITHIN_MONTH`, the payment is due on the last day of the invoicing cycle.	`REGULAR`
`scale`	string	enum	Defines the amount scale. For example, setting the amount to `100`, the currency code to USD, and the scale to `hourly` means that a worker will be paid $100 for each hour worked. For fixed rate contract types, the scale can only be `monthly`.	`biweekly`
`amount`	number	-	The amount of the compensation to be paid to the contractor. How frequently the compensation is determined by the `frequency` parameter.	`6000`
`cycle_end`	number	-	Indicates the day when the invoicing cycle ends, based on what's set in the `cycle_end_type` parameter. For example, use 7 for a Sunday or use 30 for the 30th of the month. If the month is shorter than the number indicated, the cycle ends on the last day of the month.	`7`
`frequency`	string	enum	Determines how often the compensation is paid to the contractor. The available values are `monthly`, `weekly`, `biweekly`, `semimonthly`, and `calendar_month`.	`biweekly`
`job_title_id`	number	ID	The ID of the job title.	`2`
`seniority_id`	number	ID	The ID of the seniority level.	`2`
`currency_code`	string	-	Indicates the currency code of the compensation following the 3-digit ISO 4217 format. Visit the Help center for a list of supported currencies.	`EUR`
`first_payment`	number	-	Determines the amount of the first payment, based on the invoicing cycle.	`2000`
`scope_of_work`	string	-	Fill it with a job description or a summary of the roles and responsibilities of the worker.	`Design a system`
`cycle_end_type`	string	enum	Together with the `cycle_end` parameter, determines when the compensation cycle ends. Available values are: - `DAY_OF_MONTH` for the calendar day of the month - `DAY_OF_WEEK` for the week day in weekly payments - `DAY_OF_LAST_WEEK` for the last week day of the month	`DAY_OF_WEEK`
`effective_date`	string	date	The date when the amended terms become active. Use the ISO-8601 short date format `YYYY-MM-DD`. The updated terms will apply from this date and appear in payroll, invoices, and other downstream processes.	`2025-09-20`
`job_title_name`	string	-	The name of the job title. This field is required if `job_title_id` is not provided.	`3D Designer`
`payment_due_days`	number	-	When the `payment_due_type` parameter is set to `REGULAR`, this parameter determines the offset of days for the payment to be due. For example, set it to 5 if you want the payment to be due 5 days after the last day of the invoicing cycle.	`14`
`first_payment_date`	string	date	Can be used to force the date of the first payment when the date falls outside of the invoicing cycle. Use the ISO-8601 short date format `YYYY-MM-DD`.	`2025-10-10`
`pay_before_weekends`	boolean	-	If the payment due date falls on a weekend, the payment will be processed on the Friday before the weekend.	`true`
`special_clause`	string	-	Any special clauses that apply to the contract.	`Lorem ipsum dolor sit amet.`