To extend a Magento website and implement API access according to the API definition as specified in the attached document: “[url removed, login to view]”.
The purpose of this API is to allow server to server access. The client here is the Innovist server, which will be connecting to the Magento website on behalf of a Magento customer.
Authentication (as described in the document) is done at the ‘login’ API call. Session data is stored in a cookie, and the cookie data will be passed by the client in all subsequent requests.
About Magento APIs:
Based on our brief research of Magento API, we found the following.
Note: The following assessments may not be 100% accurate. More research or prior knowledge of Magento may be needed.
Magento provides 2 methods of API access:
1. API access as an ‘API user’. This user has admin access.
2. API access using OAuth, as a customer.
Neither of these two option would be quite applicable for the API that we’re need to build here.
- Option #1 won’t work because:
a. The Magento API access is assumed to be by a predefined designated API user which will end up having an admin role. The Innovist API requires that access will be allowed on behalf of each individual customer.
b. Access is based on authentication token, which is present on each API call. The Innovist API needs to be based on cookie.
- Aption #2 won’t work because it is based on OAuth, which is very different from the API we need here. In the protocol here, the user never has direct access to the Magento store. With OAuth on the other hand, the user will be redirected to a login screen of Magento.
The packages should work with a standard insnstallation of Magento 1.7 or higher on Linux, for a standard bookstore.
It should be accompanied of documentation describing installation and testing.
40 freelancers are bidding on average $642 for this job
[url removed, login to view] [url removed, login to view] Above are magento complex recent projects ............................................................