Update customer
Changed onUpdate a customer. Send only the fields you want to change. Anything you don't send stays as it is.
Set is_taxable to false to mark the customer as tax-exempt, or true to make them taxable. Omit the field to leave the current value unchanged.
Setting custom fields is easiest using the field name as the key:
{"custom_fields": [{"Partner": true}, {"Tier": "Gold"}]}
Each item is a one-key object where the key is the custom field's name and the value is whatever you want to set. Use null to clear a field. If the name doesn't match a custom field in your organization, the API returns a 422 instead of silently ignoring it.
If you already know the custom field's id, the older nested shape still works and you can mix both in the same request:
{"custom_fields": [{"field": {"id": 42}, "value": {"custom_field_id": 42, "value": "Acme"}}]}
Edge case: if you happen to have two custom fields with the same name, the name-keyed shape can't tell them apart, so use the id-based shape for those.
Request
- Base URL: https://api.dualentry.com
- URL: https://api.dualentry.com/public/v2/customers/{customer_id}/
- Auth: none declared
Path parameters
Headers
Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns 422.
Request body
Response
OK
Changes
- info
added the optional property
/////to the response with the status
- info
- info
added the new optional request property
- info
added the new optional request property
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info