API Documentation. In the following table the available HTTP request is described in detail. The Swagger file is available at xxxx://000.000.00.000:00000/xxxxxxx/. URL xxxx://000.000.00.000:00000/xxx_x_00/xxxxxxx/xxxxxx/xxxxxxxx Method POST URL parameters None
API Documentation. The following table describe the available HTTP requests in detail. Operation URL xxxx://000.000.00.000:0000/xxxxx/xxxxxxxxxx/xxx/xxxxx/xxx- page/google-play/ METHOD POST URL parameters None
API Documentation. The available HTTP request is described in detail below. The Swagger file is available at xxxx://000.000.00.000:00000/xxxxxxx/. URL xxxx://000.000.00.000:00000/xxx_x_00/xxxxxxx/xx_xxxx Method POST URL parameters None Request example {“listOfBlocks” : [ "Railway line Xxxx Selo – Križevci is a constituent part of the branch Vb , Paneuropean corridor pass through the territory of the Republic of Croatia and the railway line M201 State border – Koprivnica – Xxxx Selo . The exist railway line has one track, large inter- station distance and be already now of limited transportation and maximum railway capacity with no possibility of capacity enhance”]}
API Documentation. In the following table the available HTTP requests is extensively reported. The Swagger file is available at xxxx://000.000.00.000:00000/xxxxxxx/. URL xxxx://000.000.00.000:00000/xxx_x_00/xxxxxxxx/xxxxxxxxxx/<string:e xtr_type> Method POST URL parameters Language model alias for entity linking, e.g. ‘en’ for English
API Documentation. The available HTTP request is outlined below. More information can be found in the Swagger, available at xxxx://000.000.00.000:0000/xxx/xxxxxxxxxx-xxxxxxxxx/xxxxxxx- ui.html. json/ontology URL xxxx://000.000.00.000:0000/xxx/xxxxxxxxxx- detection/json/ontology/{projectId} METHOD POST URL parameters projectId: id of the project containing the requirements to analyze
API Documentation. API Documentation refers to the protocols, language, syntax, and rules compiled in the electronic standard reference mate- rial provided by Connect One, which describe the API functio- nality and provide instructions for the development of pro- gramming interfaces. Cloud Feeder Cloud Feeders are reading devices that enable automated identification and assignment of UIDs to products and orders. Service Service refers to the cloud-based technology and application software specified in the SaaS agreement. IoT IoT stands for Internet of Things and refers to a network of physical objects ("Things") equipped with sensors, software, and other technology to connect them to other devices and systems via the Internet. Customer Content Customer Content refers to the data, media, and content pro- vided by the customer as part of the service and collaboration.
API Documentation. All classes and methods in the reference implementation have been documented with Doxygen code block comments. For each released version the comments have been generated to HTML files that are easy to view in any web browser. The files have also been combined into a single Compiled HTML file that is included in the released zip file. Unfortunately the formatting in the compiled HTML file is not as smooth as in the original HTML files. The compiled file can be searched or navigated through via class hierarchy or file list. However, as the resulting file links to all the classes, structs and namespaces in the project it can be difficult to find what you are looking for if you don’t already know the answer. Therefore the most important classes have been added as separate “Modules” that can be found on the main navigation toolbar. These module classes are the actor components which in turn contain all the methods that are exposed in Unreal via the blueprint graph in the DigitalHumanProcessing.
API Documentation. The documentation, data and information that BridalLive provides regarding the use of the BridalLive API. BridalLive API or “our API” – The publicly available BridalLive Application Programming Interface (“API”) as well as the related API Documentation. BridalLive Brand – The BridalLive brand and brand assets, including names, logos, trade names and trademarks. BridalLive Service(s) – BridalLive’s all-in-one IT solution for bridal and formal wear retail businesses, including point of sale, inventory and ordering, marketing, scheduling and event management services and related systems and technologies, as well as the website xxxx://xxx.XxxxxxXxxx.xxx (the “Site”), and all software, applications, data, reports, text, images, and other content made available by or on behalf of BridalLive through any of the foregoing. The “Service” does not include User Content or any software application or service that is provided by you or a third party (including Applications).
API Documentation. The documentation, data and information provided by Company regarding use of Company’s API through the Developer Site. Application: Any software application, website, or product Developer creates, or service Developer offers, using Company’s API.
API Documentation. Licensor has provided Licensee Licensor’s proprietary API documentation. Implementation of the API into Licensee’s software application will provide access to query Licensor’s database containing the Data and retrieve information related to the Data. Licensee may implement the API into Licensee’s software application, except as provided in Section 3.2.
