Use the Podia CLI from KosmoKrator to call Podia tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Podia can be configured headlessly with `kosmokrator integrations:configure podia`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure podia --set access_token="$PODIA_ACCESS_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor podia --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Bearer tokenbearer_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
access_token
PODIA_ACCESS_TOKEN
Secret secret
yes
Access Token
url
PODIA_URL
URL url
no
API Base URL
Call Podia Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Podia.
podia.podia_list_products
Read read
List all online courses and digital downloads in your Podia account. Returns product names, IDs, types, and metadata.
Get detailed information about a single Podia product by its ID. Returns full product data including description, price, type (course or download), and purchase URL.
List sales from your Podia account. Optionally filter by product ID, date range, or page. Returns sale details including buyer info, amount, and product.
Get detailed information about a single Podia product by its ID. Returns full product data including description, price, type (course or download), and purchase URL.
List sales from your Podia account. Optionally filter by product ID, date range, or page. Returns sale details including buyer info, amount, and product.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.