Longevity World Cup Public API
Public no-auth JSON endpoints for Longevity World Cup athlete, Event, field, biological aging clock calculation, and rank-preview data. The documented…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Public no-auth JSON endpoints for Longevity World Cup athlete, Event, field, biological aging clock calculation, and rank-preview data.
The documented endpoints are public data and biological aging clock calculation surfaces used by the website and external clients.
Access for every documented endpoint:
- Auth: No. No API key, OAuth, cookie, or other authentication is required.
- HTTPS: Yes. Use the production HTTPS server listed below.
- CORS: Yes. The production endpoints accept cross-origin browser requests from any origin without credentials.
Endpoints 7
Data
- GETList selectable flags
/api/data/flagsReturns the complete public flag list accepted by athlete profile and onboarding flows. - GETList competition divisions
/api/data/divisionsReturns the public division names used to group longevity athletes. - GETList public longevity athlete data
/api/data/athletesReturns the hydrated public athlete snapshot used by the website. Records include profile fields, public biomarker records, crowd age fields, generated asset… - POSTCalculate Pheno Age
/api/data/pheno-ageCalculates a Pheno Age result from chronological age and the nine required blood biomarkers. The result includes Biological Age Difference, which can be… - POSTCalculate Bortz Age
/api/data/bortz-ageCalculates a Bortz Age result from chronological age and the public biomarker panel used by the Pro clock. Monocyte and neutrophil counts are derived from WBC… - POSTPreview a hypothetical Ultimate League rank
/api/data/hypothetical-rankCalculates where a hypothetical biological age result would rank in the current Ultimate League field. Use pheno for an Amateur Pheno Age preview and bortz…
Events
- GETList public competition Events
/api/eventsReturns the complete persisted website-visible Event history as a JSON array, newest OccurredAt first. No authentication, pagination, query filters, or…
API details
- Base URL
https://longevityworldcup.com- Authentication
- None declared in the description
- Operations
- 7 operations on 7 pathsGET 4POST 3
- Main resources
- Data 6Events 1
- Response formats
application/json- Description format
- OpenAPI 3.0.4, API version
v1 - Links
- OpenAPI document · Support
How to test the Longevity World Cup Public API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Longevity World Cup Public API collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “List selectable flags” (GET /api/data/flags), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Longevity World Cup Public API?
Public no-auth JSON endpoints for Longevity World Cup athlete, Event, field, biological aging clock calculation, and rank-preview data. The documented… It is listed under Data & analytics and has 7 endpoints.
Who publishes the Longevity World Cup Public API?
It is listed from Longevity World Cup's public API description (an OpenAPI document), not published by Longevity World Cup on Swastik Codes. Anyone who controls longevityworldcup.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Longevity World Cup Public API?
Requests go to https://longevityworldcup.com. Endpoint paths are added to this base URL.
How do I authenticate with the Longevity World Cup Public API?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the Longevity World Cup Public API have?
7 operations on 7 paths (4 GET, 3 POST). The largest groups are Data, Events.
Is forking the Longevity World Cup Public API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.