Digistore24
Digistore24 digital-product commerce: purchases, refunds and rebilling, buyers, products, affiliate commissions, vouchers, deliveries and IPN connections.
About
Digistore24 ships in the w6w first-party pack. It declares 36 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.digistore24- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments
Overview
Digistore24 is a digital-product marketplace and payment platform: vendors sell courses, software and subscriptions, affiliates promote them for a commission, and Digistore24 handles checkout, tax, invoicing and payouts as the merchant of record.
This app gives a workflow the vendor’s side of that account. Read purchases and their transactions, look up the buyer behind an order, refund a purchase (fully, partially, or one transaction) and stop or resume a subscription’s rebilling, or resend the confirmation mail. Manage the catalogue by listing, reading, creating and updating products, set an affiliate’s commission per product, and run voucher codes. For physical goods, read and update deliveries with tracking data. IPN connections can be listed, created and removed, so a workflow can register itself as the receiver of Digistore24’s instant payment notifications.
A key can be read-only or writable on Digistore24’s side: with a read-only key every action that changes data is refused by the vendor, so scope the key to what the workflows using this connection actually do.
Build with Digistore24
Three routes to the same 36 actions. The Workflow tab is generated from Digistore24's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Product
create-product Create a product. Pass the product's properties as a JSON object, e.g. name_intern, name_en, currency, salespage_url, affiliate_commission.
Get Affiliate Commission
get-affiliate-commission Return an affiliate's commission settings on your products.
Get Purchase
get-purchase Return the full detail of one purchase: buyer, items, payment, billing and affiliate data.
Get User Info
get-user-info Return the account the API key belongs to: user id, login name and granted roles.
Get IPN Connection
ipn-info Return the settings of an IPN (instant payment notification) connection created via IPN Setup.
Set Up IPN Connection
ipn-setup Create an IPN connection so Digistore24 posts payment notifications to a URL. Re-using a domain ID is how a connection is identified for deletion.
List Purchases
list-purchases List your sales in a period, including those where you earn a commission (e.g. joint ventures). Filters mirror Digistore24's search criteria.
List Transactions
list-transactions List payments, refunds and chargebacks you earn a commission on, including joint-venture sales.
Refund Partially
refund-partially Refund part of a payment. The amount is treated as a discount and the order status does not change.
Resend Purchase Confirmation Mail
resend-purchase-confirmation-mail Send the purchase confirmation email to the buyer again.
Get Sales Summary
stats-sales-summary Return revenue totals for all time, the year, quarter, month, week and day.
Stop Rebilling
stop-rebilling Stop the recurring payments of a subscription or installment purchase.
Update Affiliate Commission
update-affiliate-commission Set an affiliate's commission on one or more of your products. Products without an affiliation get one created; with product IDs = all only existing affiliations change.
Update Product
update-product Update a product. Pass only the properties to change as a JSON object.
Update Purchase
update-purchase Change an order's tracking data, custom field, invoice access, or push out the next rebilling payment.
Update Voucher
update-voucher Update a voucher identified by its code or ID. Renaming is not exposed: the vendor spec reuses the name `code` for both the identifier and the new value, so it cannot be told apart on the wire.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Digistore24's real ids.
{
"manifestVersion": "2",
"name": "digistore24-example",
"steps": [
{
"id": "create-product",
"uses": {
"app": "io.w6w.digistore24",
"action": "create-product",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"data": "<data>"
}
}
]
}Here are some of the things you can do
-
Create Product
performcreate-product -
Create Voucher
performcreate-voucher -
Get Affiliate Commission
readget-affiliate-commission -
Get Buyer
readget-buyer -
Get Delivery
readget-delivery
+31 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Digistore24, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Digistore24. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "create-product",
payload: {
data: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-product --payload '{"data":"<value>"}'Give an AI agent Digistore24 — without giving it Digistore24's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.digistore24#create-product",
"input": {
"data": "<data>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Digistore24 connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Digistore24's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Digistore24 itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Digistore24 declares its own checks, so its health is a property of the app rather than something the host guesses at.
Digistore24 platform status
Status of the Digistore24 component on status.digistore24.com (the platform and its API). The page's other component, Digibiz24, is a separate product and is not read.
Digistore24 API reachability
Unauthenticated GET /api/call/ping. A schema-correct result:error envelope (no API key) proves the API answered; credential validity is checked separately.