1 | initial version |
We do not offer WSDL by default, I am going to elaborate on what we can offer. For starters, the resources for each GEri are normally on the FIWARE Catalogue (catalogue.fiware.org)
The REST APIs are typically under readthedocs, github and APIary in human readable format. For instance, if we follow links for Orion contextBroker GEri, you can find loads of info for the API:
However, there is a .apib (API blueprint) file for each one of them, in this case :
For your convenience, may I point out that we have a quick list of resources per GE in release 4 here:
2 | No.2 Revision |
We do not offer WSDL by default, I am going to elaborate on what we can offer. For starters, the resources for each GEri are normally on the FIWARE Catalogue (catalogue.fiware.org)
The REST APIs are typically under readthedocs, github and APIary in human readable format. For instance, if we follow links for Orion contextBroker GEri, you can find loads of info for the API:
However, there is a .apib (API blueprint) file for each one of them, in this case :
For your convenience, may I point out that we have a quick list of resources per GE in release 4 here:
3 | No.3 Revision |
We do not offer WSDL by default, I am going to elaborate on what we can offer. For starters, the resources for each GEri are normally on the FIWARE Catalogue (catalogue.fiware.org)
The REST APIs are typically under readthedocs, github and APIary in human readable format. For instance, if we follow links for Orion contextBroker GEri, you can find loads of info for the API:
However, there is a .apib (API blueprint) file for each one of them, in this case :
For your convenience, may I point out that we have a quick list of resources per GE in release 4 here: