The NFL appears to have an API service here: https://api.nfl.com/docs/getting-started/index.html
Accessing the API endpoints requires obtaining an OAuth2 access token. Which, if I am not mistaken, requires a client_id and client_secret.
I have read through the documentation and I am not sure how I would obtain a client_id and client_secret. Is there something I am missing to create these?
Finally got an answer on this. The documentation does say that the API is public and free for everyone, but they changed that policy and haven't updated the documentation.
Hi Dominic,
Thanks for reaching out. As of Feb. 18th, the NFL has secured the APIs and will only grant access to contractual partners. Unfortunately, if you are NOT a NFL Partner you will no longer have access to the feeds or able to obtain access to this feed.
Thanks,
Jonathan Vu
Product Operations Manager
Related
I have created a account with Calendly and want to consume the API's. Here is the link for API's
I have created a token using "Personal Access Token" mechanism provided by Calendly.
If we refer the document, it require some parameter pass to the API like organization, user etc.
I have gone through all the account which I created in Calendly but not able to found these details. Here is the reference where I am expecting it.
Anyone has any idea how can I get this info in Calendly so I can able to call these API's.
Thanks,
Atul
Found the way to get the info.
If you have valid account and valid "Personal Access Token" then you can get the info by calling this API of Calendly.
Refer the screeshot:
This is how you get the details for the user and organization. Then this info you can use to call the API's.
Thanks,
Atul
I am looking into adding Google as an Identity Provider for a Single Signon Solution. The problem is that I would very much like to be informed if the Google user that authenticates has Two Factor Authentication enabled on their account or not.
This is where my googling skills failed me however, as I have found no real mentions of the Two Factor Authentication information being available as part of the authentication Token.
So my question is simply how I can discover if a user who either creates an account via the Google IDP, or simply links their account, has Two Factor Authentication enabled on their Google account?
It seems to be possible to do via the reporting API at a later date, but it would make much better sense for my usecase to somehow get the information in the OIDC token.
Thank you very much for any help you can provide.
Having spent a lot of time on google, i finally managed to find a result, which is another stackoverflow post (No surprise there).
In short, it does not seem to be possible, at least it wasn't in 2017. It was a considered feature but was not implemented. The post is here:
Google OAuth2 API. Check user has two factor authentication (Not GSuite)
I have seen the demo in WWDC18 related video here:
https://developer.apple.com/videos/play/wwdc2018/303/
but it is not from the scratch. I don't see that which tool they have used and where we need to start it. Can anyone help with it?
I watched that video too today and I wanted to use these API features, as for now 19-6-2018 this is still marked as coming soon... based on the App Store Connect website https://developer.apple.com/app-store-connect/
In addition, the new API Keys tab under the main App Store Connect is not available yet.This is the starting point to issue / create the API keys.
I am on look out and waiting...
The App Store Connect API is now available. You can find out more here:
https://developer.apple.com/app-store-connect/api/
The general steps are:
Request access to the API.
Your Team Agent (with the Legal role) will need to do this part.
Create and download an API key.
Anyone with Admin access can do this. Each key you create can only be downloaded once, and should be kept safe.
Use the information on the Keys tab + your private key to generate a token.
You can find libraries for many languages to make this easy here.
Supply the JWT as a bearer token in the HTTP Authorization header when making requests.
For example:
GET https://api.appstoreconnect.apple.com/v1/apps
Authorization: Bearer XYZ123
Where XYZ123 is your JWT. (Your real JWT will be much longer.)
Available API endpoints are documented here:
https://developer.apple.com/documentation/appstoreconnectapi
App Store Connect API available here now.
I just wanted to know if I can use the REST API with an Italian account. I couldn't find any information about.
Thanks.
You can use REST api with an italian account, the link posted by KevinG does not state that you cannot.
I used it last year to implement Expresscheckout and it was working. Be sure to check if you need to be PCI or PCI-DSS compliant.
For more information you care read this faq https://developer.paypal.com/docs/faq/#non-US-dev
You can use REST API from Italy and you have a full access to all features in your sandbox account. In live account you have some limitations (no Direct credit cards processing!).
more info here (login in your developer account first): https://developer.paypal.com/developer/accountStatus
Currently the REST API is not available in Italy. This link will take you the the most current information regarding the REST API and supported countries:
https://developer.paypal.com/docs/integration/direct/rest_api_payment_country_currency_support/#direct-credit-card-payments
I am implementing espn api, but having some issue, most api gives me this response.
{"timestamp" :"2013-02-25T11:19:02Z","message" :"This action is forbidden for the requested resource at your permission level. Please review the documentation for account level access.","status" :"error","code" :403}
I am using this api Espn MLB Standing
I want to know that where to review the documentation, i is there any need to purchase some api or anything else?
[EDIT]
One more thing there is ?apikey=:yourkey , so this key is same for all user or we have to get this according to user login.
I think you are using the wrong apikey or there is some issue in your URL query.
Your app will have a unique apikey. This key is same for all users who are using the app.
You should get a apikey by registering to their site and use it for development purpose.
My rep doesn't allowing commenting, but I thought I'd add the following here:
A small amount of ESPN API data is free, but much requires payment.
You probably don't want to publicly share your personal API key for security reasons.
Go to http://developer.espn.com/io-docs and plug in your API key and use the GUI to generate an API call/response. It's a good way to see a valid, working syntax that you can then drop into your app and edit as necessary.