cAPI - Core

Version 1.3.4.3 Stable

Released on: Monday, 04 December 2017 19:00

 

Maturity
Stable
Released on
Monday, 04 December 2017 19:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

cAPI v1.3.4.3 is a bug-fix release.

  • Increment to version 1.3.4.3. Change joomlaID to j38
  • Resolved errors caused by undeclared, nested class objects.
  • Change minimum permission for GET component/model and GET component/list/all to core.login.admin
  • TODO: Improve access control check compatibility with various security modes for core and 3rd party extensions.


cAPI v1.3.4.2 was a bug-fix release.

  • Update version to 1.3.4.2
  • Require "Super User" (core.admin) privileges to access complete components list.
  • Create method GET /component/model to allow retrieving Model class information only. Helps with introspecting third-party Models which may not have known/standard Model methods.
  • Include modelMethod and modelMethodArguments (json) request parameters to GET /component/model/data to accommodate different Model class getters.
  • For GET /component/model/data, use call_user_func_array to call designated $modelMethod on $instance object with any number of arguments passed as JSON encoded array $modelMethodArguments.
  • Include HTML error codes for invalid requests.

cAPI v1.3.4.1 was a bug-fix release.

  • Remove unnecessary path debug in GET component/list/all response.
  • Update URL for "Find out more about cAPI" link.
  • Change $extension->name to $extension->element
  • Update to version 1.3.4.1

This release also includes the following:

  • Improve error trapping for GET component/model/data
  • Validate getInstance for getComponentModelData
  • Validate JTable::getInstance input for getComponentTableDataById
  • Build advanced filtering for getComponentModelData
  • Implement Joomla ACL per component and individual asset item.
  • New method getComponentModelData
  • Complete development on getComponentTableDataById.Include get_class_methods boolean check in URLparameter to allow class methods and associated parameters to be included in the response (requires core.edit for related component).
  • Update getComponentTableData to getComponentTableDataById.Method will return table data for single ID request.
  • Create method getComponentTableData
  • New method getComponentTableFields for returning component fields.
  • Initial work completed on getComponentListAll. Returns list of all components, along with table and model classes for "site" and "administrator" contexts.
  • Include Basic Authentication SecurityScheme definition.
  • Methods to allow Basic Authentication through Authorization header or force HTTP Apache Auth via URL variable basic_auth=true.
  • Create new class ServicesJoomlaHelpersComponent().
  • Increment to version 1.3.4.

Previous release:

  • Remove extraneous tag_link_class parameter
  • Increment cAPI version to 1.3.3
  • Resolve bug with successful updating of dlid in update_sites table, extra_query field when editing the Download ID parameter in com_services component options.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.4.2 Stable

Released on: Wednesday, 29 November 2017 19:00

 

Maturity
Stable
Released on
Wednesday, 29 November 2017 19:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

cAPI v1.3.4.2 is a bug-fix release.

  • Update version to 1.3.4.2
  • Require "Super User" (core.admin) privileges to access complete components list.
  • Create method GET /component/model to allow retrieving Model class information only. Helps with introspecting third-party Models which may not have known/standard Model methods.
  • Include modelMethod and modelMethodArguments (json) request parameters to GET /component/model/data to accommodate different Model class getters.
  • For GET /component/model/data, use call_user_func_array to call designated $modelMethod on $instance object with any number of arguments passed as JSON encoded array $modelMethodArguments.
  • Include HTML error codes for invalid requests.

cAPI v1.3.4.1 is a bug-fix release.

  • Remove unnecessary path debug in GET component/list/all response.
  • Update URL for "Find out more about cAPI" link.
  • Change $extension->name to $extension->element
  • Update to version 1.3.4.1

This release also includes the following:

  • Improve error trapping for GET component/model/data
  • Validate getInstance for getComponentModelData
  • Validate JTable::getInstance input for getComponentTableDataById
  • Build advanced filtering for getComponentModelData
  • Implement Joomla ACL per component and individual asset item.
  • New method getComponentModelData
  • Complete development on getComponentTableDataById.Include get_class_methods boolean check in URLparameter to allow class methods and associated parameters to be included in the response (requires core.edit for related component).
  • Update getComponentTableData to getComponentTableDataById.Method will return table data for single ID request.
  • Create method getComponentTableData
  • New method getComponentTableFields for returning component fields.
  • Initial work completed on getComponentListAll. Returns list of all components, along with table and model classes for "site" and "administrator" contexts.
  • Include Basic Authentication SecurityScheme definition.
  • Methods to allow Basic Authentication through Authorization header or force HTTP Apache Auth via URL variable basic_auth=true.
  • Create new class ServicesJoomlaHelpersComponent().
  • Increment to version 1.3.4.

