Rename a contract type · Fieldmotion API

When to use this endpoint

Use ContractType_edit when reproducing CRM1’s name-only edit. CRM2 uses ContractType_updateData for mapped edits.

The request must have a nonzero authenticated user ID. No page, role, ownership, or feature-bit check is performed.

Parameter	Type	Required	Description
`id`	Integer string	Yes	Positive existing type ID.
`name`	String	Yes	Trimmed replacement name, 1–64 Unicode characters. HTML is not stripped and duplicate names are allowed.

$result = FM_api('ContractType_edit', [
	'id' => '31',
	'name' => 'Planned service',
]);

{
  "ok": 1
}

An exact no-op returns {"ok":1,"msg":"no update needed"}. Comparison is case-sensitive after trimming.

Response	Condition
`{"error":"not logged in"}`	No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.
`{"error":"missing or invalid parameter: id"}`	The ID is absent or nonpositive.
`{"error":"missing or invalid parameter: name"}`	The trimmed name is blank.
`{"error":"parameter too long: name. max length 64 characters"}`	The name exceeds 64 Unicode characters.
`{"error":"Contract Type does not exist"}`	No row has the supplied ID.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

The endpoint changes only name. It does not validate uniqueness or modify invoicing behavior.
There is no pagination or soft-deleted state for contract types.

A changed name receives current server last_edited and invalidates the contract-type cache. No generic audit entry is written by this legacy route.

Open Contracts → Contract Types, click Edit, change the name, and save; CRM1 first calls ContractType_get and then this route.

A production-source search found no CRM2 caller. CRM2’s configurable table uses ContractType_updateData.