Digistore24 MCP integration for AI agents.
Connect AI agents to Digistore24 through 7 structured actions, including get buyer, get product, and get purchase. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Digistore24 integration exposes
The Digistore24 Agent App exposes 7 provider-backed actions for finance and marketing work. Its current contract lets an authorized agent retrieve details for a digistore24 buyer, retrieve details for a digistore24 product, and retrieve details for one or more digistore24 purchases. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Digistore24 account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Digistore24 capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_buyerREADRetrieve details for a Digistore24 buyer.
INPUTS: buyerId
get_productREADRetrieve details for a Digistore24 product.
INPUTS: productId
get_purchaseREADRetrieve details for one or more Digistore24 purchases.
INPUTS: purchaseId
get_user_infoREADRetrieve information about the Digistore24 user that owns the API key.
list_buyersREADList buyers from the connected Digistore24 account.
INPUTS: pageNo / pageSize
list_productsREADList products from the connected Digistore24 account.
INPUTS: sortBy
list_purchasesREADList purchases and sales from the connected Digistore24 account.
INPUTS: from / to / search / sortBy / sortOrder
INPUT CONTRACTS
Know what the action needs before it runs.
get_buyer
buyerIdREQUIRED- Numeric ID of the buyer to retrieve.
get_product
productIdREQUIRED- Numeric ID of the product to retrieve.
get_purchase
purchaseIdREQUIRED- Single purchase ID or comma-separated purchase IDs to retrieve.
list_buyers
pageNoOPTIONAL- Page number to request. Digistore24 pages start at 1.
pageSizeOPTIONAL- Number of items to request per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Buyer
Retrieve details for a Digistore24 buyer. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_buyerVerify with Get Product
Retrieve details for a Digistore24 product. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_productSAFETY BOUNDARY
Operate Digistore24 with explicit limits
- Authorize Digistore24 with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Digistore24 data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Digistore24 rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Digistore24 task completed successfully.
CONNECTION MODEL
API key
Digistore24 API key sent with the X-DS-API-KEY header. Create it in vendor view under Settings > Account access > API keys: https://help.digistore24.com/hc/en-us/articles/23658595845009-Create-API-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Digistore24.