How to connect your Eneba account

This guide walks you through connecting an Eneba merchant account: collecting API credentials, whitelisting our server IP, publishing the DNS verification token and completing the in-app authorization. The whole process usually takes under ten minutes.

Before you start

1. Get your API credentials

In the Eneba dashboard open API → Credentials. Copy the production Auth ID and Auth Secret, and the sandbox Auth ID and Auth Secret (press Regenerate if a field is empty). You will paste all four into the wizard.

What it looks like in the Eneba dashboard:

2. Whitelist our server IP

Still under API → Credentials, add the server IP shown in the wizard to the allowlist. Eneba rejects every API call from an address that is not on this list, so the connection cannot work without it.

What it looks like in the Eneba dashboard:

3. Copy the DNS verification token

Open API → Domain verification and copy the TXT token (it starts with eneba-merchant-verification=). Paste it into the wizard — we publish it for your account and verify it is served before finishing.

What it looks like in the Eneba dashboard:

4. Run the in-app authorization

On the SendItNow Apps page choose Eneba and fill in the account name, both credential pairs and the DNS token, then press Authorize. The wizard validates your production credentials, confirms the IP whitelist and DNS record, and runs Eneba's sandbox certification suite — all in the app, no redirects. It usually takes under a minute.

5. Offers import in the background

Once connected, your live Eneba offers import automatically in the background. You can keep working — when the import finishes, review the AI-suggested matches and connect each offer to a product.

What you get after connecting

Price management

Active immediately after onboarding: offer import, pricing, repricing and profit tracking on your connected offers.

Troubleshooting

The wizard says my credentials are invalid.
Re-copy the Auth ID and Secret from API → Credentials — a Regenerate in the Eneba dashboard invalidates the old pair.
The IP whitelist check fails.
Confirm the exact server IP from the wizard is on the allowlist under API → Credentials, then retry. Changes can take a minute to propagate.
The DNS record is not found.
Make sure you pasted the full token, including the eneba-merchant-verification= prefix, then retry — the check re-reads the published file each run.
← All guides