Update client-ref BCAN mapping
PUT{BASE_URL}/accounts/client-bcan
Replaces the HKIDR CID details of an existing mapping, identified by
account_number and client_ref. The assigned id, bcan,
ce_number and order_tag never change.
This is a full replacement, not a partial update: every CID field is overwritten with the value sent, and optional fields you omit are cleared.
Validation is the same as for POST. hkidr_consent must be true
and id_number must not be blank. Individuals and joint accounts need
at least one of english_first_middle_name, english_last_name or
chinese_name. Other client types need english_legal_entity_name or
chinese_legal_entity_name.
Returns 400 DataRetrieval_Error if no mapping exists for
client_ref; use POST to create one.
Request
Responses
- 200
- 400
- 401
- 403
Mapping updated.
The request could not be accepted, for example because the account or
symbol is unavailable, a required paired account is missing, buying power
or position is insufficient, required market pricing is unavailable, an
identifier is duplicated, or an order field or requested lifecycle action
is invalid. A missing account_number, or one not linked to the API key,
also returns 400 BasicInput_Error.
Missing or invalid X-API-KEY.
The API key is read-only and the request is not a GET.