You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
In reviewing the StubHub API, it appears to be rather robust and provides a couple of features that we do not have right now within our tool, namely:
Ability to verify a barcode is valid via multiple sources
Verification of seat location information
A marketplace to sell tickets that have not yet been requested in the group
Possible fallback data source for event updates when XML Team malfunctions
I am predicting this could be a rather involved process and may prompt us to consider alternative approaches. My thoughts are on a few possible phases of this:
Phase 1 - Connect to your StubHub account within SeatShare to show your current listings
Estimated time: 12 hours
Optional feature for users that also have StubHub accounts
Gets us baseline connectivity via an OAuth endpoint and storage of relevant per-user credentials
Value add for those user to remind them which tickets they put on StubHub while looking at their listings
Should just show as a sidebar item on all group index pages as a table of current listings; wouldn't be attached to SeatShare data
Phase 2 - Connect the event/ticket ID in SeatShare to the event/ticket ID in StubHub
Estimated Time: 30 hours
Tickets that are also listed on StubHub can retrieve the ticket status (sold, pricing, etc.)
Alerts other users that the ticket is available, but also listed elsewhere
Updates the ticket status in SeatShare when sold automatically
Phase 3 - Create a listing for a ticket on StubHub
Estimated Time: 10 hours
Quick access to use the attached PDF or provided Barcode to create a listing on StubHub with fixed/market price
Monitors ticket status and updates SeatShare with data
There are some risks:
Negative brand association with StubHub if we approach teams later on (they like their own marketplaces that lack APIs), so we may not want to promote it or make available for all teams
Possible costs for increased API usage quotas (10 requests / minute is their "bronze" level, which is really, really slow).
Users may not want the interface cluttered with third-party UI elements if they do not intend to use them
And possible rewards:
Affiliate program may come into play for signing up new users, etc.
May be able to partner with StubHub's API group for beta access to new features
The text was updated successfully, but these errors were encountered:
In reviewing the StubHub API, it appears to be rather robust and provides a couple of features that we do not have right now within our tool, namely:
I am predicting this could be a rather involved process and may prompt us to consider alternative approaches. My thoughts are on a few possible phases of this:
Phase 1 - Connect to your StubHub account within SeatShare to show your current listings
Phase 2 - Connect the event/ticket ID in SeatShare to the event/ticket ID in StubHub
Phase 3 - Create a listing for a ticket on StubHub
There are some risks:
And possible rewards:
The text was updated successfully, but these errors were encountered: