Custom properties of an object type
GET/custom-properties
What an integration needs before reading or writing the custom_properties block of a
resource. Properties are addressed by code; one with no code of its own is reported
under the synthetic cp_<id> key it is addressed by (has_code: false). Disabled
properties are listed with enabled: false so a missing value can be explained.
With subtype, the properties of that subtype's form, with what it changes of each
(label, description, required, disabled, order, group) applied (since 4.3.1).
Request
Responses
- 200
- 401
- 404
- 422
OK
Missing, invalid or expired token, or no contact matches it.
Unknown route, or the resource is missing or in the trash; message names what was
looked for (task, note, payment_receipt, expense…). On an expenses route,
message: "expenses" means the plugin is not active.
Invalid input. details maps each field to a reason the client can switch on
(required, invalid, not_found, conflict, unsupported, …; see each operation);
_: rejected is a refusal by EVX Software's own save, with its message.