Previous release:

  • Remove extraneous tag_link_class parameter
  • Increment cAPI version to 1.3.3
  • Resolve bug with successful updating of dlid in update_sites table, extra_query field when editing the Download ID parameter in com_services component options.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.4.1 Stable

Released on: Sunday, 26 November 2017 19:00

 

Maturity
Stable
Released on
Sunday, 26 November 2017 19:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

cAPI v1.3.4.1 is a bug-fix release.

  • Remove unnecessary path debug in GET component/list/all response.
  • Update URL for "Find out more about cAPI" link.
  • Change $extension->name to $extension->element
  • Update to version 1.3.4.1

This release also includes the following:

  • Improve error trapping for GET component/model/data
  • Validate getInstance for getComponentModelData
  • Validate JTable::getInstance input for getComponentTableDataById
  • Build advanced filtering for getComponentModelData
  • Implement Joomla ACL per component and individual asset item.
  • New method getComponentModelData
  • Complete development on getComponentTableDataById.Include get_class_methods boolean check in URLparameter to allow class methods and associated parameters to be included in the response (requires core.edit for related component).
  • Update getComponentTableData to getComponentTableDataById.Method will return table data for single ID request.
  • Create method getComponentTableData
  • New method getComponentTableFields for returning component fields.
  • Initial work completed on getComponentListAll. Returns list of all components, along with table and model classes for "site" and "administrator" contexts.
  • Include Basic Authentication SecurityScheme definition.
  • Methods to allow Basic Authentication through Authorization header or force HTTP Apache Auth via URL variable basic_auth=true.
  • Create new class ServicesJoomlaHelpersComponent().
  • Increment to version 1.3.4.

Previous release:

  • Remove extraneous tag_link_class parameter
  • Increment cAPI version to 1.3.3
  • Resolve bug with successful updating of dlid in update_sites table, extra_query field when editing the Download ID parameter in com_services component options.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.4 Stable

Released on: Wednesday, 15 November 2017 19:00

 

Maturity
Stable
Released on
Wednesday, 15 November 2017 19:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

cAPI v1.3.4 introduces basic HTTP authentication via Authorization header and a collection of methods allowing API access to Component Model & Table data.

This release includes the following:

  • Improve error trapping for GET component/model/data
  • Validate getInstance for getComponentModelData
  • Validate JTable::getInstance input for getComponentTableDataById
  • Build advanced filtering for getComponentModelData
  • Implement Joomla ACL per component and individual asset item.
  • New method getComponentModelData
  • Complete development on getComponentTableDataById.Include get_class_methods boolean check in URLparameter to allow class methods and associated parameters to be included in the response (requires core.edit for related component).
  • Update getComponentTableData to getComponentTableDataById.Method will return table data for single ID request.
  • Create method getComponentTableData
  • New method getComponentTableFields for returning component fields.
  • Initial work completed on getComponentListAll. Returns list of all components, along with table and model classes for "site" and "administrator" contexts.
  • Include Basic Authentication SecurityScheme definition.
  • Methods to allow Basic Authentication through Authorization header or force HTTP Apache Auth via URL variable basic_auth=true.
  • Create new class ServicesJoomlaHelpersComponent().
  • Increment to version 1.3.4.

Previous release:

  • Remove extraneous tag_link_class parameter
  • Increment cAPI version to 1.3.3
  • Resolve bug with successful updating of dlid in update_sites table, extra_query field when editing the Download ID parameter in com_services component options.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.3 Stable

Released on: Tuesday, 08 August 2017 20:00

 

Maturity
Stable
Released on
Tuesday, 08 August 2017 20:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

cAPI v1.3.3 includes a bug fix for the Download ID component parameter and how it populates extra_query field in the update_sites table. It's likely that the previous couple releases may not automatically update via the Joomla Updater (even with your Download ID configured). If that is the case, you should download and install cAPI Core v1.3.3, manually.

This release includes the following:

  • Remove extraneous tag_link_class parameter
  • Increment cAPI version to 1.3.3
  • Resolve bug with successful updating of dlid in update_sites table, extra_query field when editing the Download ID parameter in com_services component options.

