Restore a deleted customer
POSThttps://
Clears the soft-delete marker and returns the customer in the detail view.
Access
- Token scope
- api:
write: customers Without it:
403 insufficient-token-scope. - Permission
- customers::
create Without it:
403 insufficient-permission. - Rate cost
- 1 unit, write bucket. A write costs the same whatever
viewyou ask for. - Also
- Accepts
Idempotency-Key. AcceptsIf-Match. Never cached:private, no-store. Unknown query parameters are refused, never ignored.
Both are checked, scope first. A token never does more than its user. How access is checked
Restoring additionally requires customers::delete as well as customers::create. Restoring a customer that is not deleted succeeds and returns an already_in_target_state warning. The customer's projects are not restored: deleting the customer soft-deleted each of them, and each is brought back through POST projects/{project}/actions/restore. The restore finds a deleted customer on its own, so the trashed parameter is not accepted.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
Request headers
A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
Response 200
Returns a Customer in the detail view.
Headers
ETag- A strong validator of exactly this representation.
Idempotency-Replayedtruewhen this response was replayed from a storedIdempotency-Keyrather than produced by a new write.RateLimit- The IETF
httpapi-ratelimit-headersform of your remaining allowance on the tightest bucket this request touched. RateLimit-Policy- The ceiling and window of that bucket, as
<limit>;w=<seconds>. X-Request-Id- The server-generated ULID correlating this response with our logs.
Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning
Short customer code, e.g. ACM. Prefixes every work item's issue key, is enforced unique on write, and is one of the fields ?q= searches.
Chip colour as a CSS hex triplet or sextet, e.g. #1d4ed8. A stored value that is not valid hex reads back as #6b7280.
Where the customer sits in the sales lifecycle.
suspectprospectfuture-opportunityactiveinactive
New values may be added.
Country as an ISO 3166-1 alpha-2 code, e.g. NL, as plnnrly writes it. Older records may hold any string.
Latitude, geocoded from the address whenever address, zip or city changes. Not writable.
Longitude, geocoded from the address whenever address, zip or city changes. Not writable.
Payment term in days, as held by the accounting integration. Read by the invoice composer; written only by the Exact sync.
Debtor number in the accounting system. Writing it requires billing_settings::update.
Account identifier in Exact Online, written by the sync.
When the Exact sync last handled this customer, or null if never.
Whether the Exact sync leaves this customer's local address alone although it differs from the one in Exact. Set when a user accepts the difference on the Exact customers screen in plnnrly; not writable.
Responsible account manager. Required on create; unassigned when the user is deleted.
Company type, or null. Company types are your organisation's own list, maintained in plnnrly and not exposed as a collection.
Company size band, or null. Company sizes are your organisation's own list, maintained in plnnrly and not exposed as a collection.
The customer's category. Rendered as {"id": N} until named in ?include=customer_category, and null where none is assigned.
The customer's industry branch. Rendered as {"id": N} until named in ?include=company_branch, and null where none is assigned.
Number of live projects for this customer. Soft-deleted projects are not counted.
Errors
409 Conflict.
412 Precondition failed.
7 errors every operation can return: 400, 401, 404, 406, 429, 500, 503
400 Bad request.
idempotency-key-requiredinvalid-cursorinvalid-query-parametermalformed-requestunsupported-parameter
401 Unauthenticated.
404 Not found.
406 Not acceptable.
429 Too many requests.
500 Server error.
503 Service unavailable.
This path allows POST. Anything else answers 405.
Something wrong or missing on this page? Tell us