One post tagged with "plug-in"

We are introducing idempotency to a list of endpoints in the plug-in API. This is can be achieved by including the idempotency-ref header in the requests.

Effective:

• 12 August 2024 on Sandbox
• 20 August 2024 on Live

Using Idempotency is optional. However, if you decide to use it, you need handle the new HTTP 409 error code IDEMPOTENT_REQUEST_IN_PROGRESS. Additionally, if an idempotent endpoint is called with an idempotency-ref header exceeding 8000 characters, an HTTP 413 Payload Too Large error should be returned. If an idempotent endpoint is called twice with the same idempotency-ref but with different payloads, an HTTP 422 Unprocessable Entity error should be returned.

Affected endpoints with idempotency:

• Step up
  • POST/stepup/challenges/otp/{channel}
  • POST/stepup/challenges/otp/{channel}/verify
• Buyers
  • POST/buyers
  • POST/buyers/verification/email/send
  • POST/buyers/verification/email/verify
  • POST/buyers/kyb
• Buyer authorised users
  • POST/users
  • POST/users/{user_id}/activate
  • POST/users/{user_id}/deactivate
  • POST/users/{user_id}/invite
  • POST/users/{user_id}/invite/validate
  • POST/users/{user_id}/invite/consume
  • POST/users/verification/email/send
  • POST/users/verification/email/verify
• Payment Runs
  • POST/payment_runs
  • POST/payment_runs/{payment_run_id}/confirm
  • POST/payment_runs/{payment_run_id}/cancel
• Linked Accounts
  • POST/linked_accounts/{linked_account_id}/unlink

You can find more information about idempotency in our docs.