domain: payhip.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine whether you're integrating against the current v2 or legacy v1 license API, since they use different auth models
For v2, call GET https://payhip.com/api/v2/license/verify?license_key=... with a product-secret-key header (a per-product secret, not an account-wide API key)
For legacy v1, call GET https://payhip.com/api/v1/license/verify with product_link and license_key as query-string params and a payhip-api-key header
Read the response fields (enabled, product_link, license_key, buyer_email, uses, product_name, variant_name) to determine entitlement
Use the corresponding enable/disable endpoints (PUT) with the same param pattern to programmatically revoke or restore a license
Known gotchas
v1 and v2 use different auth models (account-ish per-product secret vs. general API key) and different HTTP methods for verify — mixing up the GET query-string v1 call with the v2 pattern is a common integration mistake
Payhip's public API is scoped almost entirely to license-key verification/enable/disable — there is no documented broad products/sales/orders API beyond this
Confirm the exact current endpoint path against payhip.com/api-reference before shipping, since v1 is being superseded and documentation may shift
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?