Update earmark (deprecated)

Updates an earmark, increasing or decreasing the reserved amount.

This endpoint produces the follow events:

• Authorization created
• Account balance changed
• Account balance changed (Availables)
• Transaction created
• Earmark created, updated, or canceled with UPDATED Action.

NOTES:

• This endpoint requires an account-specific access token. Getting an account token requires you to call the Get OpenID access token endpoint with an external account ID. Tokens can expire quickly, which can result in an unauthorized message.
• The events Authorization created and Transaction created include "corporate_metadata" in the "metadata" and "details" fields respectively. The "corporate_metadata" contains the following fields:
  • debit_external_account_id: The debited account in the creation operation.
  • earmark_id: The created earmark id.
• The event Earmark created, updated, or canceled only contains internal_operation that refers to the operation performed (Earmark update), it does not contain the complete list of all actions performed on the earmark. If the update action does not change the earmark amount, the internal_operation field is empty.
• If the account has any reason-based force debit restrictions, the force earmark update fails. The reasons that restrict force debit operations are:
  • Credit only — No force debit allowed
  • Any — No force allowed
  • Manual — No force allowed
• To find the correct reason IDs, refer to the List account status reasons endpoint.
• The maximum number of internal operation inputs (updates that change the earmark amount) allowed is 2,000. Updates that exceed this limit return bad request errors.
• An earmark balance cannot be reduced to zero as a result of this operation. If succussfully executing the request would result in a zero balance, the request fails and a bad request error is returned. If you want to reduce the balance to zero, you must use Cancel earmark, instead.