Skip to main content
HotWax setup is a one-time task — save the connection once and every reconciliation run or automation that reads HotWax order data can use it from then on.
Keep passwords, JWT bearer tokens, API keys, customer hostnames, and account-specific values in secure configuration. The docs should describe the sequence, not store credentials.

​
Before you start

Confirm:
  • You are signed in to the correct active company or active tenant.
  • Your user can edit connection settings.
  • The HotWax Moqui API URL is known.
  • The HotWax authentication type is known: none, basic, bearer, or API key.
  • The required username, password, JWT bearer token, or API key is available in secure configuration.
  • The HotWax orders endpoint is available for the tenant.

​
Steps

1

Open HotWax settings

Open Ask Darpan with Cmd/Ctrl+K or the floating Ask Darpan button. Search for Open HotWax Settings and open the result.
2

Create the HotWax connection

Choose Create Auth Profile. Answer the setup questions:
  1. Base URL: use the HotWax Moqui API URL, not the storefront, admin app, or another system URL
  2. Timezone: which timezone Darpan should use for HotWax date windows
  3. Auth Type
  4. Username and password for basic auth, a JWT token retrieved from HotWax when Bearer is selected, or an API key when the auth type requires it
  5. HotWax label
For bearer authentication, use the JWT token value from HotWax. Darpan sends it as the HTTP Authorization: Bearer <jwt-token> header.Save the connection. Darpan creates it as active and derives the connection ID from the label. If the ID, active state, auth details, or endpoint access needs to change later, open the saved connection from Open HotWax Settings and edit it.
3

Confirm the connection is reusable

Return to Open HotWax Settings. The saved connection should appear on the settings surface.The connection is ready when a reconciliation run or automation can select HotWax as an API source.

​
Validation

Use a small read-only reconciliation run or automation test with a narrow date range. Confirm HotWax returns orders before using the setup for scheduled reconciliation.

​
Troubleshooting

  • If HotWax fails, check the Moqui API URL, auth type, bearer token validity, API key header behavior, and tenant context.
  • If HotWax does not appear as an API source, confirm the connection is active and that Orders API is enabled on the saved record.
  • If the request succeeds but returns no records, test a wider date range and confirm the tenant has orders for that period.