Before You Start
Before making your first API call, make sure you have the following:
✅ A FoxData account — Sign up here
✅ An active API subscription
✅ Basic familiarity with API requests— understanding HTTP requests and JSON responses is helpful, but not required for getting started
How to Subscribe to FoxData API
FoxData uses a modular pricing structure. API access is available under the API Solutions tier, separate from ASO Intelligence and Ad Intelligence plans.
Step-by-Step: Activating API Access
Step 1: Go to the FoxData plans.
Step 2: Locate the API Solutions section.
Step 3: Review available plans and select the one that matches your expected data usage and module requirements.
Step 4: Complete your subscription or contact the FoxData team for enterprise or custom plans.
Step 5: Once your subscription is confirmed, you will receive your API key — a unique authentication token that identifies your account on every request.
⚠️ Keep your API key secure. Do not expose it in public repositories or client-side code.
💡 Not sure which plan is right for you? Talk to our sales to help you find the best fit.
Quick Start: Making Your First API Request
Full documentation is available at: FoxData Open API Documentation
Follow these three steps to make your first successful call.
Step 1: Prepare Information
Before making your first call, have the following ready:
● Base URL: https://api.foxdata.com/apiv1/open-api
● License: Used for authentication
● API Path: We recommend starting with App Basic Information
Note: Authentication relies on x-openapi-key. See Step 2 for details.
Step 2: Obtain Your License (API Key)
After activating your account via the FoxData Personal Center or through a sales representative, you will receive an authorization key:
● Header Name: x-openapi-key
● Value: Your License (the actual key provided to you upon subscription)
Step 3: Make Your First Call — Example: App Basic Information
The following example demonstrates how to “query the basic information of an app in the app store (including title, subtitle, description, images, etc.)”.
● API Endpoint: POST /app/app-info
● Authentication: Include x-openapi-key in the request header
● Request Body: JSON
cURL Example:
curl -X POST "https://api.foxdata.com/apiv1/open-api/app/app-info" \
-H "Content-Type: application/json" \
-H "x-openapi-key: YOUR_LICENSE" \
-d '{
"appId": “com.run.tower.defense”,
"region": "US",
"language": "en_US"
}'
Parameters:
● appId: Application identifier (App ID in the App Store, Bundle ID in Google Play)
● region: Country/region (e.g., US)
● language: Language (optional; e.g., en_US)
Step 4: Understand the Response
The API returns structured JSON. A successful response looks like this:
{
"code": 200,
"msg": "success",
"data": {
"requestParam": {
"appId": "com.moye.shelter",
"region": "US",
"language": "en_US"
},
"result": [
{
"appId": "com.moye.shelter",
"appName": "Gods & Demons",
"icon": "https://...",
"subtitle": "...",
"descriptions": "...",
"category": "Social Networking",
"categoryId": "7014",
"status": "ONLINE"
}
],
"creditsCost": {
"requestCredits": 0,
"baseCredits": 10,
"extraCredits": 0,
"totalCostCredits": 10
}
}
}
Key fields to note:
● Success: Generally indicated by code=200 and msg=success (subject to the actual response from the API)
● Business data: Typically found in data.result
● Credits consumed: Typically found in data.creditsCost.totalCostCredits
Troubleshooting
Here are the most common issues and how to resolve them:
❌ Invalid API Key
Error: 401 Unauthorized
Cause: The API key is missing, incorrect, or expired.
Fix:
● Double-check that you're including the header: x-openapi-key: YOUR_API_KEY
● Verify your key is correct in your account settings
● If your key has expired, generate a new one or contact support
📭 Empty Data Results
Error: 200 OK but data is empty or null
Cause: The app ID doesn't exist, or data is unavailable for the requested market/time range.
Fix:
● Confirm the app ID is correct for the specified platform (ios vs. android)
● Try a different country code or broader date range
● Check that the endpoint supports the market you're querying
🚫 Rate Limit Exceeded
Error: 429 Too Many Requests
Cause: You've exceeded your plan's request limit.
Fix:
● Slow down request frequency and implement retry logic with backoff
● Review your current usage in the account dashboard
● If you consistently hit limits, consider upgrading your plan
🔧 Unexpected Response Format
Cause: API version mismatch or deprecated endpoint.
Fix:
● Check the API documentation to confirm you're using the latest endpoint version
● Review any deprecation notices in your account or the changelog
For any other questions, please visit: Product Feedback