If you already have a key for v1, you will need to sign into your account to request a new key. The key request, if for Basic, will be authorized immediately.
Hi Benn,
The new API seems a lot cleaner - but there are a few things that I liked better about the old one that maybe is possible to include in this one.
Previously, there was much more information available in a single API request, whereas now many more requests are required for the same information.
For example, when requesting all the events for a certain league, previously I was able to see the status of each game and the score. Now to see the scores, it seems I have to go and request it for each event individually. Same goes for teams. When requesting all the teams for a league/conference/division, it would be nice to also get their short name, logo, wins/losses, and location instead of having to request the data for each team individually.
I don't know which way to go o this one. Although it was true that you would get more data in one single call in V1, I do prefer consistency on the API. I know that teams would basically give me a reference, and if I want to get more info then query that team. and that seems to be the case all through the API. But again, I am sure that in a couple of weeks I will be saying the same thing you are, :)
We've set up this new release according to REST standards. We understand that users are going to have to familiarize with the new format but the architecture will allow us to more effectively build out and expand the API.
We realize the number of calls needed will increase across all use cases. Several users have given us feedback about the rate limits for the Basic plan.
We are carefully analyzing the data during the next couple of weeks of this 'soft launch' and will adjust the rates accordingly following our review in a way that balances developer needs and our business requirements.
Yeah, just some feedback on the number of calls we need to do now in order to retrieve required information.
I liked the amount of information in the previous API's because I was able to display all the information I needed in one call. To retrieve the same data for the NEW API, I could potentially run out of calls with one sport very quickly (and I have with the basic plan, I never did with the old API basic plan). I am having second thoughts about whether fanfeeder is the api to use. I'm giving this NEW API a shot, but am still evaluating it as a viable solution.
I do like the new feed with the use of uuid's, this is exactly what I need and makes it easy to identify the information I'm going after. I was reading the legal jargon and had some questions I would like answered but are not appropriate for the forum. Is there any way to chat with someone about our specific needs that don't fit with your legal restrictions?
As I've been stating on the threads, we've set up a truly RESTful API and are planning to keep this architecture going forward. What we will be evaluating after we complete our data infrastructure modifications over the next few days is the appropriate rate limits for Basic and other tiers. We're trying to gather as much data as possible from users on use cases to strike the appropriate balance here.
I'll reach out to you via email regarding the other issues you reference.
Let us know what you think of the new version of our API. Feedback - positive or negative? Want to see new features? Tell us here.
Message edited by Benn 9 months ago
Sphere – 9 months ago
How long will an API key request take?
For V1, I had it in two days. I guess because of the Beta I'm still waiting?
Benn – 9 months ago
If you already have a key for v1, you will need to sign into your account to request a new key. The key request, if for Basic, will be authorized immediately.
Sphere – 9 months ago
I got your e-mail, thanks!
I did a new request, but it's been pending for 3 days now, hence my question.
swhopkins – 9 months ago
Hi Benn,
The new API seems a lot cleaner - but there are a few things that I liked better about the old one that maybe is possible to include in this one.
Previously, there was much more information available in a single API request, whereas now many more requests are required for the same information.
For example, when requesting all the events for a certain league, previously I was able to see the status of each game and the score. Now to see the scores, it seems I have to go and request it for each event individually. Same goes for teams. When requesting all the teams for a league/conference/division, it would be nice to also get their short name, logo, wins/losses, and location instead of having to request the data for each team individually.
Thanks,
Stephen
jorge – 9 months ago
I don't know which way to go o this one. Although it was true that you would get more data in one single call in V1, I do prefer consistency on the API. I know that teams would basically give me a reference, and if I want to get more info then query that team. and that seems to be the case all through the API. But again, I am sure that in a couple of weeks I will be saying the same thing you are, :)
Benn – 9 months ago
We've set up this new release according to REST standards. We understand that users are going to have to familiarize with the new format but the architecture will allow us to more effectively build out and expand the API.
We realize the number of calls needed will increase across all use cases. Several users have given us feedback about the rate limits for the Basic plan.
We are carefully analyzing the data during the next couple of weeks of this 'soft launch' and will adjust the rates accordingly following our review in a way that balances developer needs and our business requirements.
tracedog – 9 months ago
Benn,
Yeah, just some feedback on the number of calls we need to do now in order to retrieve required information.
I liked the amount of information in the previous API's because I was able to display all the information I needed in one call. To retrieve the same data for the NEW API, I could potentially run out of calls with one sport very quickly (and I have with the basic plan, I never did with the old API basic plan). I am having second thoughts about whether fanfeeder is the api to use. I'm giving this NEW API a shot, but am still evaluating it as a viable solution.
I do like the new feed with the use of uuid's, this is exactly what I need and makes it easy to identify the information I'm going after. I was reading the legal jargon and had some questions I would like answered but are not appropriate for the forum. Is there any way to chat with someone about our specific needs that don't fit with your legal restrictions?
Cheers!
Trace
Cheers!
Benn – 9 months ago
Trace,
Thanks for the feedback.
As I've been stating on the threads, we've set up a truly RESTful API and are planning to keep this architecture going forward. What we will be evaluating after we complete our data infrastructure modifications over the next few days is the appropriate rate limits for Basic and other tiers. We're trying to gather as much data as possible from users on use cases to strike the appropriate balance here.
I'll reach out to you via email regarding the other issues you reference.
Benn