Connect Hotmart

Send your Hotmart sales, renewals, refunds and chargebacks to Clakta over a webhook, and credit each sale to the visitor who made it.

Connecting Hotmart sends every approved sale, renewal, refund and chargeback to Clakta as it happens. It takes one webhook, set up in three short steps: copy a URL from Clakta, create the webhook in Hotmart, then paste your hottok back into Clakta.

Connect

1. In Clakta — create the connection

Go to Project settings → Sales platforms, choose Hotmart, give the connection a name, and click Create connection. Clakta generates a webhook URL — copy it.

2. In Hotmart — create the webhook

Open Tools in the left menu, click View all, then search for Webhook and open it. Click Add webhook at the top of the page and fill in:

  • Name — anything you like. It is only a label to help you recognise it.
  • Products — select all of them.
  • URL — paste the URL you copied from Clakta.
  • Version — leave it on 2.0.0, the recommended option.
  • Events — select all of them.

Save.

3. Back in Clakta — paste your hottok

Still on Hotmart's Webhook page, open the Authentication tab and copy your hottok. Paste it into Clakta and click Finish.

The card reads Added once the hottok is saved.

The hottok belongs to your Hotmart account, not to a single webhook — the same value works for every webhook you create.

Events

Selecting all of them is the simplest thing to do, and it is safe: anything Clakta does not handle is accepted and ignored. These four are the ones that change what you see:

Event (in Hotmart)What it does in Clakta
Purchase approvedRecords the sale, and each renewal as its own sale.
Purchase refundedMarks the order refunded.
ChargebackMarks the order refunded.
Purchase canceledMarks the order canceled.

Attribute sales to visitors

A Hotmart checkout link carries a free field, sck, and the tracking script fills it in for you: when a visitor clicks a link to pay.hotmart.com — or a go.hotmart.com hotlink — on your site, their session id is appended before the click goes through. Hotmart stores it with the purchase and reports it back on the webhook, so the sale is credited to the visit that produced it.

You only need to build the URL yourself for a checkout the script can't see — a server-side redirect, say, or a framework router link:

An sck you set yourself is never overwritten, and your other tracking parameters are left alone — xcod in particular carries Hotmart's affiliate code, so Clakta never touches it. Sales still arrive without an sck; they are just recorded as unattributed, so you see the revenue but not the traffic behind it. UTMs on the checkout link are recorded either way.

What gets recorded

The amount the buyer paid, in the sale's own currency; the buyer's name and email; the product; the payment method; the approval date; and the attribution from sck and any UTMs. Cards, Pix and boleto are recorded by name, and anything else — PicPay, Hotmart's wallet, the financing options — reads Other.

Refunds and chargebacks

Both mark the order refunded. A refund for a sale that predates the connection is ignored rather than invented — Clakta never saw the original order, and creating one on the refund date would report revenue on a day it never happened.

Disconnect

Remove the connection from Project settings → Sales platforms. Deliveries stop being accepted immediately, and orders already recorded stay where they are. Delete the webhook in Hotmart too, so it stops retrying against an endpoint that no longer exists.

Troubleshooting

Hotmart keeps a history of every delivery on the Webhook page, under My settings. It shows what each one returned and lets you resend the ones that failed, for up to 60 days.

Related articles