I am interested in develop a frontend similar to the WSO2 API Manager's STORE or PUBLISHER applications. The operations I need to implement would be just something like:
show all available proxies services (or published services)
show endpoint of each proxy
What API / libraries should I use in order to do something similar?
Can I build a webapp in php or asp to do that?
many thanks
For the front-end applications of WSO2 API Manager,we have used our inbuilt javascript server-side scripting engine called 'Jaggery'.You can find more info about jaggery from here.
API Manager related back-end functionalities handle through an implemented java API.And its front-end functions handle through javascript/jquery.All the mapping between back-end API Manager related java based functionalities and front-end javascript functionalities handle through this Jaggery scripting engine.
If you view API Publisher/Store source from here, the app directory structure has implemented as a template engine.A blog post related on How to customize the API Publisher/Store front-end apps can be found from here.
Other than that to implement API Publisher/Store front-end html views we have used bootstrap framework as described here.
Thanks;
Related
Recently assigned to a new project where we need to build a api centric web application. Requirement is to build 2 separate projects in Laravel one the has all API's that can be accessed by either web or mobile applications(for future purpose) and other is a web application that uses the API's to work almost all of its function.
Building an API project in Laravel is a easy and lots of tutorials are available about using passport etc. But how do i implement that API to web application.
My major question is how do i setup authentication for web application using api, because its default authentication is model based, or my approach is wrong?
Please suggest ideas, because we are currently in planning phase.
Thanks in advance
Each Laravel Project will be identified as it's own "site" so the only suggestion I would have is if you plan to invoke your APIs via AJAX calls to be wary of Cross-Domain Scripting issues.
I am building an application and currently focusing on the mobile part .
I wanted to use Lumen microframework for the server-side and Apis to connect to the mobile app.
However i also wanted to extend the application later on to build a website (Laravel)
They will both be using the same database .
I am wondering whether i should use Laravel directly and make it responsible for the apis too (albeit it would be slower for mobile apps)
Or i was wondering if i can use a combination of both.
Lumen - to deal with server requests e.g : api.site.com/...
Laravel - to deal with the website e.g : site.com/....
You could do either or, but I would suggest keeping the website and the API isolated.
I actually just finished up a similar project.
I have a mobile app built on Ionic, an API built on Lumen and an admin CMS built on Laravel. The CMS updates content in the API via authenticated API calls and then the app pulls from it.
If you take this route, you could make API calls from the CMS/Website using client side or server side requests. My CMS uses server side calls leveraging Guzzle.
I would suggest looking at sharing models between the two applications such that you don't have to update content via API calls. Here is a nice article on how to do so.
Hi I am building an application based on Magento CE 1.9.2
I have previous experience with magento but not recently or experience using the API, either SOAP or REST.
I am trying to decide whether or not it is fully beneficial or it is recommended to to abstract the client allow a fully fledged e-commerce store using an angular client / magento.
I am trying to see if it efficient to integrate AngularJs within Magento or have an Angular client making calls to the Magento API.
I have found this resource and i am investigating:
https://github.com/Wildhoney/Magento-on-Angular
This seems like an interested libary but before i start i wanted to see what the limitations where for accessing data through either SOAP or REST.
Specially as i am building this application for a client who requires the basic shoping aspects and noting to advanced, is there any data / functionality which magento would not be able to send to the client to utilise?
I wish to have the angular client ( this can be on a PHP based app such as laravel like in Magento-on-angular), i need to be able to get all the products, post reviews and interact with say magento modules, modules which work with say instragram and pull down the review pictures which will be sent to a client, i wish to make a full angular checkout and simply post a checkout object (something alone those lines) to magento for it to parse.
my objective is to have a minimal client which does not lack in functionality and i am very proficient in angular, angular was chosen due to the front end requirements of the application.
Or any other constraints or advice?
Or a Pro's / Con's List.
Thanks
We have a requirement to create an API for IOS , Android and Web App.We have a plan to create the API using PHP and Zend Restful API and the web App using zend MVC.
My Question is
We need to work web app same as like mobile apps. So is it possible to access the REST API from my web MVC in Zend? it is good approach or can i write separate model class for web app?
Help is highly appreciable.
Thanks,
Yes, you can design your web app and your API to consume the same business/services layer. You need separate the services layer well enough and treat your web app controllers and API controllers as consumers of the services layer.
Also please read about Zend's Apigility which will help you do the same with lesser efforts.
I have an application which handles some data. Now i want to make the data available throughout a php api (something like zend_gdata for google) so my application's users can handle the data from my application in their own applications on an other host.
Is this possible? Can someone hook me up whith some literature or ideas?
This has been written about on numerous occasions. Here is some reading material:
Creating a REST API with PHP
How to Add an API to your Web Service