Skip to the page content

Marktmorgen is still being built. You can open a store and set it up today; its paid plans are not on sale yet. See what is built

Marktmorgen

Webhooks

Tell your other tools what just happened

Up to five addresses of your own, such as a Zapier Catch Hook, a Make scenario or your own server, told about sales, members, leads, bookings, refunds and disputes as they happen, in signed JSON.

Working todayAll plans; limits apply

Webhooks in the studio. The address, the times and the deliveries are an example.

How to connect a tool

  1. 1

    Add an address

    An https address, and the events it should hear. Its signing secret is shown to you once.

  2. 2

    Send a test

    One press sends a test message, and the delivery log shows what the address answered.

  3. 3

    Let it run

    Each event is sent when it happens. Those read from your Stripe account can take up to about five minutes.

Eleven events, and how they arrive

  • sale.completed and refund.issuedA paid checkout of any product, each one-click offer taken after it, and a refund, even one made in your Stripe dashboard.
  • membership.started and membership.canceledA membership bought, and a membership set to end or ended.
  • membership.changedA membership moved to another price or quantity on your Stripe account, such as an upgrade or a switch to yearly: what it was and what it is now.
  • dispute.openedA buyer disputed a payment made at your checkout: the amount, the reason Stripe reports and, when Stripe gives one, the date your answer is due.
  • lead.capturedSomeone confirmed their address for a free product.
  • list.joinedSomeone confirmed their address to join your email list, from your store page, a form or the checkout script on your own site.
  • call.booked and call.movedA call or a seat in a session booked and paid, and a booking the buyer moved.
  • sequence.stepSomebody reached a step of one of your sequences that tells your webhooks: their email, the sequence and the step, once for each person.
  • SignedEvery message carries a Marktmorgen-Signature header: an HMAC-SHA256 of its time and body under that address's secret.
  • Tried againWhen an address does not answer, the message is tried six more times over about forty hours, then marked failed.
  • A log you can readYour studio keeps the last 50 deliveries, each for up to seven days, with what the address answered.

What it does not do

  • There is no Marktmorgen app in Zapier's directory. In Zapier, use its Webhooks by Zapier trigger, Catch Hook.
  • Webhooks only send. To read your store from your own tools, use an API key: the API reads your list, members, a course's students, your affiliates and your bookings. A key made to write also adds people who agreed to your list, changes their labels and gives or takes back products, for Zapier, Make or your own server. The developers page lists every address.
  • Up to five addresses per store, https only, and redirects are not followed.
  • Each billing month covers a number of deliveries, every try, retry and test counted: 300 on the $69 plan, 1,000 on the $449 plan and 3,000 on the $999 plan. Past them a message is not sent, and the log says so.

Questions about webhooks

What are webhooks here?

An address in another tool, such as a Zapier Catch Hook, a Make scenario or your own server, that your store tells when something you pick happens: a sale, a refund, a membership starting or ending, a lead, an email-list sign-up, a booking or a sequence step. Each message is JSON, a format other tools read, signed so they can tell it came from us. Most are sent at once; sales, memberships and refunds, read from your Stripe account, within about five minutes. Up to 5 addresses per store.

How do I add a webhook?

In your studio, under “Webhooks and Zapier”, type the address under “Endpoint address (https)”, choose the events under “Send these events” (all are checked to start), and press “Add endpoint”. Its signing secret is shown to you once. Once your store has a plan or its trial, press “Send test” to see what the address answers. While a plan payment is unpaid or disputed, no test is sent.

Can I try webhooks before paying?

Yes. Paid plans are not on sale yet, so there is nothing to pay for now, and you can set up a webhook address and its events in your own store's studio with no card. Files and lesson videos can be uploaded once a paid plan starts. Until a plan is paid, your store has smaller limits, for the whole trial or each month without a plan, and only so many stores without a paid plan can run each month, so some of its work can pause for a while. To see a store working, open the live demo store from the link at the end of this page: a made-up store, marked as a demo. Without a plan, nothing is sent, not even a test: a store with no plan, or whose plan ended, has no webhook deliveries to use, and a test counts as one.

Do webhooks work with Zapier?

Yes, through Zapier's own Webhooks by Zapier trigger, Catch Hook; check that your Zapier plan includes it. There is no Marktmorgen app in Zapier's directory. Paste the Catch Hook's address as an endpoint and pick its events; Zapier does not need the signing secret.

How do I know a message came from you?

Check its Marktmorgen-Signature header against the secret you were shown when you added the address, and check that its time is recent. When you make a new secret, the old one keeps signing beside it for a day, as a second v1 in the same header: accept a message when any v1 matches.

What if a message did not arrive?

It is tried again by itself for about forty hours. If it still failed, press Send again beside it in your studio's log: the same message, with the same event id, is sent once more, so a receiver that already has it can ignore the repeat.

What if the same event arrives twice?

Every event has an ID made from what it is about, and it is sent once however often it is noticed. Keep the IDs you have seen and ignore a repeat, in case a retry crosses a slow answer.

Does Stan have webhooks?

Not according to its help center, read on September 17, 2026.

A practical way to use it

  1. 1

    Let another tool react to a recorded event

    Configure the supported events your service needs and verify the signed request it receives. Your service can use that record in its own workflow; retries and delivery limits still apply.

Check the terms before you commit

Your work stays yours. Read how payments, data and leaving the platform work, then decide whether the fit is right.

  • Your own Stripe account

    Direct charges use the creator’s Stripe account. Stripe processing, payout timing, refunds and disputes still apply.

    Follow the payment path
  • Your records can leave with you

    Export the contact and order records your role can access. Keep a copy before closing a store; export does not move subscriptions to another provider.

    Read the data policy
  • Cancellation from your studio

    Manage an existing platform subscription through Account. Review its end date and what closing a store changes for buyers.

    Review cancellation terms
  • A clear platform refund policy

    The first platform payment can be requested back in full within 30 days, under the Terms. A buyer’s refund for a creator’s product follows that offer and applicable rights.

    Read the refund terms

Paid plans and paid selling remain subject to all opening gates. These terms do not mean sales are open or that earnings are guaranteed.

Prepare your own store

Take your address and put your first product up today. The plan is $69 a month and 0% of your sales, and it is not on sale yet.