I know that transactions made via Classic API will not return when using the REST API. But what about vice versa? Can I pull all transactions if using the Classic API?
The REST API uses a different set of IDs for its data model which are not analogous/compatible with the IDs used by the classic APIs.
So at the moment this is not possible.
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.
The last time I worked with Magento 1.x there wasn't a good REST API in place.
Now there looks to be one: http://devdocs.magento.com/swagger/index.html
I would like to integrate the Magento checkout and catalog (from a consumer perspective if you will) completely through the REST API (including the cart, stores etcetera).
Is this possible?
Magento 2 came up with vast features of REST API.So many Default REST API's are provided to manage the all customer activities,customer address management,CMS management
To know more core API
MAGENTO(ROOT FOLDER)/vendor/magento/magento-customer/etc/webapi.xml
Even we can create our own custom REST API to manage any other core activity by loading the model(db table)
PayPal has recently released a new API which should replace the old API. The new API is based on a REST approach.
As fare as I can see there is no option to define a callback URL. In the old API the parameter was 'notify_url'. I use the following documentation:
https://developer.paypal.com/webapps/developer/docs/api/#create-a-payment
Is there a parameter in the new REST API which allows to define a notification URL?
Unfortunately, the REST API is still pretty far behind the classic API's with all of the features they provide. To my knowledge, notify_url/NOTIFYURL simply aren't included in the REST API yet.
That said, if you have IPN configured in your PayPal account profile the REST API calls should still trigger them. It's just that you can't override the value there with a custom one using notify like you're talking about.
The classic API's aren't going away, though. You can still use them just fine.
I'm just wondering if the new PayPal rest API can be used to receive historical data. For example getting a list of sales made before the rest API existed.
I thought there would be some way to hook it up but it seems you can only get sales that were made though the rest API itself.
Am I wrong?
That's correct - only transactions created (via the REST API's) are returned in a GET /payment call today.
You would need to use the classic TransactionSearch API call for any transaction created prior to that.
Can anyone tell me the difference between the REST API and APEX REST.I am new to REST concept.I am very much confused about them.
The REST API (Force.com REST API) is the generic API provided by Salesforce. On the other hand, the Apex REST API is an API written by yourself in apex to provide custom methods.
The Force.com REST API is great for things such as CRUD operations. You should write a custom Apex REST API when you want to perform more complicated actions.
REST -> architectural style for distributed hypermedia systems.
APREX REST -> Apex REST enables you to implement custom Web services in Apex and expose them through the REST architecture.
Second is used to build RESTful web services
Use the REST API most of the time. You can access your records and update them like you'd expect. But if you need to do something special, like update two records, and only have the changes saved if both updates were successful, then look at Apex REST, where you can customize what your API call does as much as you like.
More details in this interview: https://developer.salesforce.com/blogs/tech-pubs/2011/10/salesforce-apis-what-they-are-when-to-use-them.html