/vivo/apps/topics

POST /api/vivo/apps/topics

Price: 20 credits

List the editorial collections the vivo App Store is featuring on its storefront tabs

How to use it

This is where topic ids come from: pass an id from here to /vivo/apps/topic to open the whole collection. The three storefront tabs feature different collections and shared none when compared, so leave chart unset for the whole line-up and set it when you want one tab. Unlike the app feeds behind /vivo/apps/charts, this list held steady across repeated calls, so read it as the store's current editorial line-up rather than a per-call sample. with_apps's preview stops at twelve apps however large app_count is, the cards in the banner placement carry none at all, and its membership is resampled between calls, so /vivo/apps/topic is what returns a collection's actual contents.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chart string nullable — Read only one storefront tab instead of all three (one of: "recommended", "app", "game")
• with_apps boolean — Include the apps each collection previews on the storefront (default: false)
• count integer required — Max number of collections to return (min: 1)

Response

• @type string (default: "VivoTopicCard")
• id integer required
• name string required
• subtitle string nullable
• description string nullable
• image string nullable
• thumbnail string nullable
• app_count integer nullable
• chart string (default: "")
• placement string (default: "")
• web_url string nullable
• preview_apps array (default: [])
  • @type string (default: "VivoApp")
  • id integer required
  • name string required
  • package_name string required
  • short_name string nullable
  • developer string nullable
  • version string nullable
  • version_code string nullable
  • size_kb integer nullable
  • download_count integer nullable
  • rating number nullable
  • rating_count integer nullable
  • tagline string nullable
  • description string nullable
  • changelog string nullable
  • icon string nullable
  • screenshots array (default: [])
  • video_url string nullable
  • video_cover string nullable
  • is_game boolean nullable
  • is_online_game boolean nullable
  • is_official boolean nullable
  • has_ads boolean nullable
  • category string nullable
  • category_id integer nullable
  • subcategories array (default: [])
  • subcategory_ids array (default: [])
  • badges array (default: [])
  • md5 string nullable
  • released_at integer nullable
  • updated_at integer nullable
  • privacy_policy_url string nullable
  • icp_license string nullable
  • icp_operator string nullable
  • security_scans array (default: [])
  • download_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.