App Store

The appStore tag covers search, suggestions, app details, developer listings, collections, privacy, ratings, reviews, and similar apps under /v1/appstore/*. The operation names and parameter spellings are case-sensitive in the generated API Reference.

Choose an operation

Use GET /v1/appstore/search with term to search public App Store applications. Its optional parameters are num, page, country, lang, and idsOnly. For one application, use GET /v1/appstore/app with either id or appId; that operation also accepts country, lang, and ratings. GET /v1/appstore/list reads an iTunes collection using collection, with optional category, country, lang, num, and fullDetail.

For follow-up reads, the contract provides GET /v1/appstore/developer with devId, GET /v1/appstore/privacy with id, GET /v1/appstore/ratings with id, and GET /v1/appstore/reviews with id, appId, country, page, and sort. GET /v1/appstore/suggest accepts term, while GET /v1/appstore/similar accepts id or appId. Each operation reads public App Store data; use the API Reference for the response schema of the operation you select.

Make a request

Set REPLYNODES_API_KEY in a secret store and send it only in the authorization header. This example searches by term:

curl -sS \
  -H "Authorization: Bearer $REPLYNODES_API_KEY" \
  "https://api.replynodes.com/v1/appstore/search?term=calendar"

Successful HTTP API responses use the { data, meta } envelope, and meta.request_id is available for correlation. See Quickstart for key handling, Google Play for the other app-store guide, and the API Reference for required parameters.

Use this guide when an agent needs a normalized view of publicly available Apple App Store information without opening a private account or relying on a browser session. Start with search or suggestions when the app identifier is unknown, then use the detail operation to resolve the canonical listing and its metadata. Developer and collection routes help expand a result set, while privacy, ratings, reviews, and similar-app operations provide focused enrichment for research workflows. Keep the identifier, country, language, and pagination values returned by one request when following links into another operation; changing locale can change the visible listing and review set. Responses are read-only and should be treated as a snapshot of public upstream data, not as a guarantee of availability or a substitute for App Store policy documentation.

For exact request shapes, required fields, and response envelopes, consult the generated API Reference. Use the runtime capability document as the final authority when deployed routes differ from examples. Preserve request_id values in automated jobs so an operator can trace a failed read, and handle ordinary rate-limit or upstream-availability responses with bounded retries rather than repeatedly replaying every request.