To this short-list, I will add 2 more resources.<\/p>\n
There is one article written by AndroidHive. The logic that prevailed for this POC is nice, nevertheless I consider it too development oriented, not enough user friendly for a dummy developer like me.<\/p>\n
- \n
- AndroidHive – How to create REST API for Android app using PHP, Slim and MySQL \u2013 Day 2\/2
http:\/\/www.androidhive.info\/2014\/01\/how-to-create-rest-api-for-android-app-using-php-slim-and-mysql-day-23\/<\/a><\/li>\n<\/ul>\nMy purpose was to rapidly build up an POC of an API with the help of MySQL. “No flesh and blood, not fat”, just pure representation that can be reused as much as I want on any subject.
\nIf I want to make an API on street art, on wines or on managing translations in 14 languages, that what I wanted.<\/p>\nSo, I have avoided authentication issue. Too big for me, I am too lazy.<\/p>\n
For the wines, it has been already made but unfortunately, the project did not work anymore when I have migrate it from PC to MAC. So I found it better to start with a fresh code \ud83d\ude42 but is was inspiring.<\/p>\n
- \n
- RESTful services with jQuery, PHP and the Slim Framework
http:\/\/coenraets.org\/blog\/2011\/12\/restful-services-with-jquery-php-and-the-slim-framework\/<\/a><\/li>\n<\/ul>\nEnough reading, let’s start to give my own “rudimentary” version of an API.<\/p>\n
A. The “rudimentary” API, the code explained<\/h4>\n
You can find out the code @bflaven on https:\/\/github.com\/bflaven\/BlogArticlesExamples\/tree\/master\/poc_api_slim<\/a><\/b><\/p>\n
1. REQUIRE – The “rudimentary” API<\/b>
\nFor sure, you need the framework and declare the instance of the app.<\/p>\n\r\n\r\n\/**\r\n * ----------- REQUIRE\r\n---------------------------------\r\n *\/\r\n\r\nrequire 'Slim\/Slim.php';\r\nuse Slim\\Slim;\r\nSlim::registerAutoloader();\r\n$app = new Slim();\r\n\r\n<\/pre>\n
The .htaccess has to put in the directory of the API eg \/Applications\/MAMP\/htdocs\/api-for-mobile\/api-v3\/<\/b><\/p>\n
\r\nRewriteEngine On\r\nRewriteCond %{REQUEST_FILENAME} !-f\r\nRewriteRule ^ index.php [QSA,L]\r\n<\/pre>\n2. MESSAGES – The “rudimentary” API<\/b>
\nVery cheesy way to pretend you have build up a true API without handling the HTTP status codes properly and instead using a \u201carchaic\u201d error messages system. I have made this heresy in plain consciousness because I like to get answer in browser and not only in postman.<\/p>\n\r\n\/**\r\n * ----------- MESSAGES\r\n---------------------------------\r\n *\/\r\ndefine ('_MESSAGE_ERROR_NO_RECORD_FOUND_','{\"error\": {\"text\": \"no record found\"}}');\r\ndefine ('_MESSAGE_ERROR_DELETE_','{\"error\": {\"success\": \"delete succeeded\"}}');\r\ndefine ('_MESSAGE_ADD_RECORD_SUCCEEDED_', '{\"success\": {\"success\": \"record successfully added\"}}');\r\ndefine ('_MESSAGE_UPDATE_RECORD_SUCCEEDED_', '{\"success\": {\"success\": \"record successfully updated\"}}');\r\n<\/pre>\n3. ROUTES – The “rudimentary” API<\/b>
\n2 good practices when you write routes<\/b><\/p>\n- \n
- Centralize the routes of your API and use functions. Functions are always much more self explanatory than a poor routes list.<\/li>\n
- Use comment as often as you can because from day to day, you will forget the meaning of your function. Be simple and straightforward in your comment and always have in mind that your code may be read by someone else.<\/li>\n<\/ol>\n
\r\n\/**\r\n * ----------- ROUTES\r\n---------------------------------\r\n *\/\r\n\/* homepage *\/\r\n$app->get('\/', 'getIntroHelp');\r\n\r\n\/* All the get operation *\/\r\n$app->get('\/strings', 'getStrings');\r\n$app->get('\/strings\/:id', 'getStringDetails');\r\n$app->get('\/strings\/search\/:query', 'findByStringName');\r\n\/* Add a string *\/\r\n$app->post('\/strings', 'addString');\r\n\/* Update a string *\/\r\n$app->put('\/strings\/:id', 'updateString');\r\n\/* Delete a string *\/\r\n$app->delete('\/strings\/:id', 'deleteString');\r\n\r\n\/* required *\/\r\n$app->run();\r\n<\/pre>\n4. FUNCTIONS – The “rudimentary” API<\/b>
\nHere is the list of the functions. I know it may be stupid, but I like having a welcome page. 2 reasons to this : <\/p>\n- \n
- To have the sensation that the API is truly up and running<\/li>\n
- To leverage on this page to help users to manipulate your API right away for the very first operations…<\/li>\n<\/ol>\n
\r\n \/**\r\n * ----------- FUNCTIONS\r\n---------------------------------\r\n *\/\r\n\/**\r\n * Welcome\r\n * url - \/\r\n * method - GET\r\n * description - the main documentation\r\n *\/\r\nfunction getIntroHelp() { \r\n $intro = '{\r\n \"name\": \"POC API\",\r\n \"description\": \"WELCOME ON SLIM FAST API V1\",\r\n \"interactions\": {\r\n \"listing_strings\": {\r\n \"url\": \"\/strings\", \r\n \"method\": \"GET\",\r\n \"parameters\": \"n\/a\",\r\n \"required\": [\"n\/a\"],\r\n \"description\": \"Listing of the strings\"\r\n },\r\n \"details_string\": {\r\n \"url\": \"\/strings\", \r\n \"method\": \"GET\",\r\n \"parameters\": \"id\",\r\n \"required\": [\"id\"],\r\n \"description\": \"Get the details of a string\"\r\n },\r\n \"add_string\": {\r\n \"url\": \"\/strings\", \r\n \"method\": \"POST\",\r\n \"parameters\": \"brand, source, language, cat, string_name, string_name_model, string_name_value\",\r\n \"required\": [\"brand\", \"source\", \"language\", \"cat\", \"string_name\", \"string_name_model\", \"string_name_value\"],\r\n \"description\": \"Add a new string\"\r\n },\r\n \"update_string\": {\r\n \"url\": \"\/strings\", \r\n \"method\": \"PUT\",\r\n \"parameters\": \"id\",\r\n \"required\": [\"id\"],\r\n \"description\": \"Update an existing string\"\r\n },\r\n \"delete_string\": {\r\n \"url\": \"\/strings\/:id\", \r\n \"method\": \"DELETE\",\r\n \"parameters\": \"id\",\r\n \"required\": [\"id\"],\r\n \"description\": \"To delete a string in the database\"\r\n },\r\n \"search_string\": {\r\n \"url\": \"\/strings\/search\/:query\", \r\n \"method\": \"GET\",\r\n \"parameters\": \"query\",\r\n \"required\": [\"query\"],\r\n \"description\": \"To search a string in the database on string_name with UPPER(RTRIM(string_name)) eg twitter_\"\r\n }\r\n }\r\n}';\r\n echo ($intro);\r\n}\r\n<\/pre>\n5. extra informations about The “rudimentary” API – Test for emptiness<\/b>
\nI know it is quick and very dirty but who care? It is part of the “cheesy smoke screen conspiracy” to pretend that you have made a true API even to your own eyes. <\/p>\nIf there is no result, please tell me what I did wrong<\/b><\/p>\n
\r\n\r\n\t\/* emptiness *\/\r\n if(!$string) {\r\n echo (''._ERROR_MESSAGE_UPDATE_FAILED_.''); \r\n } else {\r\n echo json_encode($string); \r\n }\r\n \/* emptiness *\/\r\n<\/pre>\nB. The “rudimentary” API – send content to this API<\/h4>\n
Most of the time, you can spend hours to find out how to send content to your brand new API and many of the articles that I have read supposed you are mastering Postman and if it is not the case, you will be forced to make time-consuming iterations to populate data in your API.<\/p>\n
That is reason I have given the Postman collection of basic queries.<\/b><\/p>\n
See all the queries in my-api-from-me-see-api-v3.postman_collection.json<\/b><\/p>\n
Create a string<\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_4.jpg\")
<\/p>\nUpdate a string<\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_6.jpg\")
<\/p>\nDelete a string<\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_7.jpg\")
<\/p>\nSearch for the query string
twitter_<\/code><\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_8.jpg\")
<\/p>\nFew screens of the output in JSON<\/h4>\n
The welcome page @
\/<\/code><\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_1.jpg\")
<\/p>\nListing of the strings (getStrings) @
\/strings<\/code><\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_2.jpg\")
<\/p>\nListing of the details of one string (getStringDetails) @
\/strings<\/code><\/b>
\n![\"Proof](\"https:\/\/flaven.fr\/wp-content\/uploads\/2017\/05\/poc_api_slim_3.jpg\")
<\/p>\nEn savoir plus<\/h2>\n
- \n
- Creating A Simple REST API With Slim Framework
https:\/\/www.cloudways.com\/blog\/simple-rest-api-with-slim-micro-framework\/<\/a><\/li>\n- How to Create a Simple REST API With Slim Framework
http:\/\/phpflow.com\/php\/create-simple-rest-api-using-slim-framework\/<\/a><\/li>\n- Getting Started with Slim Framework – Creating a RESTful API
http:\/\/codoki.com\/2015\/01\/27\/getting-started-with-slim-framework\/
\n<\/a><\/li>\n- Create REST applications with the Slim micro-framework
https:\/\/www.ibm.com\/developerworks\/library\/x-slim-rest\/<\/a><\/li>\n- How to Create a Simple REST API With Slim Framework
http:\/\/phpflow.com\/php\/create-simple-rest-api-using-slim-framework\/<\/a><\/li>\n- AndroidHive – Android Task Manager App REST Api Testing
https:\/\/www.youtube.com\/watch?v=CJcf-Zn9oRI<\/a><\/li>\n- Creating a RESTful API using Slim php framework
https:\/\/spinspire.com\/article\/creating-restful-api-using-slim-php-framework<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"I have looked for many resources throughout the web to find out a small and easy piece of PHP to create a POC for an… <\/p>\n
- How to Create a Simple REST API With Slim Framework
- Creating A Simple REST API With Slim Framework
- RESTful services with jQuery, PHP and the Slim Framework