Skip to main content
When you approve a price in Elastly, it lands in a queue for your connector. Drain it on whatever schedule fits: claim a batch, write each price into your system, then acknowledge what landed. A claim leases the tasks, so two workers never apply the same price. Set up your client first (see the overview).
The connector framework drains write-backs for you, with leases handled. Read this page when you want to claim and acknowledge yourself.

Claim, apply, acknowledge

Delivery is at-least-once, so make your write idempotent. A task whose ack never arrives returns to the queue and reaches you again. Setting the same price twice should be harmless. When you acknowledge, expired counts tasks whose lease had already run out; those went back to the queue, so claim again and reapply. Each task carries both productSku and productExternalId, so you can match it however your system keys products. The claim and acknowledge endpoints document every field.