PipedreamHQ / PipedreamHQ/pipedream
[APP] Live Tennis API
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Name of app / service**
Live Tennis API — https://livetennisapi.com (I'm the vendor)
**Link to developer documentation**
https://docs.livetennisapi.com/reference.html — OpenAPI 3.1 spec at
https://github.com/livetennisapi/openapi
Auth: a single API key, sent as the `x-api-key` header (also accepted as
`Authorization: Bearer `). Free self-serve tier, no card, 1,000 req/day:
https://livetennisapi.com/subscribe/free
**Is lack of support preventing you from moving forward, or do you have a workaround?**
No workaround today — the API is only reachable from Pipedream via a raw HTTP
step, which gives users no props, no dropdowns and no triggers.
**Are there specific actions or triggers you'd like to see for this app?**
Yes — I have them written and tested and will open the PR as soon as the app is
integrated: actions Get Live Matches, Get Match, Get Match Score, Search
Players, Get Upcoming Fixtures; sources New Live Match and New Score Change
(both polling, both deduped).
Contributor guide
Research direction
Start with the Live Tennis API developer documentation and its OpenAPI 3.1 specification to verify authentication and endpoint details. Define the five requested actions and two polling, deduplicated sources, then verify that the integration exposes the listed operations and triggers with the documented API key options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100