Testing your integration

Test keys, the dashboard console, and what to check before going live.

Test keys (esl_test_…) go through authentication, the rate limit, validation, the queue and the merge exactly like live keys, and then stop: nothing is written and no label changes. Batch results report what would have happened.

The dashboard console

The POS API page of the dashboard has a console that sends real requests with a key you paste in and shows the raw response, its headers and the batch as it progresses. It is the quickest way to confirm a key and a store code work.

Before going live

1. 1

   Send a full catalogue with a test key and check the batch reports no rejected products.

2. 2

   Handle 429 and 503 with backoff, and log X-Request-Id with every request.

3. 3

   Send changedAt with every product.

4. 4

   If you use webhooks, verify signatures and deduplicate on the event id, then send a test from the dashboard.

5. 5

   Swap in a live key and send one product. Watch its label change.