Skip to main content

Idempotence

The NOAH Business API includes support for idempotence, crucial for safely retrying requests without duplicating operations.

  • This feature is especially useful to prevent unintended multiple executions in scenarios of failures and retries.

Using Idempotence Nonces​

All our Transactional Endpoints, endpoints which lead to the creation of a transaction, require a Nonce value which must be unique for each transaction. It guarantees that the same endpoint will not overwrite nor duplicate transactions with the same Nonce. This allows for safely retrying requests. You should ensure that your system uses a unique nonce for each transaction you attempt to create.

Creating Idempotence Nonces​

  • The choice of method for generating unique nonces is flexible and the maximum length for a nonce is 36 characters.
  • Ensure that the Nonce is not used in another transaction.
  • You could use e.g. a high entropy UUID or a unique identifier automatically generated by your database.
  • Nonces is specific to your Business user.