canonical: https://jentic.com/apis/buy-app-downloads.com/buy-app-downloads # Buy App Downloads API The Buy App Downloads API lets an agent order app installs and manage the listings and orders behind them. It can list and create app listings, read or delete a single listing, place and list download orders, read or delete a single order, and list the countries installs can be targeted at. It is a user-acquisition service for mobile apps. ## For AI agents Order app installs and manage listings and orders through the Buy App Downloads API. List or create apps, place and track download orders, and read supported countries. Secured with a bearer token. ## Scope Does not handle app store publishing or install attribution - use it to order app downloads and manage the orders behind them. ## Capabilities - List and create app listings - Retrieve or delete a single app listing - Place and list download orders - Retrieve or delete a single order - List the supported countries ## Use cases ### Order app installs Drive app installs programmatically. The agent places a download order for a listed app and targets it at the supported countries. Example prompt: Call POST /orders to place an install order for an app ### Manage app listings Keep the set of promoted apps current. The agent creates listings, reads them back, and removes listings that are no longer promoted. Example prompt: Call POST /apps to create a listing, GET /apps to review them ### Track order status Report progress on running campaigns. The agent reads a single order to check its status and lists orders to summarise what is in flight. Example prompt: Call GET `/orders/{id}` to read the status of an order ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/apps` | List app listings | | POST | `/apps` | Create an app listing | | GET | `/apps/{id}` | Retrieve a single app listing | | DELETE | `/apps/{id}` | Delete an app listing | | GET | `/orders` | List download orders | | POST | `/orders` | Place a download order | | GET | `/orders/{id}` | Retrieve a single order | | DELETE | `/orders/{id}` | Delete an order | ## Key resources - **Apps** — App listings that can be promoted for installs - **Orders** — Download orders placed against a listed app - **Countries** — Countries that installs can be targeted at ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 55 / 100 - Developer Experience & Jentic Compatibility: 57 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 53 / 100 - **View full report:** https://jentic.com/apis/buy-app-downloads.com/buy-app-downloads/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Buy App Downloads API by hand means managing a bearer token, pointing at the buy-app-downloads.com host, and shaping the order requests yourself. Through Jentic you install once, import the Buy App Downloads API from the Jentic API Directory, store the token once, and your agent calls it. - **Permission scoping:** You decide which operations your agent may call, so it can read orders without being able to place or delete them. Because the order id sits in the URL path (`/orders/{id}`), a rule can pin the agent to a single order rather than the whole account. - **Credential handling:** Your Buy App Downloads bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'order app installs' or 'check an order status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference. ## Related APIs - **TikTok** — Alternative app marketing and promotion channel - **Adjust** — Complementary mobile install attribution API - **Mailchimp** — Complementary marketing campaign API ## FAQ ### What authentication does the Buy App Downloads API use? The Buy App Downloads API uses a bearer token. Through Jentic, that token is stored encrypted in your Jentic One instance and injected at execution time, so the raw token never enters the agent context. ### What can an agent do with the Buy App Downloads API? It can list and create app listings, read or delete a single listing, place and list download orders, read or delete a single order, and list the supported countries. The service is built for programmatic app user acquisition. ### How does an agent connect to the Buy App Downloads API through Jentic? Install Jentic One, import the Buy App Downloads API from the Jentic API Directory, and store the bearer token once. Your agent then calls the operations you have allowed without handling the raw token. ### What are the rate limits for the Buy App Downloads API? Rate limits are not specified in the OpenAPI spec. Check the Buy App Downloads documentation for current limits. Through Jentic, retries are handled in the execution layer. ### How many endpoints does the Buy App Downloads API have? The Buy App Downloads API exposes 9 endpoints covering apps, orders, and supported countries. ### Can I limit what my agent is allowed to do with the Buy App Downloads API? Yes. Jentic One is self-hosted by you, so your own rules decide which operations your agent may call. You can let it read orders without being able to place or delete them, and because the order id sits in the URL path, such as `/orders/{id}`, a rule can pin the agent to a single order.