Complementary Apps
The complementary apps routes show you which other apps an app’s users also use. Use them to find partners, cross-promotion targets, or competitors you didn’t know you had.
Every route scores each complementary app. Scores are estimates. A higher score means we estimate more audience overlap with the app you asked about. Scores are relative to that app, so compare them within one response, not across apps.
Grouping Complementary Apps by Category
Section titled “Grouping Complementary Apps by Category”This route returns complementary apps grouped by their main category, with the top apps in each.
Request
Section titled “Request”GET /complementary-apps?{filters}One request requires five (5) partner credits.
Arguments
Section titled “Arguments”| Field | Type | Description |
|---|---|---|
| unified_app | String | The Appfigures ID of the unified app to get data for. Set either unified_app or product, not both. |
| product | Product ID | The Appfigures ID of the app to get data for. We return unified apps either way. Set either unified_app or product, not both. |
| top | Number | The most apps to return in each category. Defaults to 10. |
| page | Number | A page number starting with 1. Defaults to 1. |
| count | Number | The number of categories per page. Defaults to 5. |
Response
Section titled “Response”The response is wrapped in an object that holds paging details (metadata.resultset) along with the results themselves (results key). Each result is a category. Categories are sorted by the score of their top app, highest first. Paging counts categories, not apps.
| Field | Type | Description |
|---|---|---|
| type | String | Always complementary-unified-category. |
| id | String | The unified category ID (ex. uc_DzgPsx). |
| depth | Number | How many complementary apps we found in this category, before the top limit. |
| unified_apps | List | The category’s top apps, sorted by score, highest first. Each has a type, id and complementary_score. |
Note: This route doesn’t fill in estimates. downloads_estimate and revenue_estimate come back with a null value. Its scores also aren’t scaled to 1, so you can’t compare them with scores from the other routes.
Example Response
Section titled “Example Response”// GET /complementary-apps? unified_app=ua_miTXv6 &top=2 &count=1
{ "error": null, "metadata": { "resultset": { "count": 1, "page": 1, "total_count": 22, "total_pages": 22 } }, "results": [{ "type": "complementary-unified-category", "id": "uc_DzgPsx", "depth": 31, "unified_apps": [{ "type": "unified-complementary-app", "id": "ua_xDxOtE", "complementary_score": "0.41", ... }, { "type": "unified-complementary-app", "id": "ua_vlOrxP", "complementary_score": "0.40", ... }] }]}