Connect your tools
Use offer information in your own internal tools, catalogues, reporting workflows and supported integrations.
Build with AmaJova
The AmaJova Developer API provides a secure way to connect external applications and services to your AmaJova seller account. Read your own offers and recent orders, and create unpublished offer drafts, using credentials you control.
Manage API access
Seller account owners can create and revoke API keys in Dashboard Settings. Keys use scoped permissions to limit access.
Integrate securely
Make authenticated requests from your server, keep API keys private and handle responses using the published reference.
Connect a website for automatic fulfillment
Seller account owners can use Dashboard → Settings → Developer API → Webhooks → Add a website to register a secure HTTPS receiver. Configure the order.fulfilment_eligible event, save the one-time signing secret on your server, validate the receiver, and then enable the connection. In Offer Builder Step 7, choose Automatic Website Fulfilment and select the enabled website.
Your server must verify webhook authenticity, re-check the seller-owned order using an orders:read key, grant the purchased entitlement only when eligible, and send an authenticated fulfillment update using fulfillment:write. A webhook acknowledgement or buyer action alone does not mark the order delivered. Follow the website integration quickstart or read the webhook reference.
Availability: Website integrations require an enabled seller account, appropriate API permissions and a configured webhook receiver. Use the API endpoint and credentials for the environment where your seller account operates.
Available API capabilities
The API supports reading your own offers with offers:read, creating unpublished drafts with offers:write, and reading your own recent orders with orders:read. The Orders API is read-only: it cannot change, cancel or refund orders. Order listings return up to 50 recent orders; pagination is not supported.
Explore the API documentation or follow the quickstart guide to build your integration.
Structured website fulfillment
Report buyer actions, processing, failure or confirmed delivery using versioned JSON. Confirmed content can include website access, downloads, activation codes and instructions. Universal JSON contract, states and retry rules. A received JSON message or action button alone never marks an order delivered.