Skip to main content

Overview

All POST requests in the HopNow API require an Idempotency-Key header to prevent duplicate operations. This ensures safe retries when network errors or timeouts occur.
Do not include an Idempotency-Key with GET, PUT, PATCH, or DELETE requests. These methods are naturally idempotent.

How It Works

  • Include a unique Idempotency-Key (UUID format) in every POST request
  • If a request is retried with the same key, HopNow returns the original response without performing the operation again
  • This prevents duplicate payments, account creations, or other operations

Request Example

Generating Keys

Use UUIDs for each new operation:

Best Practices

Store Keys in Your Database

Track idempotency keys with request state for reliable retry logic:

Retry with Same Key

Always reuse the same idempotency key when retrying failed requests:

Common Errors

Invalid Format

Solution: Use a properly formatted UUID (e.g., 550e8400-e29b-41d4-a716-446655440000)

Conflicting Request Body

Solution: Use the same request body as the original request, or generate a new idempotency key for a different operation.