Skip to content

Deel: Update contract — request body — body data cycle end type: DAY OF WEEK, DAY OF LAST WEEK, DAY OF MONTH, frequency: weekly, monthly, biweekly, semimonthly, calendar-month, payment due type: REGULAR, WITHIN MONTH, scale: hourly, daily, weekly, monthly, biweekly, semimonthly, custom

Update contract: request body, field body / data / cycle_end_type: DAY_OF_WEEK, DAY_OF_LAST_WEEK, DAY_OF_MONTH, frequency: weekly, monthly, biweekly, semimonthly, calendar-month, payment_due_type: REGULAR, WITHIN_MONTH, scale: hourly, daily, weekly, monthly, biweekly, semimonthly, custom. Complete fields and constraints for contract 2026-10-27.

API reference · Contract 2026-10-27

SDK schema: Update contract — request body — body / data / cycle_end_type: DAY OF WEEK, DAY OF LAST WEEK, DAY OF MONTH, frequency: weekly, monthly, biweekly, semimonthly, calendar-month, payment due type: REGULAR, WITHIN MONTH, scale: hourly, daily, weekly, monthly, biweekly, semimonthly, custom

FieldTypePresenceDescription and constraints
$objectRootYou can specify any combination of data points that need changing.
amountnumberOptionalAmount to be paid per scale.
Format: double
Minimum: 1
currency_codestringOptionalCurrency code in ISO 4217 format.
Maximum length: 3
Minimum length: 3
Pattern: ^[A-Z]{3}$
cycle_endnumberOptionalDay of the month when the cycle ends.
Format: double
Maximum: 31
Minimum: 1
cycle_end_typestringOptionalCycle end can be weekly 1-7 (Monday = 1) or monthly 1-31.
One of: DAY_OF_WEEK, DAY_OF_LAST_WEEK, DAY_OF_MONTH
effective_datestringOptionalShort date in format ISO-8601 (YYYY-MM-DD). For example: 2022-12-31.
Format: date
first_paymentnumberOptionalAmount to be paid as the first payment.
Format: double
Minimum: 0
first_payment_datestringOptionalShort date in format ISO-8601 (YYYY-MM-DD). For example: 2022-12-31.
Format: date
frequencystringOptionalScale of the invoice cycle.
One of: weekly, monthly, biweekly, semimonthly, calendar-month
job_title_idModelOptionalExpand Update contract — request body — body / data / cycle_end_type: DAY OF WEEK, DAY OF LAST WEEK, DAY OF MONTH, frequency: weekly, monthly, biweekly, semimonthly, calendar-month, payment due type: REGULAR, WITHIN MONTH, scale: hourly, daily, weekly, monthly, biweekly, semimonthly, custom job title id
job_title_namestringOptionalYou can enter new job title.
pay_before_weekendsbooleanOptionalIf the payment due is on a weekend, pay on Friday.
payment_due_daysnumberOptionalNumber of days after the invoice is sent that the payment is due.
Format: double
Maximum: 90
Minimum: 0
payment_due_typestringOptionalType of payment due. If the payment is due on the last day of month, enter ‘WITHIN_MONTH’.
Default: REGULAR
One of: REGULAR, WITHIN_MONTH
scalestringOptionalDefines the scale at which the amount is paid. For example, enter ‘hourly’ to define the amount per hour. This field can be excluded when creating a Pay-as-you-go task-based or Milestone contracts.
One of: hourly, daily, weekly, monthly, biweekly, semimonthly, custom
scope_of_workstringOptionalText to describe the scope of work of the contract.
seniority_idModelOptionalExpand Update contract — request body — body / data / cycle_end_type: DAY OF WEEK, DAY OF LAST WEEK, DAY OF MONTH, frequency: weekly, monthly, biweekly, semimonthly, calendar-month, payment due type: REGULAR, WITHIN MONTH, scale: hourly, daily, weekly, monthly, biweekly, semimonthly, custom job title id
special_clausestringOptionalText to describe any special clause in contract.
start_datestringOptionalThe contract start date in ISO-8601 format (YYYY-MM-DD). Updates the contract’s effective date.
Format: date

Referenced models: Update contract — request body — body / data / cycle_end_type: DAY OF WEEK, DAY OF LAST WEEK, DAY OF MONTH, frequency: weekly, monthly, biweekly, semimonthly, calendar-month, payment due type: REGULAR, WITHIN MONTH, scale: hourly, daily, weekly, monthly, biweekly, semimonthly, custom job title id

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.