I'm starting a brand new project (aka no legacy code) that will interact with github, and there's currently 2 supported APIs, the "rest" API is called "API V3" and the "GraphQL" API is called "API V4",
question is then, does the V4 API deprecate the V3 API? Should I strive to use the V4 API even if I think the V3 API seems easier to use? or should I just pick the API that seems like the best fit regardless of the API version number?
There are two stable versions of the GitHub API: the REST API v3 and the GraphQL API v4.
Looking at the https://developer.github.com/v3/versions/ - it is not. Only V1 and V2 are listed in the "deprecated" section - both are already dead since 2012.
Related
I find tons of articles explaining how to call rest apis from APEX - but I'm accessing salesforce from an integration system using the Salesforce REST API, and want to it the other way around.
ie -
I've found functionality (record merging) - that is not available from the rest API, but IS available from apex. Is there any way to run an apex statement or script from the rest API?
NOTE: I'm aware that the functionality also available from the SOAP api, but we really don't want to go near that for various reasons.
you want to REST API endpoints in APEX, so that you can call this endpoint from anywhere, Right? if so then you need to check this article.
After reading above article, you are able to create GET, POST, DELETE endpoint in your Salesforce Org and you can use this endpoints.
Much has been written about the benefits of the GitHub GraphQL API. And this is a really great technology. The only thing I can't figure out is in what situations is it still better to use the good old REST API v3?
Github GraphQL API is subject to the following caveats:
GraphQL API can only be accessed using authentication. You need a token to use this API. Thus, you can't use GraphQL in an environment where you can't secure the provisioning of this token. For example, in a web app without github authentication. This is a big caveat, especially for people who want to create web app or scripts that target only public repository informations.
Searching commits and code using the search API is not possible in Github Graphql. Only searching repos, issues and users are supported (for the search API)
some features like comparing commits and getting contributors are not possible yet in Graphql. Another example: you can't recursively get a tree using GraphQL API
some mutations already available in v3 may not yet have been implemented in GraphQL (create commit, create tag, create branch etc...), checkout mutations documentation
I need to interact with Github Actions through some code. I found the v3 API for that, but I've been migrating code to use the v4 API instead. I have not been able to find anything related to github actions on v4, unfortunately. Using introspection won't show "artifacts" or "workflows", except for copying the latter on CloneProjectInput, but, perhaps, there's a feature flag I need to use to get them.
Is there any way to interact with Github Actions through their v4 API?
Not yet: the GitHub Actions API announced last January 2020 is:
still in beta
using the V3 API only
Note that there is a difference between:
GitHub REST API v3
GitHub GraphQL API v4
For now, Actions are exposed through REST, not GraphQL
The request has been made of course:
As of now, the GitHub Actions API enables you to manage GitHub Actions only using the REST API.
I'll be sure to pass on your request for v4 support to the team for consideration.
(that was mid-April 2020)
I am using the evaluate REST API from the Academic Knowledge API from Microsoft Cognitive service using the REST endpoint:
https://api.projectoxford.ai/academic/v1.0/evaluate?
In the suscription page at Microsoft Cognitive Service it says:
Important Notice: starting on 1/17, our API endpoints will be changing.
If your API is currently using "api.projectoxford.ai" endpoint, you will need to switch to the new API endpoint (see our API reference for that) or you may experience latency. The old API endpoints will be deprecated 90 days following this change.
I'm trying to find the new REST endpoint and how to use it but I could not figure out. Could you please point me to the documentation?
For most users, the endpoints for Microsoft Cognitive Services are moving to https://westus.api.cognitive.microsoft.com. The rest of the path is unchanged.
Im trying to implement paypal on a website, where I want to give my site-users the ability to add paypal as an payment option for there web shops. So I'm using Laravel, and I found this one, http://jslim.net/blog/2014/09/19/integrate-paypal-sdk-into-laravel-4/ and do pretty much like that.
So my question is, is it possible to combine the Permissions API from the Classic API and using the Rest API for my shop? And then could anyone point me in the right direction?
Currently adding PayPal REST API and Classic API SDKs are causing namespacing conflict issues, as to prevent breaking changes in REST API. The work is under way to release 1.x version of REST APIs that would allow you to work with both rest and classic APIs together.