Previous release:

  • Remove updateserver for services/slimjsonapiview plugin.Remove updateserver for services/slimjsonapiview plugin.
  • Remove updateserver for services/slimjsonapimiddleware plugin
  • Remove updateserver for services/slim
  • Remove updateserver for services/rest plugin.
  • Remove updateserver for services/joomla
  • Remove updateserver for lib_services.
  • Remove updateserver for com_services.
  • Build component options fields and logic to control view-access to Swagger UI routes for each services plugin.
  • Update Swagger definition description for cAPI.
  • Bug fixes to authentication for getUserDetailByTypeValue.
  • Allow Super Users (or where user's session matches requested user detail) to access getUserDetailByTypeValue
  • Return responses for getUserDetailByTypeValue as object instead of as sub-elements of array[0].
  • Require Super User permissions for getUserDetailByTypeValue.
  • Update Joomla minimum version to 3.6.
  • Update cAPI Core Package manifest file to include new include libraries and provide link to learn.getcapi.org.
  • Add additional services folders to lib_services.xml manifest.
  • Fix 500 error getCategoryListByIdCategories when searching category id which does not exist.
  • Update zircote/swagger-php 2.0.10
  • Update doctrine/annotations library
  • Add symfony/finder libraries
  • Fix typo in guzzlehttp vendor library folder name.
  • Updated lib_services.xml manifest to include new ReactPHP libraries.
  • Update Composer library files to include ReactPHP libraries.
  • Add libraries and associated dependencies for ReactPHP
  • Update zircote/swagger-php to v2.0.10
  • Upgrade Slim Framework to v2.6.3
  • Commit remaining unversioned files added to /libararies/services/
  • Include web.config in /libraries/services/
  • Commit updated symfony vendor library in /libraries/services/symfony to match J37.x
  • Included updated psr vendor library in /libraries/services/psr
  • Include updated Joomla vendor library in /libraries/services/joomla to match compatibility with Joomla 3.7.x
  • Increment Joomla ID to j37

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.2 Stable

Released on: Friday, 21 July 2017 20:00

 

Maturity
Stable
Released on
Friday, 21 July 2017 20:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

cAPI v1.3.2 is one of the biggest releases to date, ecompassing not only bug fixes and feature improvements, but also including every component from the fantastic ReactPHP library. This lays the foundation for new functionality including asynchronous event handling, non-blocking I/O operations, high-speed messaging queuing and much more!

This release includes the following:

  • Remove updateserver for services/slimjsonapiview plugin.Remove updateserver for services/slimjsonapiview plugin.
  • Remove updateserver for services/slimjsonapimiddleware plugin
  • Remove updateserver for services/slim
  • Remove updateserver for services/rest plugin.
  • Remove updateserver for services/joomla
  • Remove updateserver for lib_services.
  • Remove updateserver for com_services.
  • Build component options fields and logic to control view-access to Swagger UI routes for each services plugin.
  • Update Swagger definition description for cAPI.
  • Bug fixes to authentication for getUserDetailByTypeValue.
  • Allow Super Users (or where user's session matches requested user detail) to access getUserDetailByTypeValue
  • Return responses for getUserDetailByTypeValue as object instead of as sub-elements of array[0].
  • Require Super User permissions for getUserDetailByTypeValue.
  • Update Joomla minimum version to 3.6.
  • Update cAPI Core Package manifest file to include new include libraries and provide link to learn.getcapi.org.
  • Add additional services folders to lib_services.xml manifest.
  • Fix 500 error getCategoryListByIdCategories when searching category id which does not exist.
  • Update zircote/swagger-php 2.0.10
  • Update doctrine/annotations library
  • Add symfony/finder libraries
  • Fix typo in guzzlehttp vendor library folder name.
  • Updated lib_services.xml manifest to include new ReactPHP libraries.
  • Update Composer library files to include ReactPHP libraries.
  • Add libraries and associated dependencies for ReactPHP
  • Update zircote/swagger-php to v2.0.10
  • Upgrade Slim Framework to v2.6.3
  • Commit remaining unversioned files added to /libararies/services/
  • Include web.config in /libraries/services/
  • Commit updated symfony vendor library in /libraries/services/symfony to match J37.x
  • Included updated psr vendor library in /libraries/services/psr
  • Include updated Joomla vendor library in /libraries/services/joomla to match compatibility with Joomla 3.7.x
  • Increment Joomla ID to j37

Previous release:

  • Swagger documentation fixes for Tag service routes.
  • BUG FIX - Resolved issue with REST API limitation for token access not working properly since version 1.2.8.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.1 Stable

Released on: Thursday, 11 May 2017 20:00

 

Maturity
Stable
Released on
Thursday, 11 May 2017 20:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

The release of cAPI v1.3.1 includes the following:

  • Swagger documentation fixes for Tag service routes.
  • BUG FIX - Resolved issue with REST API limitation for token access not working properly since version 1.2.8.

Previous release:

cAPI v1.3.0 is now fully compatible with Joomla 3.7!

  • Increment to v1.3.0. This is done to accommodate major changes to class autoloading from services plugins helpers. Also includes a minor response scheme change to GET /user route.
  • Refactor to register JLoader prefix "Services" to faciliate autoloading of helper classes in services plugins.
  • Correction to doc block summary for getTagFields.
  • Remove outside array dimension [0] from user getUser response.
  • Remove $application->getInstance();
  • Change to JUri()->isSSL() for SSL check in swaggerui administrative view.
  • Update class name instantiation to ServicesRestHelpersTokenmanage.
  • Cross domain access is now fully handled in code.
  • BUG: Update GET /token/:token to prevent auth failure when logging in with account matching existing session.
  • Updating to resolve compatibility issues with J3.7.
  • Update documentation for getTokenByToken.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.3.0 Stable

Released on: Thursday, 27 April 2017 20:00

 

Maturity
Stable
Released on
Thursday, 27 April 2017 20:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

The release of cAPI v1.3.0 includes changes to class autoloading from services plugins helpers. Also includes a minor response scheme change to GET /user route.. The next version of cAPI will handle tag assignment to com_content items.

cAPI v1.3.0 is now fully compatible with Joomla 3.7!

  • Increment to v1.3.0. This is done to accommodate major changes to class autoloading from services plugins helpers. Also includes a minor response scheme change to GET /user route.
  • Refactor to register JLoader prefix "Services" to faciliate autoloading of helper classes in services plugins.
  • Correction to doc block summary for getTagFields.
  • Remove outside array dimension [0] from user getUser response.
  • Remove $application->getInstance();
  • Change to JUri()->isSSL() for SSL check in swaggerui administrative view.
  • Update class name instantiation to ServicesRestHelpersTokenmanage.
  • Cross domain access is now fully handled in code.
  • BUG: Update GET /token/:token to prevent auth failure when logging in with account matching existing session.
  • Updating to resolve compatibility issues with J3.7.
  • Update documentation for getTokenByToken.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Version 1.2.8 Stable

Released on: Thursday, 13 April 2017 20:00

 

Maturity
Stable
Released on
Thursday, 13 April 2017 20:00

What is cAPI?

Code named "Constant API", cAPI is the fantastic result of an effort to mesh the Slim micro-framework with the Joomla Framework / CMS. Once that goal was accomplished, it soon became obvious that just built a Joomla RESTful API was only the beginning! By leveraging Joomla's advanced "pluggable" architecture and robust ACL, cAPI can transform your website into a true middleware service for anything ranging from SQL servers, MongoDB servers and even Microsoft's Active Directory (think of the SSO possibilities!).

How does it work?

cAPI injects the Slim micro-framework into the Joomla application instance, allowing for service route plugins to be built at any level of the event stack. But that's only the beginning!

A Services Control Panel manages the creation of access tokens, Slim framework parameters and API rate limitation rules. This allows an administrator to create tokens mapped to specific Joomla users who in turn are assigned unique group permissions using Joomla ACL.

The service routes are built into Joomla plugins which can be enabled / disabled or assigned access permissions individually. This opens the door for development of feature expansions to the core cAPI services to expose 3rd party Joomla extensions, database querying or even remote LDAP as RESTful JSON APIs.

The release of cAPI v1.2.8 includes new Joomal Tag methods to allow create / read / update / delete and tag search. The next version of cAPI will handle tag assignment to com_content items.

A new menu item view has been added to com_services to allow site admins to create Swagger UI interfaces for any Swagger JSON definition URLs. 

Commit Message  
47818e5ed11 Remove unnecessary language item definition.
f25e6b2d67d Remove unnecessary array definition.
1d09ae78e87 Remove slim_php_framework view and related files and language parameters as they are no longer needed.
956a56313ae Symmetrically encrypt swaggerjson path parameter as "cryptoKey" key value store in user session.
a726cd3562a Create service route getSlimSwaggerRemoteByUrl.Update com_services to use this route for the view swaggeruimisc.
982c4c98801 Commit previously unversioned files.
2c50d5da210 Menu item parameter configuration for swaggeruimisc view for com_services
c51921d1eaa Create swaggeruimisc view for com_services to allow for front-end presentation of any pre-configured Swagger JSON definition file.
416cea8ca97 Resolve issues with proper handling of CORS preflight requests.
745e2515fb8 Fix bug with proper setting of Access-Control-Allow-Origin with respect to CORS.
9a91f513903 Update token handling for parameter and header value to ensure acceptance.
adc6a78fb64 Created PUT /tag and DELETE /tag methods.Working on Swagger docs.
75233fa07ad Use jModel for postTag.Improve getTagNameById
82edd622fc9 Complete initial work on postTag.TODO: Finish metadata handling and parameters. Finish swagger doc block.
a5cfd0d7c7f getTagFields, postTag
83c97cd9f3e getTagTypes, getTagSearch, getTagNameById
9d9bc9544a2 Build new Tag methods.
a3e35260d55 span title="Include "Authorization" in Access-Control-Allow-Headers as per request Include "Authorization" in Access-Control-Allow-Headers as per request https://www.annatech.com/forums/capi-wish-list/25-adding-authorization-in-htaccess.html#84
ab554d3b9a9 Update version and year.

Updated documentation can be found here:
http://learn.getcapi.org

API Doc and Sandbox

https://getcapi.io

View files

Releases per page:

Subscribe To Our Newsletter!