TrackStar APItrackstar.info ↗
Query the current download status of the TrackStar NYC iPhone app: beta program details, distribution channel, App Store availability, and FAQ text.
What is the TrackStar API?
The TrackStar.info API exposes 1 endpoint, get_app_availability, returning 9 structured fields about the current release status of the TrackStar NYC iPhone app. You get the verbatim status paragraph, distribution channel, beta program name, App Store listing flag, platform tags, and the site's own FAQ answer on how to obtain the app — all from the homepage status section in a single call.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/63040b5b-ed90-4b27-8ca9-131b611e6ad9/get_app_availability' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace trackstar-info-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: check TrackStar app availability and follow-up links."""
from parse_apis.trackstar_info_api import TrackStar, ParseError
client = TrackStar()
# Fetch current availability status for the TrackStar app.
try:
info = client.availability.get()
except ParseError as e:
# Site layout may change; surface the structured error code.
print(f"Could not parse availability: {e.code}")
raise
print(f"{info.app_name} ({info.beta_name}) — {info.platform}")
print(f"Private beta: {info.private_beta}, On App Store: {info.on_app_store}")
print(f"Distribution: {info.distribution}")
print()
# Show the verbatim status paragraph from the site.
print(info.status_text)
print()
# Walk the structured follow-up links.
for link in info.links:
print(f" {link.label}: {link.url}")
print()
print(f"Data sources: {info.data_sources_text}")
print("\nexercised: availability.get / Link fields / all scalar fields")
Returns the current download/availability status of the TrackStar app as published on the site's homepage status section and FAQ: platform, distribution channel (currently a private TestFlight beta), whether it is listed on the App Store, the beta build name, the hero tags shown on the homepage, the verbatim status and FAQ text, the follow-up links the site offers (contact/about), and the data-sources note. The site publishes no downloadable files or store links; this endpoint is the whole of its download-related information. Two page fetches per call; no inputs; never empty when the site is up. Boolean fields are derived from the status text: distribution and platform are null if the text no longer names them.
No input parameters required.
{
"type": "object",
"fields": {
"links": "array of {label, url} follow-up links offered in the status section",
"app_name": "product name shown on the site",
"platform": "device platform named in the homepage hero (null if absent)",
"beta_name": "name the app carries in the beta program, or null if the status text no longer states one",
"hero_tags": "array of short tag strings shown above the homepage headline (platform, city, stage)",
"status_text": "verbatim 'Where things stand' status paragraph",
"distribution": "channel the app is distributed through (null if the status text no longer names one)",
"on_app_store": "boolean, false while the status text says the app is not on the App Store",
"private_beta": "boolean, true while the status text says the app is in private beta",
"how_to_get_app": "verbatim FAQ answer to 'How do I get the app?'",
"data_sources_text": "verbatim note on where the app's show/release data comes from, or null"
},
"sample": {
"data": {
"links": [
{
"url": "https://trackstar.info/contact/",
"label": "Contact"
},
{
"url": "https://trackstar.info/about/",
"label": "About the app"
}
],
"app_name": "TrackStar",
"platform": "iPhone",
"beta_name": "TrackStar NYC",
"hero_tags": [
"iPhone",
"New York City",
"Private beta"
],
"status_text": "TrackStar is in private beta on TestFlight under the name TrackStar NYC. It is not on the App Store yet, and it covers New York City first. If you would like to try it, get in touch.",
"distribution": "TestFlight",
"on_app_store": false,
"private_beta": true,
"how_to_get_app": "It is in private beta on TestFlight as TrackStar NYC and is not on the App Store yet. Contact us if you would like to try it.",
"data_sources_text": "Show and release data comes from Ticketmaster, SeatGeek, Apple Music, MusicBrainz, Wikidata, Spotify and Deezer."
},
"status": "success"
}
}About the TrackStar API
What the API Returns
The single endpoint, get_app_availability, returns a structured snapshot of how the TrackStar NYC iPhone app is currently distributed. The status_text field contains the verbatim 'Where things stand' paragraph from the site, while how_to_get_app is the exact FAQ answer the site provides. Together these two fields give you the source's own words, not an interpretation.
Key Fields
The response includes on_app_store (a boolean, currently false while the app remains outside the App Store), private_beta (a boolean, currently true), and distribution (the named channel, presently TestFlight). beta_name records the name the app carries inside the beta program. hero_tags returns the short tag strings — platform, city, stage — shown above the homepage headline, and platform isolates the device platform named in the hero.
Links and Metadata
The links array surfaces any follow-up URLs the status section offers, each as a {label, url} pair, so you can surface actionable sign-up or waitlist links without scraping the page yourself. app_name returns the product name as the site displays it.
Endpoint Inputs
The get_app_availability endpoint takes no inputs. There are no filters, query parameters, or pagination — the response always reflects the current published state of the single status section.
The TrackStar API is a managed, monitored endpoint for trackstar.info — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when trackstar.info changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official trackstar.info API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor when
on_app_storeflips to true to trigger an alert the moment TrackStar NYC lists on the App Store. - Track changes to
distributionto detect if the beta moves from TestFlight to a public channel. - Embed the
status_textparagraph in an internal dashboard so transit teams follow the app's rollout without visiting the site. - Pull
hero_tagsto programmatically confirm which city and stage the app is currently tagged as. - Store
private_betastate over time to build a timeline of the app's release progress. - Surface
how_to_get_appFAQ text in a chatbot or Slack bot that answers user questions about accessing the beta. - Use the
linksarray to automatically surface the latest sign-up or waitlist URLs in downstream tooling.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TrackStar.info have an official developer API?+
What does the `on_app_store` field actually tell me?+
false while the app is in private beta and not publicly listed. private_beta and distribution give you the complementary detail — the current channel (TestFlight) and beta state.Does the API return historical availability states or a changelog?+
Does the API cover Android availability or platforms other than iPhone?+
platform field reflects whatever device platform the site's homepage names, which at the time of writing is iPhone only. If TrackStar publishes Android or web availability, that would appear in status_text and hero_tags but no separate Android-specific field exists. You can fork the API on Parse and revise it to add a dedicated Android field once the site covers that platform.