Documentation
¶
Overview ¶
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v5 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
* Infiot API * * # Introduction <b>Infiot</b> provides API endpoints for interacting with <b> Infiot Management Portal</b>, so that you can rapidly deploy IoT at scale anywhere with automation. <b>Infiot's</b> Developer-friendly SDKs and APIs enable seamless integration.Leverage <b>Infiot SDK</b> and seamlessly integrate with additional services for early time-to-market. The <b>Infiot API</b> is a powerful [REST API](https://en.wikipedia.org/wiki/Representational_state_transfer) that can be accessed by an [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) client tools such as curl/wget, or HTTP libraries of most modern programming languages including Python, GoLang, Java. The API provides abundance of features, listing some of the top rated ones, * Support to interact securely with our API Servers from a Client Web application (<b>API tokens should never be exposed outside</b>). * The API responds with a well-formatted [JSON](http://www.json.org/) data. * Support for built-in HTTP features, like HTTP authentication and HTTP verbs, which can be easily interpreted by any HTTP clients that are designed to comply with [HTTP RFC](https://tools.ietf.org/html/rfc2616). If you have good knowledge with REST API, our reference guide will help serve you to get started. To start using <b>Infiot</b> APIs, API tokens need to be created If you have any questions you can reach out to us on [support@infiot.com](mailto:support@infiot.com) # Endpoints Our APIs can be accessed through HTTP requests to our API Servers. There are different API servers provisioned based on production stages. The user has to select the applicable API server from the given list of servers populated, and punch in the appropriate MSP tenant name field to get started: ``` https://{tenant}.api.infiot.net ``` All our APIs are [versioned] (#versioning). If there are any changes to the API which either changes the response format or request parameter, the version would be incremented accordingly. # Authentication To authenticate your API request you will need to include your secret token. You can manage your API tokens in the Infiot MSP Portal.The user should have appropriate privileges in the tenant portal for the tokens option to be visible. Tokens can be generated from `Tokens` navigation window.Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on. All API requests must be made over secure HTTP [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail. Once the token is generated and ready to use, authorize the API token in the swagger hub, click on the `Authorize` button and in the pop-up, fill the API token and click on `Authorize` again. # Request Methods Our API endpoints use [HTTP request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) to specify the desired operation to be performed. The documentation below specifies request method supported by each endpoint and the resulting action with its appropriate CRUD workflow. | Method Type | CRUD | Description | |- |- |- | | GET | Read | GET requests can be used to retrieve data (eg: get all tenant details from a Master MSP or MSP) | | POST | Create | POST requests can be used to create a new record (eg: adding new tenants to the Master MSP or MSP) | | PUT | Update/Replace | PUT requests can be used for updating an existing record (eg: updating the name or description of a MSP | | DELETE | Delete | DELETE requests can be used to delete a record (like deleting a MSP from the Master MSP) | # Response Codes All API requests will respond with appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). Your API client should handle each response class differently. | Response Code | Description | |- |- | | 2XX | These are successful responses and indicate that the API request returned the expected response | | 4XX | These indicate that there was a problem with the request like a missing parameter or invalid values | |5XX | These indicate server errors when the server is unreachable or is misconfigured. In this case, you should retry the API request after some delay | # <a name=\"versioning\"></a>Versioning All our APIs are versioned. Our current API version is `v1` and we are continuously working on improving it further and provide additional endpoints. If there are any changes to an API which either changes the response format or request parameter, we will increment the version. * * API version: v9 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
Index ¶
- Variables
- func CacheExpires(r *http.Response) time.Time
- type APIClient
- type APIKey
- type APIResponse
- type AddDevicePolicyInput
- type AddEdgeInput
- type AddPolicyFirewallRuleInput
- type AddPolicyInput
- type AddPolicyQoSRuleInput
- type AllOfGatewayWanPathsAndLinksStatsData
- type BasicAuth
- type ClientConfiguration
- type ClientIpv4PoolRangesInner
- type CloneIdInput
- type Configuration
- type DataUsageLimitSetting
- type DevicePoliciesApiAddDevicePolicyOpts
- type DevicePoliciesApiDeleteDevicePolicyByIdOpts
- type DevicePoliciesApiGetAllDevicePoliciesOpts
- type DevicePoliciesApiGetDevicePolicyByIdOpts
- type DevicePoliciesApiService
- func (a *DevicePoliciesApiService) AddDevicePolicy(ctx context.Context, body AddDevicePolicyInput, ...) (ManagedDevicePolicy, *http.Response, error)
- func (a *DevicePoliciesApiService) DeleteDevicePolicyById(ctx context.Context, id string, ...) (ManagedDevicePolicy, *http.Response, error)
- func (a *DevicePoliciesApiService) GetAllDevicePolicies(ctx context.Context, ...) (ManagedDevicePolicyList, *http.Response, error)
- func (a *DevicePoliciesApiService) GetDevicePolicyById(ctx context.Context, id string, ...) (ManagedDevicePolicy, *http.Response, error)
- func (a *DevicePoliciesApiService) UpdateDevicePolicyById(ctx context.Context, body ManagedDevicePolicy, id string, ...) (ManagedDevicePolicy, *http.Response, error)
- type DevicePoliciesApiUpdateDevicePolicyByIdOpts
- type DevicesApiAddManagedDeviceOpts
- type DevicesApiDeleteManagedDeviceByIdOpts
- type DevicesApiGetManagedDeviceByIdOpts
- type DevicesApiGetManagedDeviceListOpts
- type DevicesApiGetOnlineDeviceListOpts
- type DevicesApiService
- func (a *DevicesApiService) AddManagedDevice(ctx context.Context, body ManagedDevice, id string, ...) (ManagedDevice, *http.Response, error)
- func (a *DevicesApiService) DeleteManagedDeviceById(ctx context.Context, id string, deviceId string, ...) (ManagedDevice, *http.Response, error)
- func (a *DevicesApiService) GetManagedDeviceById(ctx context.Context, id string, deviceId string, ...) (ManagedDevice, *http.Response, error)
- func (a *DevicesApiService) GetManagedDeviceList(ctx context.Context, id string, ...) (ManagedDeviceList, *http.Response, error)
- func (a *DevicesApiService) GetOnlineDeviceList(ctx context.Context, id string, ...) (ManagedDeviceList, *http.Response, error)
- func (a *DevicesApiService) UpdateManagedDeviceById(ctx context.Context, body ManagedDevice, id string, deviceId string, ...) (ManagedDevice, *http.Response, error)
- type DevicesApiUpdateManagedDeviceByIdOpts
- type DhcpRelayServerSettings
- type DhcpServerSettings
- type DhcpServerSettingsAddressRanges
- type DhcpServerSettingsCustomOptions
- type DhcpServerSettingsMacAddressToIpv4Bindings
- type Edge
- type EdgeActivationCode
- type EdgeBgpConfiguration
- type EdgeGenerateActivationCodeInput
- type EdgeModel
- type EdgeOverlayConfiguration
- type EdgeOverlayConfigurationRoutableAddresses
- type EdgeRef
- type EdgeRole
- type EdgeStatus
- type EdgeStatusDsDevstatusGeneral
- type EdgeStatusDsDevstatusGeneralDsgGeolocation
- type EdgeStatusDsFlowcounts
- type EdgeStatusDsLandevices
- type EdgeStatusDsPathstats
- type EdgeStatusDsPathstatsDspsPathstatsSample
- type EdgeStatusDsPathstatsDspsPs
- type EdgeStatusDsResusage
- type EdgeStatusDsResusageDsrContainers
- type EdgeStatusDsResusageDsrLoadavg
- type EdgeStatusDsResusageDsrMemory
- type EdgeStatusDsResusageDsrNetwork
- type EdgeStatusDsResusageDsrNetworkDsrnCellularStats
- type EdgeStatusDsResusageDsrNetworkDsrnIfGeolocation
- type EdgeStatusDsResusageDsrNetworkDsrnIfstats
- type EdgeStatusDsResusageDsrNetworkDsrnTrafficstats
- type EdgeStatusDsResusageDsrStorage
- type EdgeStatusDsUserinfo
- type EdgeStatusDsUserinfoDsuUsers
- type EdgeStatusRef
- type EdgesApiActivateEdgeByIdOpts
- type EdgesApiAddEdgeInterfaceOpts
- type EdgesApiAddEdgeOpts
- type EdgesApiDeleteEdgeByIdOpts
- type EdgesApiDeleteEdgeIfByNameOpts
- type EdgesApiGetAllEdgesOpts
- type EdgesApiGetEdgeByIdOpts
- type EdgesApiGetEdgeIfByNameOpts
- type EdgesApiGetEdgeInterfaceListOpts
- type EdgesApiGetEdgeStatusByIdOpts
- type EdgesApiService
- func (a *EdgesApiService) ActivateEdgeById(ctx context.Context, body EdgeGenerateActivationCodeInput, id string, ...) (EdgeActivationCode, *http.Response, error)
- func (a *EdgesApiService) AddEdge(ctx context.Context, body AddEdgeInput, localVarOptionals *EdgesApiAddEdgeOpts) (Edge, *http.Response, error)
- func (a *EdgesApiService) AddEdgeInterface(ctx context.Context, body InterfaceSettings, id string, ...) (Edge, *http.Response, error)
- func (a *EdgesApiService) DeleteEdgeById(ctx context.Context, id string, localVarOptionals *EdgesApiDeleteEdgeByIdOpts) (Edge, *http.Response, error)
- func (a *EdgesApiService) DeleteEdgeIfByName(ctx context.Context, id string, name string, ...) (Edge, *http.Response, error)
- func (a *EdgesApiService) GetAllEdges(ctx context.Context, localVarOptionals *EdgesApiGetAllEdgesOpts) (EdgesList, *http.Response, error)
- func (a *EdgesApiService) GetEdgeById(ctx context.Context, id string, localVarOptionals *EdgesApiGetEdgeByIdOpts) (Edge, *http.Response, error)
- func (a *EdgesApiService) GetEdgeIfByName(ctx context.Context, id string, name string, ...) (InterfaceSettings, *http.Response, error)
- func (a *EdgesApiService) GetEdgeInterfaceList(ctx context.Context, id string, ...) ([]InterfaceSettings, *http.Response, error)
- func (a *EdgesApiService) GetEdgeStatusById(ctx context.Context, id string, ...) (EdgeStatusRef, *http.Response, error)
- func (a *EdgesApiService) UpdateEdgeById(ctx context.Context, body UpdateEdgeInput, id string, ...) (Edge, *http.Response, error)
- func (a *EdgesApiService) UpdateEdgeIfByName(ctx context.Context, body InterfaceSettings, id string, name string, ...) (Edge, *http.Response, error)
- type EdgesApiUpdateEdgeByIdOpts
- type EdgesApiUpdateEdgeIfByNameOpts
- type EdgesList
- type FirewallRule
- type GatewayDevicesAggregatedDeviceFlowStats
- type GatewayDevicesAggregatedDeviceFlowStatsData
- type GatewayDevicesAggregatedDeviceStats
- type GatewayDevicesAggregatedDeviceStatsData
- type GatewayInterfacesLatestStats
- type GatewayInterfacesLatestStatsCellularStats
- type GatewayInterfacesLatestStatsData
- type GatewayInterfacesLatestStatsWifiStats
- type GatewayPathsLatestStats
- type GatewayPathsLatestStatsData
- type GatewayRoutesLatestStats
- type GatewayRoutesLatestStatsData
- type GatewaySysLoadStats
- type GatewaySysLoadStatsData
- type GatewaySysLteSignalStats
- type GatewaySysLteSignalStatsData
- type GatewaySysMemoryStats
- type GatewaySysMemoryStatsData
- type GatewaySysUptimeStats
- type GatewaySysUptimeStatsData
- type GatewaySysWiFiStrengthStats
- type GatewaySysWiFiStrengthStatsData
- type GatewayWanAggregatedPathsAndLinksStats
- type GatewayWanAggregatedPathsAndLinksStatsData
- type GatewayWanPathsAndLinksStats
- type GenericSwaggerError
- type InboundNatRule
- type InfiotErrorResponse
- type InterfaceSettings
- type InterfaceSettingsAddresses
- type L4Protocols
- type LteInterfaceSetting
- type ManagedDevice
- type ManagedDeviceList
- type ManagedDevicePolicy
- type ManagedDevicePolicyList
- type ManagedDevicePolicyService
- type ManagedDeviceProps
- type ManagedDeviceService
- type MonitoringApiGetGatewayAggregatedDeviceFlowStatsByIDOpts
- type MonitoringApiGetGatewayAggregatedDeviceStatsByIDOpts
- type MonitoringApiGetGatewayAggregatedPathAndLinkStatsByIDOpts
- type MonitoringApiGetGatewayLTESignalStatsByIDOpts
- type MonitoringApiGetGatewayLatestInterfaceStatsByIDOpts
- type MonitoringApiGetGatewayLatestPathStatsByIDOpts
- type MonitoringApiGetGatewayLatestRouteStatsByIDOpts
- type MonitoringApiGetGatewayLoadStatsByIDOpts
- type MonitoringApiGetGatewayMemoryStatsByIDOpts
- type MonitoringApiGetGatewayPathAndLinkStatsByIDOpts
- type MonitoringApiGetGatewayUptimeStatsByIDOpts
- type MonitoringApiGetGatewayWiFiStrengthStatsByIDOpts
- type MonitoringApiService
- func (a *MonitoringApiService) GetGatewayAggregatedDeviceFlowStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewayDevicesAggregatedDeviceFlowStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayAggregatedDeviceStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewayDevicesAggregatedDeviceStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayAggregatedPathAndLinkStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewayWanAggregatedPathsAndLinksStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayLTESignalStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewaySysLteSignalStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayLatestInterfaceStatsByID(ctx context.Context, id string, ...) (GatewayInterfacesLatestStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayLatestPathStatsByID(ctx context.Context, id string, ...) (GatewayPathsLatestStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayLatestRouteStatsByID(ctx context.Context, id string, ...) (GatewayRoutesLatestStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayLoadStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewaySysLoadStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayMemoryStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewaySysMemoryStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayPathAndLinkStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewayWanPathsAndLinksStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayUptimeStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewaySysUptimeStats, *http.Response, error)
- func (a *MonitoringApiService) GetGatewayWiFiStrengthStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ...) (GatewaySysWiFiStrengthStats, *http.Response, error)
- type MqttgcpConfiguration
- type MqttgcpConfigurationTopic
- type NetflowCollector
- type NetflowExporterSetting
- type ObjectProps
- type ObjectRef
- type OverlaySetting
- type PagedResponse
- type PoliciesApiAddDenySourceIPRuleToPolicyOpts
- type PoliciesApiAddPolicyOpts
- type PoliciesApiAddQoSSourceIPRuleToPolicyOpts
- type PoliciesApiDeleteDenySourceIPRuleFromPolicyOpts
- type PoliciesApiDeletePolicyByIdOpts
- type PoliciesApiDeleteQoSSourceIPRuleFromPolicyOpts
- type PoliciesApiGetAllPoliciesOpts
- type PoliciesApiGetPolicyByIdOpts
- type PoliciesApiService
- func (a *PoliciesApiService) AddDenySourceIPRuleToPolicy(ctx context.Context, body AddPolicyFirewallRuleInput, id string, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) AddPolicy(ctx context.Context, body AddPolicyInput, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) AddQoSSourceIPRuleToPolicy(ctx context.Context, body AddPolicyQoSRuleInput, id string, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) DeleteDenySourceIPRuleFromPolicy(ctx context.Context, id string, ip string, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) DeletePolicyById(ctx context.Context, id string, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) DeleteQoSSourceIPRuleFromPolicy(ctx context.Context, id string, ip string, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) GetAllPolicies(ctx context.Context, localVarOptionals *PoliciesApiGetAllPoliciesOpts) ([]Policy, *http.Response, error)
- func (a *PoliciesApiService) GetPolicyById(ctx context.Context, id string, ...) (Policy, *http.Response, error)
- func (a *PoliciesApiService) UpdatePolicyById(ctx context.Context, body Policy, id string, ...) (Policy, *http.Response, error)
- type PoliciesApiUpdatePolicyByIdOpts
- type Policy
- type PolicyClassOfService
- type PolicyConfig
- type PolicyConfigPcfgFirewall
- type PolicyConfigPcfgFirewallPcfgFwLogging
- type PolicyConfigPcfgGeneralSettings
- type PolicyConfigPcfgGeneralSettingsPcfgNetflow
- type PolicyConfigPcfgUrlFilter
- type PolicyFirewallAction
- type PolicyLinkSteeringAction
- type PolicyLinkSteeringActionLnksVia
- type PolicyLinkSteeringActionLnksViaActive
- type PolicyLinkSteeringActionLnksViaBackup
- type PolicyMatchRule
- type PolicyPbrAction
- type PolicyQoS
- type PolicyQoSAction
- type PolicyRef
- type PolicySchedulerAction
- type PolicyTrafficAction
- type PolicyTrafficPriority
- type PolicyType
- type ProxyArpSetting
- type RadiusSetting
- type SnmpSetting
- type SnmpTrapSetting
- type StaticRoute
- type SyslogServer
- type Tenant
- type TenantTypeInput
- type TenantsApiAddTenantOpts
- type TenantsApiDeleteTenantByIdOpts
- type TenantsApiGetAllTenantsOpts
- type TenantsApiGetTenantByIdOpts
- type TenantsApiService
- func (a *TenantsApiService) AddTenant(ctx context.Context, body Tenant, localVarOptionals *TenantsApiAddTenantOpts) (Tenant, *http.Response, error)
- func (a *TenantsApiService) DeleteTenantById(ctx context.Context, tenantId string, ...) (Tenant, *http.Response, error)
- func (a *TenantsApiService) GetAllTenants(ctx context.Context, localVarOptionals *TenantsApiGetAllTenantsOpts) (TenantsList, *http.Response, error)
- func (a *TenantsApiService) GetTenantById(ctx context.Context, tenantId string, ...) (Tenant, *http.Response, error)
- func (a *TenantsApiService) UpdateTenantById(ctx context.Context, body Tenant, tenantId string, ...) (Tenant, *http.Response, error)
- type TenantsApiUpdateTenantByIdOpts
- type TenantsList
- type TimeSeriesProps
- type TrafficMatchCriteria
- type UpdateEdgeInput
- type User
- type UserGroupRef
- type UserRef
- type UserRole
- type UsersApiAddUserOpts
- type UsersApiDeleteUserByIdOpts
- type UsersApiGetAllUsersOpts
- type UsersApiGetUserByIdOpts
- type UsersApiService
- func (a *UsersApiService) AddUser(ctx context.Context, body User, localVarOptionals *UsersApiAddUserOpts) (User, *http.Response, error)
- func (a *UsersApiService) DeleteUserById(ctx context.Context, id string, localVarOptionals *UsersApiDeleteUserByIdOpts) (User, *http.Response, error)
- func (a *UsersApiService) GetAllUsers(ctx context.Context, localVarOptionals *UsersApiGetAllUsersOpts) ([]User, *http.Response, error)
- func (a *UsersApiService) GetUserById(ctx context.Context, id string, localVarOptionals *UsersApiGetUserByIdOpts) (User, *http.Response, error)
- func (a *UsersApiService) UpdateUserById(ctx context.Context, body User, id string, ...) (User, *http.Response, error)
- type UsersApiUpdateUserByIdOpts
- type Vrrp
- type WebReputation
- type WiFiInterfaceSetting
- type WiFiInterfaceSettingEncryption
Constants ¶
This section is empty.
Variables ¶
var ( // ContextOAuth2 takes a oauth2.TokenSource as authentication for the request. ContextOAuth2 = contextKey("token") // ContextBasicAuth takes BasicAuth as authentication for the request. ContextBasicAuth = contextKey("basic") // ContextAccessToken takes a string oauth2 access token as authentication for the request. ContextAccessToken = contextKey("accesstoken") // ContextAPIKey takes an APIKey as authentication for the request ContextAPIKey = contextKey("apikey") )
Functions ¶
Types ¶
type APIClient ¶
type APIClient struct {
DevicePoliciesApi *DevicePoliciesApiService
DevicesApi *DevicesApiService
EdgesApi *EdgesApiService
MonitoringApi *MonitoringApiService
PoliciesApi *PoliciesApiService
TenantsApi *TenantsApiService
UsersApi *UsersApiService
// contains filtered or unexported fields
}
APIClient manages communication with the Infiot API API vv9 In most cases there should be only one, shared, APIClient.
func NewAPIClient ¶
func NewAPIClient(cfg *Configuration) *APIClient
NewAPIClient creates a new API client. Requires a userAgent string describing your application. optionally a custom http.Client to allow for advanced features such as caching.
func (*APIClient) ChangeBasePath ¶
Change base path to allow switching to mocks
type APIKey ¶
APIKey provides API key based authentication to a request passed via context using ContextAPIKey
type APIResponse ¶
type APIResponse struct {
*http.Response `json:"-"`
Message string `json:"message,omitempty"`
// Operation is the name of the swagger operation.
Operation string `json:"operation,omitempty"`
// RequestURL is the request URL. This value is always available, even if the
// embedded *http.Response is nil.
RequestURL string `json:"url,omitempty"`
// Method is the HTTP method used for the request. This value is always
// available, even if the embedded *http.Response is nil.
Method string `json:"method,omitempty"`
// Payload holds the contents of the response body (which may be nil or empty).
// This is provided here as the raw response.Body() reader will have already
// been drained.
Payload []byte `json:"-"`
}
func NewAPIResponse ¶
func NewAPIResponse(r *http.Response) *APIResponse
func NewAPIResponseWithError ¶
func NewAPIResponseWithError(errorMessage string) *APIResponse
type AddDevicePolicyInput ¶
type AddDevicePolicyInput struct {
MdplcName string `json:"mdplc_name,omitempty"`
MdplcType string `json:"mdplc_type,omitempty"`
MdplcDeviceServices []ManagedDevicePolicyService `json:"mdplc_device_services,omitempty"`
MdplcUserGroups []UserGroupRef `json:"mdplc_user_groups,omitempty"`
}
type AddEdgeInput ¶
type AddEdgeInput struct {
SourceTenantId string `json:"sourceTenantId,omitempty"`
SourceObjectId string `json:"sourceObjectId,omitempty"`
Model *EdgeModel `json:"model,omitempty"`
Name string `json:"name,omitempty"`
Description string `json:"description,omitempty"`
Role *EdgeRole `json:"role,omitempty"`
Serialnumber string `json:"serialnumber,omitempty"`
AssignedPolicy *PolicyRef `json:"assignedPolicy,omitempty"`
IsTemplate bool `json:"isTemplate,omitempty"`
Ipv4PoolRanges *[]ClientIpv4PoolRangesInner `json:"ipv4PoolRanges,omitempty"`
}
type AddPolicyFirewallRuleInput ¶
type AddPolicyFirewallRuleInput struct {
Ip string `json:"ip,omitempty"`
}
type AddPolicyInput ¶
type AddPolicyInput struct {
SourceTenantId string `json:"sourceTenantId,omitempty"`
SourceObjectId string `json:"sourceObjectId,omitempty"`
Name string `json:"name,omitempty"`
Type_ *PolicyType `json:"type,omitempty"`
Hubs []EdgeRef `json:"hubs,omitempty"`
Config *PolicyConfig `json:"config,omitempty"`
}
type AddPolicyQoSRuleInput ¶
type AddPolicyQoSRuleInput struct {
Ip string `json:"ip,omitempty"`
Priority *PolicyTrafficPriority `json:"priority,omitempty"`
}
type BasicAuth ¶
type BasicAuth struct {
UserName string `json:"userName,omitempty"`
Password string `json:"password,omitempty"`
}
BasicAuth provides basic http authentication to a request passed via context using ContextBasicAuth
type ClientConfiguration ¶
type ClientConfiguration struct {
AlwaysOn bool `json:"alwaysOn,omitempty"`
DisableVif bool `json:"disableVif,omitempty"`
DnsSuffixes []string `json:"dnsSuffixes,omitempty"`
Ipv4DnsServers []string `json:"ipv4DnsServers,omitempty"`
Ipv4PoolRanges *[]ClientIpv4PoolRangesInner `json:"ipv4PoolRanges,omitempty"`
AssignedVirtualIPAddress string `json:"assignedVirtualIPAddress,omitempty"`
}
type CloneIdInput ¶
type Configuration ¶
type Configuration struct {
BasePath string `json:"basePath,omitempty"`
Host string `json:"host,omitempty"`
Scheme string `json:"scheme,omitempty"`
DefaultHeader map[string]string `json:"defaultHeader,omitempty"`
UserAgent string `json:"userAgent,omitempty"`
HTTPClient *http.Client
}
func NewConfiguration ¶
func NewConfiguration() *Configuration
func (*Configuration) AddDefaultHeader ¶
func (c *Configuration) AddDefaultHeader(key string, value string)
type DataUsageLimitSetting ¶
type DevicePoliciesApiService ¶
type DevicePoliciesApiService service
func (*DevicePoliciesApiService) AddDevicePolicy ¶
func (a *DevicePoliciesApiService) AddDevicePolicy(ctx context.Context, body AddDevicePolicyInput, localVarOptionals *DevicePoliciesApiAddDevicePolicyOpts) (ManagedDevicePolicy, *http.Response, error)
func (*DevicePoliciesApiService) DeleteDevicePolicyById ¶
func (a *DevicePoliciesApiService) DeleteDevicePolicyById(ctx context.Context, id string, localVarOptionals *DevicePoliciesApiDeleteDevicePolicyByIdOpts) (ManagedDevicePolicy, *http.Response, error)
func (*DevicePoliciesApiService) GetAllDevicePolicies ¶
func (a *DevicePoliciesApiService) GetAllDevicePolicies(ctx context.Context, localVarOptionals *DevicePoliciesApiGetAllDevicePoliciesOpts) (ManagedDevicePolicyList, *http.Response, error)
func (*DevicePoliciesApiService) GetDevicePolicyById ¶
func (a *DevicePoliciesApiService) GetDevicePolicyById(ctx context.Context, id string, localVarOptionals *DevicePoliciesApiGetDevicePolicyByIdOpts) (ManagedDevicePolicy, *http.Response, error)
func (*DevicePoliciesApiService) UpdateDevicePolicyById ¶
func (a *DevicePoliciesApiService) UpdateDevicePolicyById(ctx context.Context, body ManagedDevicePolicy, id string, localVarOptionals *DevicePoliciesApiUpdateDevicePolicyByIdOpts) (ManagedDevicePolicy, *http.Response, error)
type DevicesApiService ¶
type DevicesApiService service
func (*DevicesApiService) AddManagedDevice ¶
func (a *DevicesApiService) AddManagedDevice(ctx context.Context, body ManagedDevice, id string, localVarOptionals *DevicesApiAddManagedDeviceOpts) (ManagedDevice, *http.Response, error)
func (*DevicesApiService) DeleteManagedDeviceById ¶
func (a *DevicesApiService) DeleteManagedDeviceById(ctx context.Context, id string, deviceId string, localVarOptionals *DevicesApiDeleteManagedDeviceByIdOpts) (ManagedDevice, *http.Response, error)
func (*DevicesApiService) GetManagedDeviceById ¶
func (a *DevicesApiService) GetManagedDeviceById(ctx context.Context, id string, deviceId string, localVarOptionals *DevicesApiGetManagedDeviceByIdOpts) (ManagedDevice, *http.Response, error)
func (*DevicesApiService) GetManagedDeviceList ¶
func (a *DevicesApiService) GetManagedDeviceList(ctx context.Context, id string, localVarOptionals *DevicesApiGetManagedDeviceListOpts) (ManagedDeviceList, *http.Response, error)
func (*DevicesApiService) GetOnlineDeviceList ¶
func (a *DevicesApiService) GetOnlineDeviceList(ctx context.Context, id string, localVarOptionals *DevicesApiGetOnlineDeviceListOpts) (ManagedDeviceList, *http.Response, error)
func (*DevicesApiService) UpdateManagedDeviceById ¶
func (a *DevicesApiService) UpdateManagedDeviceById(ctx context.Context, body ManagedDevice, id string, deviceId string, localVarOptionals *DevicesApiUpdateManagedDeviceByIdOpts) (ManagedDevice, *http.Response, error)
type DhcpRelayServerSettings ¶
type DhcpRelayServerSettings struct {
RelayServerIpList []string `json:"relayServerIpList,omitempty"`
}
type DhcpServerSettings ¶
type DhcpServerSettings struct {
Network string `json:"network,omitempty"`
AddressRanges []DhcpServerSettingsAddressRanges `json:"addressRanges,omitempty"`
LeaseDuration int32 `json:"leaseDuration,omitempty"`
DnsPrimary string `json:"dnsPrimary,omitempty"`
DnsSecondary string `json:"dnsSecondary,omitempty"`
MacAddressToIpv4Bindings []DhcpServerSettingsMacAddressToIpv4Bindings `json:"macAddressToIpv4Bindings,omitempty"`
CustomOptions []DhcpServerSettingsCustomOptions `json:"customOptions,omitempty"`
}
type Edge ¶
type Edge struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
Id string `json:"id,omitempty"`
Model *EdgeModel `json:"model,omitempty"`
// The display name of the edge
Name string `json:"name,omitempty"`
// Additional notes about the edge
Description string `json:"description,omitempty"`
// True if edge is activated
Activated bool `json:"activated,omitempty"`
Role *EdgeRole `json:"role,omitempty"`
// Serial number of the edge
Serialnumber string `json:"serialnumber,omitempty"`
// Version of the software manifest assigned to this edge
Swversion string `json:"swversion,omitempty"`
// URL of the software manifest assined to this edge
Swmanifest string `json:"swmanifest,omitempty"`
OverlayConfiguration *EdgeOverlayConfiguration `json:"overlayConfiguration,omitempty"`
Psk string `json:"psk,omitempty"`
PublicKey string `json:"publicKey,omitempty"`
BgpConfiguration []EdgeBgpConfiguration `json:"bgpConfiguration,omitempty"`
StaticRoutes []StaticRoute `json:"staticRoutes,omitempty"`
MqttConfiguration *MqttgcpConfiguration `json:"mqttConfiguration,omitempty"`
AssignedPolicy *PolicyRef `json:"assignedPolicy,omitempty"`
One2OneNatRules []InboundNatRule `json:"one2OneNatRules,omitempty"`
PortForwardingNatRules []InboundNatRule `json:"portForwardingNatRules,omitempty"`
Interfaces []InterfaceSettings `json:"interfaces,omitempty"`
IsTemplate bool `json:"isTemplate,omitempty"`
ClientConfiguration *ClientConfiguration `json:"clientConfiguration,omitempty"`
Source *ObjectRef `json:"source,omitempty"`
}
type EdgeActivationCode ¶
type EdgeActivationCode struct {
Token string `json:"token,omitempty"`
}
type EdgeBgpConfiguration ¶
type EdgeBgpConfiguration struct {
Name string `json:"name,omitempty"`
Neighbor string `json:"neighbor,omitempty"`
RouterId string `json:"routerId,omitempty"`
RemoteAS int32 `json:"remoteAS,omitempty"`
LocalAS int32 `json:"localAS,omitempty"`
IsBfdEnabled bool `json:"isBfdEnabled,omitempty"`
// BFD interval in milli seconds
BfdInterval int32 `json:"bfdInterval,omitempty"`
// BFD recieve interval in milli seconds
BfdRecvInterval int32 `json:"bfdRecvInterval,omitempty"`
BfdMultiplier int32 `json:"bfdMultiplier,omitempty"`
}
type EdgeOverlayConfiguration ¶
type EdgeOverlayConfiguration struct {
Ip string `json:"ip,omitempty"`
Mask string `json:"mask,omitempty"`
RoutableAddresses []EdgeOverlayConfigurationRoutableAddresses `json:"routableAddresses,omitempty"`
}
type EdgeStatus ¶
type EdgeStatus struct {
// Major Schema Version
DsSchemaverMajor int32 `json:"ds_schemaver_major,omitempty"`
// Minor Schema Version
DsSchemaverMinor int32 `json:"ds_schemaver_minor,omitempty"`
DsEvtCreated int32 `json:"ds_evt_created,omitempty"`
DsDevstatusGeneral *EdgeStatusDsDevstatusGeneral `json:"ds_devstatus_general,omitempty"`
DsPathstats *EdgeStatusDsPathstats `json:"ds_pathstats,omitempty"`
DsFlowcounts *EdgeStatusDsFlowcounts `json:"ds_flowcounts,omitempty"`
DsLandevices []EdgeStatusDsLandevices `json:"ds_landevices,omitempty"`
DsResusage *EdgeStatusDsResusage `json:"ds_resusage,omitempty"`
DsUserinfo *EdgeStatusDsUserinfo `json:"ds_userinfo,omitempty"`
}
type EdgeStatusDsDevstatusGeneral ¶
type EdgeStatusDsDevstatusGeneral struct {
// Id of this site
DsgId string `json:"dsg_id,omitempty"`
// IP address of overlay
DsgOverlayId string `json:"dsg_overlay_id,omitempty"`
// Name of this edge
DsgName string `json:"dsg_name,omitempty"`
// Version of the software (Display version) running on this edge.
DsgSwversion string `json:"dsg_swversion,omitempty"`
// Id of the tenant
DsgTenantId string `json:"dsg_tenant_id,omitempty"`
// Name of the tenant
DsgTenantName string `json:"dsg_tenant_name,omitempty"`
// Activation URI of this edge
DsgActuri string `json:"dsg_acturi,omitempty"`
// Time of activation
DsgActdate string `json:"dsg_actdate,omitempty"`
// The device activation token has expired
DsgActtokinvalid bool `json:"dsg_acttokinvalid,omitempty"`
// Edge time and date in local time zone
DsgLtime string `json:"dsg_ltime,omitempty"`
// Edge uptime in seconds
DsgUptime int32 `json:"dsg_uptime,omitempty"`
// URI of the software manifest
DsgAswmuri string `json:"dsg_aswmuri,omitempty"`
// Status of the applied configuration version
DsgAconfigv string `json:"dsg_aconfigv,omitempty"`
// Applied configuration version
DsgAconfigt string `json:"dsg_aconfigt,omitempty"`
// Name of the ISPs to which the WAN public ip belongs
DsgIspname []string `json:"dsg_ispname,omitempty"`
DsgGeolocation []EdgeStatusDsDevstatusGeneralDsgGeolocation `json:"dsg_geolocation,omitempty"`
// Status of the edge device when it is part of an HA pair
DsgHastatus string `json:"dsg_hastatus,omitempty"`
}
type EdgeStatusDsFlowcounts ¶
type EdgeStatusDsFlowcounts struct {
// Number of flows seen in backup link
DsfcBackupLinkCnt int32 `json:"dsfc_backup_link_cnt,omitempty"`
// Number of flows seen in active link
DsfcActiveLinkCnt int32 `json:"dsfc_active_link_cnt,omitempty"`
// Number of flows seen in backup path
DsfcBackupPathCnt int32 `json:"dsfc_backup_path_cnt,omitempty"`
// Number of flows seen in active path
DsfcActivePathCnt int32 `json:"dsfc_active_path_cnt,omitempty"`
// Number of flows for which FEC was applied
DsfcDegradeFecCnt int32 `json:"dsfc_degrade_fec_cnt,omitempty"`
DsfcDegradeSwitchCnt int32 `json:"dsfc_degrade_switch_cnt,omitempty"`
DsfcDownSwitchCnt int32 `json:"dsfc_down_switch_cnt,omitempty"`
// Total number of direct flows
DsfcDirectCnt int32 `json:"dsfc_direct_cnt,omitempty"`
// Total number of overlay flows
DsfcOverlayCnt int32 `json:"dsfc_overlay_cnt,omitempty"`
// Total number of closed UDP flows
DsfcUdpCloseCnt int32 `json:"dsfc_udp_close_cnt,omitempty"`
// Total number of open UDP flows
DsfcUdpOpenCnt int32 `json:"dsfc_udp_open_cnt,omitempty"`
// Total number of closed TCP flows
DsfcTcpCloseCnt int32 `json:"dsfc_tcp_close_cnt,omitempty"`
// Total number of open TCP flows
DsfcTcpOpenCnt int32 `json:"dsfc_tcp_open_cnt,omitempty"`
// Total number of closed ICMP flows
DsfcIcmpCloseCnt int32 `json:"dsfc_icmp_close_cnt,omitempty"`
// Total number of open ICMP flows
DsfcIcmpOpenCnt int32 `json:"dsfc_icmp_open_cnt,omitempty"`
// Total number of closed flows
DsfcTotalCloseCnt int32 `json:"dsfc_total_close_cnt,omitempty"`
// Total number of open flows
DsfcTotalOpenCnt int32 `json:"dsfc_total_open_cnt,omitempty"`
}
type EdgeStatusDsLandevices ¶
type EdgeStatusDsLandevices struct {
DslIpv4 string `json:"dsl_ipv4,omitempty"`
// Name of the connected LAN device
DslName string `json:"dsl_name,omitempty"`
// Protocol of the connected LAN device
DslProtocol string `json:"dsl_protocol,omitempty"`
// State of the device, true indicates device is online
DslState bool `json:"dsl_state,omitempty"`
// Mac address of this device
DslMacAddr string `json:"dsl_mac_addr,omitempty"`
// Total amount of traffic transmitted by this device in bytes
DslTxbytes int32 `json:"dsl_txbytes,omitempty"`
// Total amount of traffic transmitted by this device in packets
DslTxpkts int32 `json:"dsl_txpkts,omitempty"`
// Total amount of traffic received by this device in bytes
DslRxbytes int32 `json:"dsl_rxbytes,omitempty"`
// Total amount of traffic received by this device in packets
DslRxpkts int32 `json:"dsl_rxpkts,omitempty"`
// String containing DHCP finger print.
DslDhcpFp string `json:"dsl_dhcp_fp,omitempty"`
// Indicates whether the device is a LAN device (internal) WAN device (external), special devices added by admin (managed) or the edge itself (infiotedge)
DslDeviceType string `json:"dsl_device_type,omitempty"`
}
type EdgeStatusDsPathstats ¶
type EdgeStatusDsPathstats struct {
// Sampling frequency, indicates the sampling granularity in seconds
DspsSfreq int32 `json:"dsps_sfreq,omitempty"`
// Number of samples present in this block.
DspsScount int32 `json:"dsps_scount,omitempty"`
// Pathstats sample giving stats at the start of each sampling interval.
DspsPathstatsSample []EdgeStatusDsPathstatsDspsPathstatsSample `json:"dsps_pathstats_sample,omitempty"`
}
High frequency stats about all the paths present in this edge
type EdgeStatusDsPathstatsDspsPathstatsSample ¶
type EdgeStatusDsPathstatsDspsPathstatsSample struct {
// A single sample containing information about paths
DspsPs []EdgeStatusDsPathstatsDspsPs `json:"dsps_ps,omitempty"`
}
type EdgeStatusDsPathstatsDspsPs ¶
type EdgeStatusDsPathstatsDspsPs struct {
DspsOverlayIp string `json:"dsps_overlay_ip,omitempty"`
DspsOverlayIpName string `json:"dsps_overlay_ip_name,omitempty"`
DspsLocalIp string `json:"dsps_local_ip,omitempty"`
DspsRemoteIp string `json:"dsps_remote_ip,omitempty"`
DspsRxloss int32 `json:"dsps_rxloss,omitempty"`
DspsTxloss int32 `json:"dsps_txloss,omitempty"`
// Latency measure in this path
DspsLatency int32 `json:"dsps_latency,omitempty"`
// Jitter measure in this path
DspsJitter int32 `json:"dsps_jitter,omitempty"`
// Link through which traffic is sent
DspsLink string `json:"dsps_link,omitempty"`
// Traffic sent in this path in bytes
DspsTxbytes int32 `json:"dsps_txbytes,omitempty"`
// Traffic sent in this link in packets
DspsTxpkts int32 `json:"dsps_txpkts,omitempty"`
// Traffic recieved in this path in bytes
DspsRxbytes int32 `json:"dsps_rxbytes,omitempty"`
// Traffic recieved in this path in packets
DspsRxpkts int32 `json:"dsps_rxpkts,omitempty"`
// Status of the remote overlay interface
DspsRemoteUp bool `json:"dsps_remote_up,omitempty"`
// Status of local overlay interface
DspsLocalUp bool `json:"dsps_local_up,omitempty"`
}
type EdgeStatusDsResusage ¶
type EdgeStatusDsResusage struct {
DsrLoadavg *EdgeStatusDsResusageDsrLoadavg `json:"dsr_loadavg,omitempty"`
DsrMemory *EdgeStatusDsResusageDsrMemory `json:"dsr_memory,omitempty"`
// Storage space reported in bytes
DsrStorage []EdgeStatusDsResusageDsrStorage `json:"dsr_storage,omitempty"`
DsrContainers []EdgeStatusDsResusageDsrContainers `json:"dsr_containers,omitempty"`
DsrNetwork *EdgeStatusDsResusageDsrNetwork `json:"dsr_network,omitempty"`
}
type EdgeStatusDsResusageDsrContainers ¶
type EdgeStatusDsResusageDsrContainers struct {
// Name of the container
DsrcoName string `json:"dsrco_name,omitempty"`
// Uptime of the container
DsrcoUptime int32 `json:"dsrco_uptime,omitempty"`
// Container state
DsrcoState string `json:"dsrco_state,omitempty"`
// Number of processes in the container
DsrcoPcount int32 `json:"dsrco_pcount,omitempty"`
}
type EdgeStatusDsResusageDsrLoadavg ¶
type EdgeStatusDsResusageDsrLoadavg struct {
// Load average of the past 1 minute
DsrlL1min float64 `json:"dsrl_l1min,omitempty"`
// Load average of the past 5 minutes
DsrlL5min float64 `json:"dsrl_l5min,omitempty"`
// Load average of the past 15 minutes
DsrlL15min float64 `json:"dsrl_l15min,omitempty"`
// Total number of processes running
DsrlPrunning int32 `json:"dsrl_prunning,omitempty"`
// Total number of processes in the system
DsrlPcount int32 `json:"dsrl_pcount,omitempty"`
}
type EdgeStatusDsResusageDsrMemory ¶
type EdgeStatusDsResusageDsrMemory struct {
// Sampling frequency
DsrmSfreq int32 `json:"dsrm_sfreq,omitempty"`
// Sample count
DsrmScount int32 `json:"dsrm_scount,omitempty"`
// Current Sample Index
DsrmSindex int32 `json:"dsrm_sindex,omitempty"`
// Total memory available in the system in KB
DsrmTotal int32 `json:"dsrm_total,omitempty"`
DsrmFree []int32 `json:"dsrm_free,omitempty"`
DsrmBuffered []int32 `json:"dsrm_buffered,omitempty"`
}
Memory reported in KiB
type EdgeStatusDsResusageDsrNetwork ¶
type EdgeStatusDsResusageDsrNetwork struct {
DsrnIfstats []EdgeStatusDsResusageDsrNetworkDsrnIfstats `json:"dsrn_ifstats,omitempty"`
}
type EdgeStatusDsResusageDsrNetworkDsrnCellularStats ¶
type EdgeStatusDsResusageDsrNetworkDsrnCellularStats struct {
CifConnected bool `json:"cif_connected,omitempty"`
CifNumdisconnects int32 `json:"cif_numdisconnects,omitempty"`
// Signal quality
CifSignalquality int32 `json:"cif_signalquality,omitempty"`
// Access technology
CifRadiolink string `json:"cif_radiolink,omitempty"`
// https://en.wikipedia.org/wiki/Access_Point_Name
CifApn string `json:"cif_apn,omitempty"`
// Mobile Network Operator
CifOperator string `json:"cif_operator,omitempty"`
// https://en.wikipedia.org/wiki/Mobile_country_code
CifOperatorid string `json:"cif_operatorid,omitempty"`
// https://en.wikipedia.org/wiki/International_mobile_subscriber_identity
CifImsi string `json:"cif_imsi,omitempty"`
// https://en.wikipedia.org/wiki/SIM_card
CifIccid string `json:"cif_iccid,omitempty"`
// https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity
CifImei string `json:"cif_imei,omitempty"`
// https://en.wikipedia.org/wiki/UTC_offset
CifTimezone int32 `json:"cif_timezone,omitempty"`
// https://en.wikipedia.org/wiki/Location_area_identity
CifLac int32 `json:"cif_lac,omitempty"`
// https://en.wikipedia.org/wiki/Cell_Global_Identity
CifCellid int32 `json:"cif_cellid,omitempty"`
CifGpsLat int32 `json:"cif_gps_lat,omitempty"`
CifGpsLng int32 `json:"cif_gps_lng,omitempty"`
CifGpsAlt int32 `json:"cif_gps_alt,omitempty"`
}
Cellular interface specific stats
type EdgeStatusDsResusageDsrNetworkDsrnIfstats ¶
type EdgeStatusDsResusageDsrNetworkDsrnIfstats struct {
// Sampling frequency
DsrnSfreq int32 `json:"dsrn_sfreq,omitempty"`
// Sampling count
DsrnScount int32 `json:"dsrn_scount,omitempty"`
// Current sample index
DsrnSindex int32 `json:"dsrn_sindex,omitempty"`
// Physical name of the interface
DsrnPhysicalname string `json:"dsrn_physicalname,omitempty"`
// Type of the interface
DsrnIftype string `json:"dsrn_iftype,omitempty"`
DsrnCellularStats *EdgeStatusDsResusageDsrNetworkDsrnCellularStats `json:"dsrn_cellular_stats,omitempty"`
// Logical name of the interface.
DsrnLogicalname string `json:"dsrn_logicalname,omitempty"`
// Indicates whether this interface is a overlay interface or not.
DsrnIsoverlay bool `json:"dsrn_isoverlay,omitempty"`
// Indicates whether this interface is up or down.
DsrnIfstate string `json:"dsrn_ifstate,omitempty"`
DsrnAddress []string `json:"dsrn_address,omitempty"`
DsrnPublicip string `json:"dsrn_publicip,omitempty"`
// Name of the ISP to which the public ip belongs
DsrnIfIspname string `json:"dsrn_if_ispname,omitempty"`
DsrnIfGeolocation *EdgeStatusDsResusageDsrNetworkDsrnIfGeolocation `json:"dsrn_if_geolocation,omitempty"`
// Transmission capacity (bandwidth) of this interface measured in bps
DsrnTxCapacity string `json:"dsrn_tx_capacity,omitempty"`
// Receive capacity (bandwidth) of this interface measured in bps
DsrnRxCapacity string `json:"dsrn_rx_capacity,omitempty"`
// Snapshot of stats at the start of collection interval (5s for example)
DsrnTrafficstats []EdgeStatusDsResusageDsrNetworkDsrnTrafficstats `json:"dsrn_trafficstats,omitempty"`
}
type EdgeStatusDsResusageDsrNetworkDsrnTrafficstats ¶
type EdgeStatusDsResusageDsrNetworkDsrnTrafficstats struct {
// Overhead data in bytes (non-customer data) sent in this link
DsrnOverheadBytes int32 `json:"dsrn_overhead_bytes,omitempty"`
// Amount of traffic received in this interface in bytes
DsrnRxbytes int32 `json:"dsrn_rxbytes,omitempty"`
// Amount of traffic received in this interface in packets
DsrnRxpkts int32 `json:"dsrn_rxpkts,omitempty"`
// Amount of traffic dropped in this interface in packets
DsrnRxdrop int32 `json:"dsrn_rxdrop,omitempty"`
// Receive side errors in packets
DsrnRxerrs int32 `json:"dsrn_rxerrs,omitempty"`
// Receive side traffic loss in percentage
DsrnRxloss int32 `json:"dsrn_rxloss,omitempty"`
// Recieve side latency measure in milli seconds
DsrnRxlatency int32 `json:"dsrn_rxlatency,omitempty"`
// Recieve side jitter measurement in milli seconds
DsrnRxjitter int32 `json:"dsrn_rxjitter,omitempty"`
// Amount of traffic transmitted in bytes
DsrnTxbytes int32 `json:"dsrn_txbytes,omitempty"`
// Amount of traffic transmitted in packets
DsrnTxpkts int32 `json:"dsrn_txpkts,omitempty"`
// Transmit side packet drops in packets
DsrnTxdrop int32 `json:"dsrn_txdrop,omitempty"`
// Transmit side errors measured in packets
DsrnTxerrs int32 `json:"dsrn_txerrs,omitempty"`
// Transmit side traffic loss in percentage
DsrnTxloss int32 `json:"dsrn_txloss,omitempty"`
// Transmit side latency measure in milli seconds
DsrnTxlatency int32 `json:"dsrn_txlatency,omitempty"`
// Transmit side jitter measure in milli seconds
DsrnTxjitter int32 `json:"dsrn_txjitter,omitempty"`
}
type EdgeStatusDsResusageDsrStorage ¶
type EdgeStatusDsResusageDsrStorage struct {
// Name of the storage device
DsrsDev string `json:"dsrs_dev,omitempty"`
// Mount point of the storage device
DsrsMount string `json:"dsrs_mount,omitempty"`
// File system type.
DsrsFs string `json:"dsrs_fs,omitempty"`
// Total space present in this device in bytes
DsrsTotal int32 `json:"dsrs_total,omitempty"`
// Amount of space free in this device in bytes
DsrsFree int32 `json:"dsrs_free,omitempty"`
}
type EdgeStatusDsUserinfo ¶
type EdgeStatusDsUserinfo struct {
DsuUsers []EdgeStatusDsUserinfoDsuUsers `json:"dsu_users,omitempty"`
}
type EdgeStatusDsUserinfoDsuUsers ¶
type EdgeStatusDsUserinfoDsuUsers struct {
// authenticated user name
DsuUsername string `json:"dsu_username,omitempty"`
// authentication event
DsuEvent string `json:"dsu_event,omitempty"`
DsuEventtime int32 `json:"dsu_eventtime,omitempty"`
// mac address of the supplicant
DsuMacaddress string `json:"dsu_macaddress,omitempty"`
// IPv4 address of the supplicant
DsuIpv4 string `json:"dsu_ipv4,omitempty"`
}
type EdgeStatusRef ¶
type EdgeStatusRef struct {
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
TimePublished time.Time `json:"timePublished,omitempty"`
Status *EdgeStatus `json:"status,omitempty"`
}
type EdgesApiAddEdgeOpts ¶
type EdgesApiGetAllEdgesOpts ¶
type EdgesApiGetEdgeByIdOpts ¶
type EdgesApiService ¶
type EdgesApiService service
func (*EdgesApiService) ActivateEdgeById ¶
func (a *EdgesApiService) ActivateEdgeById(ctx context.Context, body EdgeGenerateActivationCodeInput, id string, localVarOptionals *EdgesApiActivateEdgeByIdOpts) (EdgeActivationCode, *http.Response, error)
func (*EdgesApiService) AddEdge ¶
func (a *EdgesApiService) AddEdge(ctx context.Context, body AddEdgeInput, localVarOptionals *EdgesApiAddEdgeOpts) (Edge, *http.Response, error)
func (*EdgesApiService) AddEdgeInterface ¶
func (a *EdgesApiService) AddEdgeInterface(ctx context.Context, body InterfaceSettings, id string, localVarOptionals *EdgesApiAddEdgeInterfaceOpts) (Edge, *http.Response, error)
func (*EdgesApiService) DeleteEdgeById ¶
func (a *EdgesApiService) DeleteEdgeById(ctx context.Context, id string, localVarOptionals *EdgesApiDeleteEdgeByIdOpts) (Edge, *http.Response, error)
func (*EdgesApiService) DeleteEdgeIfByName ¶
func (a *EdgesApiService) DeleteEdgeIfByName(ctx context.Context, id string, name string, localVarOptionals *EdgesApiDeleteEdgeIfByNameOpts) (Edge, *http.Response, error)
func (*EdgesApiService) GetAllEdges ¶
func (a *EdgesApiService) GetAllEdges(ctx context.Context, localVarOptionals *EdgesApiGetAllEdgesOpts) (EdgesList, *http.Response, error)
func (*EdgesApiService) GetEdgeById ¶
func (a *EdgesApiService) GetEdgeById(ctx context.Context, id string, localVarOptionals *EdgesApiGetEdgeByIdOpts) (Edge, *http.Response, error)
func (*EdgesApiService) GetEdgeIfByName ¶
func (a *EdgesApiService) GetEdgeIfByName(ctx context.Context, id string, name string, localVarOptionals *EdgesApiGetEdgeIfByNameOpts) (InterfaceSettings, *http.Response, error)
func (*EdgesApiService) GetEdgeInterfaceList ¶
func (a *EdgesApiService) GetEdgeInterfaceList(ctx context.Context, id string, localVarOptionals *EdgesApiGetEdgeInterfaceListOpts) ([]InterfaceSettings, *http.Response, error)
func (*EdgesApiService) GetEdgeStatusById ¶
func (a *EdgesApiService) GetEdgeStatusById(ctx context.Context, id string, localVarOptionals *EdgesApiGetEdgeStatusByIdOpts) (EdgeStatusRef, *http.Response, error)
func (*EdgesApiService) UpdateEdgeById ¶
func (a *EdgesApiService) UpdateEdgeById(ctx context.Context, body UpdateEdgeInput, id string, localVarOptionals *EdgesApiUpdateEdgeByIdOpts) (Edge, *http.Response, error)
func (*EdgesApiService) UpdateEdgeIfByName ¶
func (a *EdgesApiService) UpdateEdgeIfByName(ctx context.Context, body InterfaceSettings, id string, name string, localVarOptionals *EdgesApiUpdateEdgeIfByNameOpts) (Edge, *http.Response, error)
type FirewallRule ¶
type FirewallRule struct {
// name of the rule
FwName string `json:"fw_name,omitempty"`
FwMatch *TrafficMatchCriteria `json:"fw_match,omitempty"`
FwAction *PolicyFirewallAction `json:"fw_action,omitempty"`
}
type GatewayDevicesAggregatedDeviceFlowStats ¶
type GatewayDevicesAggregatedDeviceFlowStats struct {
// One object for each device flow found, containing all its metrics
Data []GatewayDevicesAggregatedDeviceFlowStatsData `json:"data,omitempty"`
}
type GatewayDevicesAggregatedDeviceFlowStatsData ¶
type GatewayDevicesAggregatedDeviceFlowStatsData struct {
// IP address of the connected device
SrcIp string `json:"src_ip,omitempty"`
// Source port in the first packet of the flow
SrcPort string `json:"src_port,omitempty"`
// Destination IP in the first packet of the flow
DestIp string `json:"dest_ip,omitempty"`
// Destination port in the first packet of the flow
DestPort string `json:"dest_port,omitempty"`
// Timestamp indicating the first packet arrival for this flow, in RFC 3339 format
FlowFirstPacketTs string `json:"flow_first_packet_ts,omitempty"`
// Comma separated policies that were applied to this flow
ConcatPolicies string `json:"concat_policies,omitempty"`
// Comma separated application ids of this flow
ConcatAppIds string `json:"concat_app_ids,omitempty"`
// Comma separated application display names of this flow
ConcatAppDisplaynames string `json:"concat_app_displaynames,omitempty"`
// Total bytes transmitted in this flow
TxBytes float32 `json:"tx_bytes,omitempty"`
// Total bytes received in this flow
RxBytes float32 `json:"rx_bytes,omitempty"`
// Name of the interface through which first packet of this flow was received.
InterfaceRx string `json:"interface_rx,omitempty"`
// Name of the interface through which first packet of this flow was sent out.
InterfaceTx string `json:"interface_tx,omitempty"`
// The overlay ip of the remote peer to which first packet of the flow was sent out.
OverlayIpTx string `json:"overlay_ip_tx,omitempty"`
// Name of the link used by the flow
LinkName string `json:"link_name,omitempty"`
// The scheduler queue assigned to this flow
SchedulerQueue string `json:"scheduler_queue,omitempty"`
// Average application latency measured in milliseconds
AvgAppLatency float32 `json:"avg_app_latency,omitempty"`
// The value of the protocol number in the IP packet header
ProtocolNumber float32 `json:"protocol_number,omitempty"`
// Timestamp indicating the last packet arrival for this flow, in RFC 3339 format
FlowLastPacketTs string `json:"flow_last_packet_ts,omitempty"`
// Destination URLs of this flow
DestUrls []string `json:"dest_urls,omitempty"`
// Comma separated names of the remote peers to which packets of the flow were sent out.
ConcatPeers string `json:"concat_peers,omitempty"`
// VPN NAT IPs used by this flow
VnatIps []string `json:"vnat_ips,omitempty"`
}
type GatewayDevicesAggregatedDeviceStats ¶
type GatewayDevicesAggregatedDeviceStats struct {
// One object for each device found, containing all its metrics
Data []GatewayDevicesAggregatedDeviceStatsData `json:"data,omitempty"`
}
type GatewayDevicesAggregatedDeviceStatsData ¶
type GatewayDevicesAggregatedDeviceStatsData struct {
// Name of the connected LAN device
Name string `json:"name,omitempty"`
// Mac address of this device
MacAddr string `json:"mac_addr,omitempty"`
// IP address of the connected device
Ipv4 string `json:"ipv4,omitempty"`
// Total bytes transmitted by this device
TxBytes float32 `json:"tx_bytes,omitempty"`
// Total bytes received by this device
RxBytes float32 `json:"rx_bytes,omitempty"`
// Total packets transmitted by this device
TxPackets float32 `json:"tx_packets,omitempty"`
// Total packets received by this device
RxPackets float32 `json:"rx_packets,omitempty"`
// VPN NAT IPs used by this device
VnatIps []string `json:"vnat_ips,omitempty"`
// Number of flows for this device
FlowsNumber float32 `json:"flows_number,omitempty"`
}
type GatewayInterfacesLatestStats ¶
type GatewayInterfacesLatestStats struct {
// One object for each interface found, containing all its metrics
Data []GatewayInterfacesLatestStatsData `json:"data,omitempty"`
}
type GatewayInterfacesLatestStatsCellularStats ¶
type GatewayInterfacesLatestStatsCellularStats struct {
// https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity
Imei string `json:"imei,omitempty"`
// https://en.wikipedia.org/wiki/Cell_Global_Identity
CellId int32 `json:"cell_id,omitempty"`
// https://en.wikipedia.org/wiki/SIM_card
Iccid string `json:"iccid,omitempty"`
// Signal quality
SignalQuality int32 `json:"signal_quality,omitempty"`
// https://en.wikipedia.org/wiki/Access_Point_Name
Apn string `json:"apn,omitempty"`
}
Cellular interface specific stats
type GatewayInterfacesLatestStatsData ¶
type GatewayInterfacesLatestStatsData struct {
// Amount of traffic received in this interface in bytes
BytesRx int32 `json:"bytes_rx,omitempty"`
// Amount of traffic transmitted in bytes
BytesTx int32 `json:"bytes_tx,omitempty"`
// IP address of the interface along with netmask
CidrIp string `json:"cidr_ip,omitempty"`
// Name of the ISP to which the public ip belongs
Isp string `json:"isp,omitempty"`
// Amount of traffic received in this interface in packets
PacketsRx int32 `json:"packets_rx,omitempty"`
// Amount of traffic transmitted in packets
PacketsTx int32 `json:"packets_tx,omitempty"`
// IP of local interface forwarding the traffic
PublicIp string `json:"public_ip,omitempty"`
// Indicates whether this interface is up or down
State string `json:"state,omitempty"`
// Type of the interface
Type_ string `json:"type,omitempty"`
WifiStats *GatewayInterfacesLatestStatsWifiStats `json:"wifi_stats,omitempty"`
CellularStats *GatewayInterfacesLatestStatsCellularStats `json:"cellular_stats,omitempty"`
}
type GatewayInterfacesLatestStatsWifiStats ¶
type GatewayInterfacesLatestStatsWifiStats struct {
// WiFi SSID connected to
Ssid string `json:"ssid,omitempty"`
// Frequency of the WiFi SSID connected to
Frequency int32 `json:"frequency,omitempty"`
// WiFi signal strength in dBm (decibel milliwatts)
SignalStrength int32 `json:"signal_strength,omitempty"`
// RX rate in kbps
RxRate int32 `json:"rx_rate,omitempty"`
// TX rate in kbps
TxRate int32 `json:"tx_rate,omitempty"`
// Channel number
ChannelNumber int32 `json:"channel_number,omitempty"`
// Total errors encountered
ErrorsCount int32 `json:"errors_count,omitempty"`
}
Managed wifi (client) mode connection stats
type GatewayPathsLatestStats ¶
type GatewayPathsLatestStats struct {
// One object for each path found, containing all its metrics
Data []GatewayPathsLatestStatsData `json:"data,omitempty"`
}
type GatewayPathsLatestStatsData ¶
type GatewayPathsLatestStatsData struct {
// Traffic received in this path in bytes
BytesRx int32 `json:"bytes_rx,omitempty"`
// Traffic sent in this path in bytes
BytesTx int32 `json:"bytes_tx,omitempty"`
// Jitter measure in this path
Jitter int32 `json:"jitter,omitempty"`
// Latency measure in this path
Latency int32 `json:"latency,omitempty"`
// Link through which traffic is sent
Link string `json:"link,omitempty"`
// IP of local interface forwarding the traffic
LocalIp string `json:"local_ip,omitempty"`
// Receive side loss in percentage
LossRx int32 `json:"loss_rx,omitempty"`
// Transmit side loss in percentage
LossTx int32 `json:"loss_tx,omitempty"`
// Overlay IP of the peer
OverlayIp string `json:"overlay_ip,omitempty"`
// Name of the edge forwarding the traffic
OverlayIpName string `json:"overlay_ip_name,omitempty"`
// Traffic received in this path in packets
PacketsRx int32 `json:"packets_rx,omitempty"`
// Traffic sent in this link in packets
PacketsTx int32 `json:"packets_tx,omitempty"`
}
type GatewayRoutesLatestStats ¶
type GatewayRoutesLatestStats struct {
// One object for each route found, containing its metrics
Data []GatewayRoutesLatestStatsData `json:"data,omitempty"`
}
type GatewayRoutesLatestStatsData ¶
type GatewayRoutesLatestStatsData struct {
// Gateway IP
GatewayIp string `json:"gateway_ip,omitempty"`
// Gateway name
GatewayName string `json:"gateway_name,omitempty"`
// Interface name
InterfaceName string `json:"interface_name,omitempty"`
// Route metric
Metric int32 `json:"metric,omitempty"`
// Network address/mask
Netmask string `json:"netmask,omitempty"`
// Route type
RouteType string `json:"route_type,omitempty"`
}
type GatewaySysLoadStats ¶
type GatewaySysLoadStats struct {
Data *GatewaySysLoadStatsData `json:"data,omitempty"`
}
type GatewaySysLoadStatsData ¶
type GatewaySysLoadStatsData struct {
// Aggregated average of system load samples taken in a 1 minute rolling window
AvgLoad1min []float32 `json:"avg_load_1min,omitempty"`
// Aggregated average of system load samples taken in a 5 minute rolling window
AvgLoad5min []float32 `json:"avg_load_5min,omitempty"`
// Aggregated average of system load samples taken in a 15 minute rolling window
AvgLoad15min []float32 `json:"avg_load_15min,omitempty"`
}
type GatewaySysLteSignalStats ¶
type GatewaySysLteSignalStats struct {
Data *GatewaySysLteSignalStatsData `json:"data,omitempty"`
}
type GatewaySysMemoryStats ¶
type GatewaySysMemoryStats struct {
Data *GatewaySysMemoryStatsData `json:"data,omitempty"`
}
type GatewaySysMemoryStatsData ¶
type GatewaySysMemoryStatsData struct {
// Aggregated average of buffered memory in the system in KB
AvgBuffered []float32 `json:"avg_buffered,omitempty"`
// Aggregated average of free memory in the system in KB
AvgFree []float32 `json:"avg_free,omitempty"`
// Aggregated average of total memory available in the system in KB
AvgTotal []float32 `json:"avg_total,omitempty"`
}
type GatewaySysUptimeStats ¶
type GatewaySysUptimeStats struct {
Data *GatewaySysUptimeStatsData `json:"data,omitempty"`
}
type GatewaySysUptimeStatsData ¶
type GatewaySysUptimeStatsData struct {
// Aggregated average of system uptime
AvgUptime []float32 `json:"avg_uptime,omitempty"`
}
type GatewaySysWiFiStrengthStats ¶
type GatewaySysWiFiStrengthStats struct {
Data *GatewaySysWiFiStrengthStatsData `json:"data,omitempty"`
}
type GatewaySysWiFiStrengthStatsData ¶
type GatewaySysWiFiStrengthStatsData struct {
// Channel number
ChannelNum []int32 `json:"channel_num,omitempty"`
// Total errors encountered
Errors []int32 `json:"errors,omitempty"`
// RX rate in kbps
Rxrate []int32 `json:"rxrate,omitempty"`
// TX rate in kbps
Txrate []int32 `json:"txrate,omitempty"`
// WiFi SSIDs connected to
Ssids [][]string `json:"ssids,omitempty"`
// Frequency of the WiFi SSID connected to
WifiFrequency []int32 `json:"wifi_frequency,omitempty"`
// WiFi signal strength in dBm (decibel milliwatts)
WifiSignalStrength []int32 `json:"wifi_signal_strength,omitempty"`
}
type GatewayWanAggregatedPathsAndLinksStats ¶
type GatewayWanAggregatedPathsAndLinksStats struct {
// One object for each path and link found, containing all its metrics
Data []GatewayWanAggregatedPathsAndLinksStatsData `json:"data,omitempty"`
}
type GatewayWanAggregatedPathsAndLinksStatsData ¶
type GatewayWanAggregatedPathsAndLinksStatsData struct {
// Link through which traffic is sent
Link string `json:"link,omitempty"`
// Name of the ISP to which the public ip belongs
Isp string `json:"isp,omitempty"`
// IP of local interface forwarding the traffic
Ip string `json:"ip,omitempty"`
// Overlay IP of the peer
OverlayIp string `json:"overlay_ip,omitempty"`
// Name of the edge forwarding the traffic for paths, 'Link' for links
Peer string `json:"peer,omitempty"`
// Receive capacity(bandwidth) of this link measured in bps
LatestRxBandwidth float32 `json:"latest_rx_bandwidth,omitempty"`
// Transmission capacity(bandwidth) of this link measured in bps
LatestTxBandwidth float32 `json:"latest_tx_bandwidth,omitempty"`
// Average number of bytes transmitted per sample interval
AvgTxThroughput float32 `json:"avg_tx_throughput,omitempty"`
// Max number of bytes transmitted in a sample interval
MaxTxThroughput float32 `json:"max_tx_throughput,omitempty"`
// Average number of bytes received per sample interval
AvgRxThroughput float32 `json:"avg_rx_throughput,omitempty"`
// Max number of bytes received in a sample interval
MaxRxThroughput float32 `json:"max_rx_throughput,omitempty"`
// Average latency measured in milli seconds
AvgLatency float32 `json:"avg_latency,omitempty"`
// Max latency measured in milli seconds
MaxLatency float32 `json:"max_latency,omitempty"`
// Average jitter measurement in milli seconds
AvgJitter float32 `json:"avg_jitter,omitempty"`
// Max jitter measurement in milli seconds
MaxJitter float32 `json:"max_jitter,omitempty"`
// Average traffic loss in percentage
AvgLoss float32 `json:"avg_loss,omitempty"`
// Max traffic loss in percentage
MaxLoss float32 `json:"max_loss,omitempty"`
// Traffic received in this path/link in bytes
TotalRxBytes float32 `json:"total_rx_bytes,omitempty"`
// Traffic transmitted in this path/link in bytes
TotalTxBytes float32 `json:"total_tx_bytes,omitempty"`
// Traffic received in this path/link in packets
TotalRxPackets float32 `json:"total_rx_packets,omitempty"`
// Traffic transmitted in this path/link in packets
TotalTxPackets float32 `json:"total_tx_packets,omitempty"`
}
type GatewayWanPathsAndLinksStats ¶
type GatewayWanPathsAndLinksStats struct {
Data *AllOfGatewayWanPathsAndLinksStatsData `json:"data,omitempty"`
}
type GenericSwaggerError ¶
type GenericSwaggerError struct {
// contains filtered or unexported fields
}
GenericSwaggerError Provides access to the body, error and model on returned errors.
func (GenericSwaggerError) Body ¶
func (e GenericSwaggerError) Body() []byte
Body returns the raw bytes of the response
func (GenericSwaggerError) Error ¶
func (e GenericSwaggerError) Error() string
Error returns non-empty string if there was an error.
func (GenericSwaggerError) Model ¶
func (e GenericSwaggerError) Model() interface{}
Model returns the unpacked model of the error
type InboundNatRule ¶
type InboundNatRule struct {
Name string `json:"name,omitempty"`
PublicIp string `json:"publicIp"`
UpLinkIfName string `json:"upLinkIfName"`
LanIp string `json:"lanIp"`
BiDirectional bool `json:"biDirectional,omitempty"`
LanPort int32 `json:"lanPort,omitempty"`
PublicPort int32 `json:"publicPort,omitempty"`
}
Object for representing a 1:1 NAT or a port forwarding rule.
type InfiotErrorResponse ¶
type InfiotErrorResponse struct {
// Error message
Message string `json:"message,omitempty"`
}
Infiot standard error response
type InterfaceSettings ¶
type InterfaceSettings struct {
Var8021xMab bool `json:"8021xMab,omitempty"`
Radius []RadiusSetting `json:"radius,omitempty"`
Mode string `json:"mode,omitempty"`
AllowedVlans []int32 `json:"allowedVlans,omitempty"`
Zone string `json:"zone,omitempty"`
BridgeMembers []string `json:"bridgeMembers,omitempty"`
WifiProps *WiFiInterfaceSetting `json:"wifiProps,omitempty"`
LteProps *LteInterfaceSetting `json:"lteProps,omitempty"`
Name string `json:"name,omitempty"`
Type_ string `json:"type,omitempty"`
MacAddr string `json:"macAddr,omitempty"`
Mtu int32 `json:"mtu,omitempty"`
MtuDiscovery string `json:"mtuDiscovery,omitempty"`
IsDisabled bool `json:"isDisabled,omitempty"`
Vlan int32 `json:"vlan,omitempty"`
EnableNat bool `json:"enableNat,omitempty"`
ProxyArpSettings []ProxyArpSetting `json:"proxyArpSettings,omitempty"`
OverlaySetting *OverlaySetting `json:"overlaySetting,omitempty"`
Vrrp *Vrrp `json:"vrrp,omitempty"`
DhcpServerSetting *DhcpServerSettings `json:"dhcpServerSetting,omitempty"`
DhcpRelayServerSetting *[]string `json:"dhcpRelayServerSetting,omitempty"`
// advertise the interface subnet
DoAdvertise bool `json:"doAdvertise,omitempty"`
Addresses []InterfaceSettingsAddresses `json:"addresses,omitempty"`
}
type InterfaceSettingsAddresses ¶
type InterfaceSettingsAddresses struct {
AddressAssignment string `json:"addressAssignment,omitempty"`
AddressFamily string `json:"addressFamily,omitempty"`
Address string `json:"address,omitempty"`
Mask string `json:"mask,omitempty"`
Gateway string `json:"gateway,omitempty"`
DnsPrimary string `json:"dnsPrimary,omitempty"`
DnsSecondary string `json:"dnsSecondary,omitempty"`
}
type L4Protocols ¶
type L4Protocols string
const ( TCP_L4Protocols L4Protocols = "tcp" UDP_L4Protocols L4Protocols = "udp" ICMP_L4Protocols L4Protocols = "icmp" GRE_L4Protocols L4Protocols = "gre" )
List of L4Protocols
type LteInterfaceSetting ¶
type ManagedDevice ¶
type ManagedDevice struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
Id string `json:"id,omitempty"`
Name string `json:"name,omitempty"`
Location *EdgeRef `json:"location,omitempty"`
MdDevicePolicy string `json:"md_device_policy,omitempty"`
Props *ManagedDeviceProps `json:"props,omitempty"`
}
type ManagedDeviceList ¶
type ManagedDeviceList struct {
FirstPage bool `json:"firstPage,omitempty"`
LastPage bool `json:"lastPage,omitempty"`
StartCursor string `json:"startCursor,omitempty"`
EndCursor string `json:"endCursor,omitempty"`
Data []ManagedDevice `json:"data,omitempty"`
}
type ManagedDevicePolicy ¶
type ManagedDevicePolicy struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
Id string `json:"id,omitempty"`
MdplcName string `json:"mdplc_name,omitempty"`
MdplcType string `json:"mdplc_type,omitempty"`
MdplcDeviceServices []ManagedDevicePolicyService `json:"mdplc_device_services,omitempty"`
MdplcUserGroups []UserGroupRef `json:"mdplc_user_groups,omitempty"`
}
type ManagedDevicePolicyList ¶
type ManagedDevicePolicyList struct {
FirstPage bool `json:"firstPage,omitempty"`
LastPage bool `json:"lastPage,omitempty"`
StartCursor string `json:"startCursor,omitempty"`
EndCursor string `json:"endCursor,omitempty"`
Data []ManagedDevicePolicy `json:"data,omitempty"`
}
type ManagedDeviceProps ¶
type ManagedDeviceProps struct {
MdSchemaver int32 `json:"md_schemaver,omitempty"`
MdConfigVersion string `json:"md_config_version,omitempty"`
MdDescription string `json:"md_description,omitempty"`
MdLabels []string `json:"md_labels,omitempty"`
MdVendor string `json:"md_vendor,omitempty"`
MdModel string `json:"md_model,omitempty"`
MdSerialNumber string `json:"md_serial_number,omitempty"`
MdMacAddress string `json:"md_mac_address,omitempty"`
MdIp string `json:"md_ip,omitempty"`
MdProxyFqdn string `json:"md_proxy_fqdn,omitempty"`
MdServices []ManagedDeviceService `json:"md_services,omitempty"`
MdPort string `json:"md_port,omitempty"`
}
type ManagedDeviceService ¶
type MonitoringApiService ¶
type MonitoringApiService service
func (*MonitoringApiService) GetGatewayAggregatedDeviceFlowStatsByID ¶
func (a *MonitoringApiService) GetGatewayAggregatedDeviceFlowStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, ip string, localVarOptionals *MonitoringApiGetGatewayAggregatedDeviceFlowStatsByIDOpts) (GatewayDevicesAggregatedDeviceFlowStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayAggregatedDeviceStatsByID ¶
func (a *MonitoringApiService) GetGatewayAggregatedDeviceStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayAggregatedDeviceStatsByIDOpts) (GatewayDevicesAggregatedDeviceStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayAggregatedPathAndLinkStatsByID ¶
func (a *MonitoringApiService) GetGatewayAggregatedPathAndLinkStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayAggregatedPathAndLinkStatsByIDOpts) (GatewayWanAggregatedPathsAndLinksStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayLTESignalStatsByID ¶
func (a *MonitoringApiService) GetGatewayLTESignalStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayLTESignalStatsByIDOpts) (GatewaySysLteSignalStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayLatestInterfaceStatsByID ¶
func (a *MonitoringApiService) GetGatewayLatestInterfaceStatsByID(ctx context.Context, id string, localVarOptionals *MonitoringApiGetGatewayLatestInterfaceStatsByIDOpts) (GatewayInterfacesLatestStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayLatestPathStatsByID ¶
func (a *MonitoringApiService) GetGatewayLatestPathStatsByID(ctx context.Context, id string, localVarOptionals *MonitoringApiGetGatewayLatestPathStatsByIDOpts) (GatewayPathsLatestStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayLatestRouteStatsByID ¶
func (a *MonitoringApiService) GetGatewayLatestRouteStatsByID(ctx context.Context, id string, localVarOptionals *MonitoringApiGetGatewayLatestRouteStatsByIDOpts) (GatewayRoutesLatestStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayLoadStatsByID ¶
func (a *MonitoringApiService) GetGatewayLoadStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayLoadStatsByIDOpts) (GatewaySysLoadStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayMemoryStatsByID ¶
func (a *MonitoringApiService) GetGatewayMemoryStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayMemoryStatsByIDOpts) (GatewaySysMemoryStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayPathAndLinkStatsByID ¶
func (a *MonitoringApiService) GetGatewayPathAndLinkStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, metric string, localVarOptionals *MonitoringApiGetGatewayPathAndLinkStatsByIDOpts) (GatewayWanPathsAndLinksStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayUptimeStatsByID ¶
func (a *MonitoringApiService) GetGatewayUptimeStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayUptimeStatsByIDOpts) (GatewaySysUptimeStats, *http.Response, error)
func (*MonitoringApiService) GetGatewayWiFiStrengthStatsByID ¶
func (a *MonitoringApiService) GetGatewayWiFiStrengthStatsByID(ctx context.Context, id string, startDatetime time.Time, endDatetime time.Time, localVarOptionals *MonitoringApiGetGatewayWiFiStrengthStatsByIDOpts) (GatewaySysWiFiStrengthStats, *http.Response, error)
type MqttgcpConfiguration ¶
type MqttgcpConfiguration struct {
Name string `json:"name,omitempty"`
DeviceId string `json:"deviceId,omitempty"`
ProjectId string `json:"projectId,omitempty"`
Region string `json:"region,omitempty"`
Registry string `json:"registry,omitempty"`
Topic []MqttgcpConfigurationTopic `json:"topic,omitempty"`
}
type NetflowCollector ¶
type NetflowExporterSetting ¶
type NetflowExporterSetting struct {
NfExportInterval int32 `json:"nf_export_interval,omitempty"`
// TODO The `omitempty` below has been removed manually. We need to find a way to
// generate it like this from swagger
NfCollectorSettings []NetflowCollector `json:"nf_collector_settings"`
}
type ObjectProps ¶
type ObjectProps struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
}
type OverlaySetting ¶
type OverlaySetting struct {
Tag string `json:"tag,omitempty"`
IsBackup bool `json:"isBackup,omitempty"`
IsMetered bool `json:"isMetered,omitempty"`
DataUsageLimit *DataUsageLimitSetting `json:"dataUsageLimit,omitempty"`
TxBwKbps int32 `json:"txBwKbps,omitempty"`
RxBwKbps int32 `json:"rxBwKbps,omitempty"`
BwMeasurementMode string `json:"bwMeasurementMode,omitempty"`
DoCopyTos bool `json:"doCopyTos,omitempty"`
}
type PagedResponse ¶
type PoliciesApiService ¶
type PoliciesApiService service
func (*PoliciesApiService) AddDenySourceIPRuleToPolicy ¶
func (a *PoliciesApiService) AddDenySourceIPRuleToPolicy(ctx context.Context, body AddPolicyFirewallRuleInput, id string, localVarOptionals *PoliciesApiAddDenySourceIPRuleToPolicyOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) AddPolicy ¶
func (a *PoliciesApiService) AddPolicy(ctx context.Context, body AddPolicyInput, localVarOptionals *PoliciesApiAddPolicyOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) AddQoSSourceIPRuleToPolicy ¶
func (a *PoliciesApiService) AddQoSSourceIPRuleToPolicy(ctx context.Context, body AddPolicyQoSRuleInput, id string, localVarOptionals *PoliciesApiAddQoSSourceIPRuleToPolicyOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) DeleteDenySourceIPRuleFromPolicy ¶
func (a *PoliciesApiService) DeleteDenySourceIPRuleFromPolicy(ctx context.Context, id string, ip string, localVarOptionals *PoliciesApiDeleteDenySourceIPRuleFromPolicyOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) DeletePolicyById ¶
func (a *PoliciesApiService) DeletePolicyById(ctx context.Context, id string, localVarOptionals *PoliciesApiDeletePolicyByIdOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) DeleteQoSSourceIPRuleFromPolicy ¶
func (a *PoliciesApiService) DeleteQoSSourceIPRuleFromPolicy(ctx context.Context, id string, ip string, localVarOptionals *PoliciesApiDeleteQoSSourceIPRuleFromPolicyOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) GetAllPolicies ¶
func (a *PoliciesApiService) GetAllPolicies(ctx context.Context, localVarOptionals *PoliciesApiGetAllPoliciesOpts) ([]Policy, *http.Response, error)
func (*PoliciesApiService) GetPolicyById ¶
func (a *PoliciesApiService) GetPolicyById(ctx context.Context, id string, localVarOptionals *PoliciesApiGetPolicyByIdOpts) (Policy, *http.Response, error)
func (*PoliciesApiService) UpdatePolicyById ¶
func (a *PoliciesApiService) UpdatePolicyById(ctx context.Context, body Policy, id string, localVarOptionals *PoliciesApiUpdatePolicyByIdOpts) (Policy, *http.Response, error)
type Policy ¶
type Policy struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
Id string `json:"id,omitempty"`
// The name of the policy
Name string `json:"name,omitempty"`
Type_ *PolicyType `json:"type,omitempty"`
AssignedEdges []string `json:"assignedEdges,omitempty"`
Hubs []EdgeRef `json:"hubs,omitempty"`
Config *PolicyConfig `json:"config,omitempty"`
}
type PolicyClassOfService ¶
type PolicyClassOfService struct {
// the cos class e.g. Voice, Broadcast etc
CosTrafficClass string `json:"cos_traffic_class,omitempty"`
CosMinGuaranteeBwPercent int32 `json:"cos_min_guarantee_bw_percent,omitempty"`
// latency SLA for the cos class
CosLatencyMs int32 `json:"cos_latency_ms,omitempty"`
// jitter SLA for the cos class
CosJitterMs int32 `json:"cos_jitter_ms,omitempty"`
CosLossPercent int32 `json:"cos_loss_percent,omitempty"`
// choose to use a low latency queue (llq)
CosLlq bool `json:"cos_llq,omitempty"`
// priority level
CosPriority string `json:"cos_priority,omitempty"`
// control specific traffic types to pass through if the only\\ available link is the metered/standby link
CosLastResort bool `json:"cos_last_resort,omitempty"`
}
type PolicyConfig ¶
type PolicyConfig struct {
PcfgSchemaver int32 `json:"pcfg_schemaver,omitempty"`
PcfgSchemaverMinor int32 `json:"pcfg_schemaver_minor,omitempty"`
PcfgQosPolicies []PolicyQoS `json:"pcfg_qos_policies,omitempty"`
PcfgCosTable []PolicyClassOfService `json:"pcfg_cos_table,omitempty"`
PcfgGeneralSettings *PolicyConfigPcfgGeneralSettings `json:"pcfg_general_settings,omitempty"`
PcfgUrlFilter *PolicyConfigPcfgUrlFilter `json:"pcfg_url_filter,omitempty"`
PcfgFirewall *PolicyConfigPcfgFirewall `json:"pcfg_firewall,omitempty"`
}
type PolicyConfigPcfgFirewall ¶
type PolicyConfigPcfgFirewall struct {
// Firewall feature enable or disable
PcfgFirewallEnabled bool `json:"pcfg_firewall_enabled,omitempty"`
// Stateful Firewall enable or disable
PcfgFwStatefulEnabled bool `json:"pcfg_fw_stateful_enabled,omitempty"`
PcfgFwLogging *PolicyConfigPcfgFirewallPcfgFwLogging `json:"pcfg_fw_logging,omitempty"`
// List of firewall policies
PcfgFwPolicies []FirewallRule `json:"pcfg_fw_policies,omitempty"`
}
type PolicyConfigPcfgFirewallPcfgFwLogging ¶
type PolicyConfigPcfgFirewallPcfgFwLogging struct {
// Enable or disable the firewall logging
PcfgFwLogEnabled bool `json:"pcfg_fw_log_enabled,omitempty"`
// Logging the flows that got denied
PcfgFwDenyLogEnabled bool `json:"pcfg_fw_deny_log_enabled,omitempty"`
// Logging the flows that got allowed
PcfgFwAllowLogEnabled bool `json:"pcfg_fw_allow_log_enabled,omitempty"`
}
Configure the firewall logging
type PolicyConfigPcfgGeneralSettings ¶
type PolicyConfigPcfgGeneralSettings struct {
PcfgSnmp []SnmpSetting `json:"pcfg_snmp,omitempty"`
PcfgSnmpTraps []SnmpTrapSetting `json:"pcfg_snmp_traps,omitempty"`
PcfgSyslogEnabled bool `json:"pcfg_syslog_enabled,omitempty"`
PcfgSyslogServers []SyslogServer `json:"pcfg_syslog_servers,omitempty"`
PcfgNetflow *PolicyConfigPcfgGeneralSettingsPcfgNetflow `json:"pcfg_netflow,omitempty"`
}
type PolicyConfigPcfgGeneralSettingsPcfgNetflow ¶
type PolicyConfigPcfgGeneralSettingsPcfgNetflow struct {
PcfgNfEnabled bool `json:"pcfg_nf_enabled,omitempty"`
PcfgNfExporterSettings *NetflowExporterSetting `json:"pcfg_nf_exporter_settings,omitempty"`
}
type PolicyConfigPcfgUrlFilter ¶
type PolicyConfigPcfgUrlFilter struct {
PcfgUfEnabled bool `json:"pcfg_uf_enabled,omitempty"`
// List of URLs to be blocked irrespective of category/reputation
PcfgUfBlocklist []string `json:"pcfg_uf_blocklist,omitempty"`
// List of URLs to be allowed irrespective of category/reputation
PcfgUfAllowlist []string `json:"pcfg_uf_allowlist,omitempty"`
PcfgUfReputationThreshold *WebReputation `json:"pcfg_uf_reputation_threshold,omitempty"`
// List of categories to block (Infiot category specifier)
PcfgUfBlockedCategories []int32 `json:"pcfg_uf_blocked_categories,omitempty"`
}
type PolicyFirewallAction ¶
type PolicyLinkSteeringAction ¶
type PolicyLinkSteeringAction struct {
LnksLinkSteeringMode string `json:"lnks_link_steering_mode,omitempty"`
LnksVia *PolicyLinkSteeringActionLnksVia `json:"lnks_via,omitempty"`
// the interface to use for steering
LnksInterface string `json:"lnks_interface,omitempty"`
// link steering algorithm to use
LnksAlgo string `json:"lnks_algo,omitempty"`
}
type PolicyLinkSteeringActionLnksVia ¶
type PolicyLinkSteeringActionLnksVia struct {
Active []PolicyLinkSteeringActionLnksViaActive `json:"active,omitempty"`
Backup []PolicyLinkSteeringActionLnksViaBackup `json:"backup,omitempty"`
}
type PolicyMatchRule ¶
type PolicyMatchRule struct {
// name of the match rule
CmapName string `json:"cmap_name,omitempty"`
// match type can be all (logical AND) or any (logical OR)
CmapMatchType string `json:"cmap_match_type,omitempty"`
CmapMatchCriteria *TrafficMatchCriteria `json:"cmap_match_criteria,omitempty"`
}
type PolicyPbrAction ¶
type PolicyQoS ¶
type PolicyQoS struct {
QosMatch *PolicyMatchRule `json:"qos_match,omitempty"`
QosAction *PolicyQoSAction `json:"qos_action,omitempty"`
}
type PolicyQoSAction ¶
type PolicyQoSAction struct {
SchedAction *PolicySchedulerAction `json:"sched_action,omitempty"`
PbrAction *PolicyPbrAction `json:"pbr_action,omitempty"`
TrafficAction *PolicyTrafficAction `json:"traffic_action,omitempty"`
LinkSteeringAction *PolicyLinkSteeringAction `json:"link_steering_action,omitempty"`
FirewallAction *PolicyFirewallAction `json:"firewall_action,omitempty"`
}
type PolicySchedulerAction ¶
type PolicySchedulerAction struct {
// toggle rate limiting
SchRateLimitEnable bool `json:"sch_rate_limit_enable,omitempty"`
// kbps value of the uplink capacity to be used
SchTxRateLimitKbps int32 `json:"sch_tx_rate_limit_kbps,omitempty"`
// kbps value of the downlink capacity to be used
SchRxRateLimitKbps int32 `json:"sch_rx_rate_limit_kbps,omitempty"`
// choose between policing and shaping for rate limiting
SchTxRateLimitType string `json:"sch_tx_rate_limit_type,omitempty"`
// drop strategy for policing and when shaping queue is full
SchDropAlgo string `json:"sch_drop_algo,omitempty"`
// capacity of the shaping queue
SchQueueLimitBytes int32 `json:"sch_queue_limit_bytes,omitempty"`
}
type PolicyTrafficAction ¶
type PolicyTrafficAction struct {
Priority *PolicyTrafficPriority `json:"priority,omitempty"`
// Classification of traffic
Class string `json:"class,omitempty"`
}
type PolicyTrafficPriority ¶
type PolicyTrafficPriority string
PolicyTrafficPriority : Priority of the traffic
const ( HIGH_PolicyTrafficPriority PolicyTrafficPriority = "high" NORMAL_PolicyTrafficPriority PolicyTrafficPriority = "normal" LOW_PolicyTrafficPriority PolicyTrafficPriority = "low" DROP_PolicyTrafficPriority PolicyTrafficPriority = "drop" DROP_WITH_LOG_PolicyTrafficPriority PolicyTrafficPriority = "drop_with_log" AUTO_PolicyTrafficPriority PolicyTrafficPriority = "auto" )
List of PolicyTrafficPriority
type PolicyType ¶
type PolicyType string
PolicyType : The type of the policy
const ( GATEWAY_PolicyType PolicyType = "gateway" CLIENT_PolicyType PolicyType = "client" )
List of PolicyType
type ProxyArpSetting ¶
type ProxyArpSetting struct {
Ipv4Address string `json:"ipv4Address"`
Ipv4Mask string `json:"ipv4Mask"`
Ipv4Gateway string `json:"ipv4Gateway,omitempty"`
LanInterfaceName string `json:"lanInterfaceName,omitempty"`
}
describes one proxy arp entry
type RadiusSetting ¶
type RadiusSetting struct {
Name string `json:"name,omitempty"`
Ipv4 string `json:"ipv4,omitempty"`
Port int32 `json:"port,omitempty"`
AccountingPort int32 `json:"accountingPort,omitempty"`
Secret string `json:"secret,omitempty"`
ClientIpv4 string `json:"clientIpv4,omitempty"`
ClientInterfaceName string `json:"clientInterfaceName,omitempty"`
}
type SnmpSetting ¶
type SnmpTrapSetting ¶
type StaticRoute ¶
type SyslogServer ¶
type SyslogServer struct {
ServerIp string `json:"server_ip,omitempty"`
SourceInterface string `json:"source_interface,omitempty"`
Protocol string `json:"protocol,omitempty"`
Port int32 `json:"port,omitempty"`
Facility string `json:"facility,omitempty"`
Tag string `json:"tag,omitempty"`
// application list whose logs are expected.eg.urlfilter, all
Applications []string `json:"applications,omitempty"`
// output format type
Format string `json:"format,omitempty"`
}
type Tenant ¶
type Tenant struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
Id string `json:"id,omitempty"`
// The display name of the tenant.
Name string `json:"name"`
// One or more domain names that this tenant uses in the URL
DomainNames []string `json:"domainNames"`
// Additional notes about the tenant.
Description string `json:"description,omitempty"`
// Tenant's disabled status. If a tenant disabled no operations can be performed to it.
IsDisabled bool `json:"isDisabled,omitempty"`
TenantTypeInput *TenantTypeInput `json:"tenantTypeInput,omitempty"`
TenantType string `json:"tenantType,omitempty"`
ParentId string `json:"parentId,omitempty"`
// A list of all ancestor tenants that have access to this one. The list is sorted with the most immidiate ancesort, the parent tenant, being the first and the most distant, the sys tenant, being the last.
AncestorTenants []string `json:"ancestorTenants,omitempty"`
// The REST Endpoint for this tenant, use this URL when requesting access to resources under this tenant.
RestApiEndPoint string `json:"restApiEndPoint,omitempty"`
}
type TenantTypeInput ¶
type TenantTypeInput string
TenantTypeInput : Tenant type of an already created tenant can't be modified, ignored in put request body
const ( MASTER_MSP_TenantTypeInput TenantTypeInput = "Master MSP" MSP_TenantTypeInput TenantTypeInput = "MSP" ORGANIZATION_TenantTypeInput TenantTypeInput = "Organization" )
List of TenantTypeInput
type TenantsApiAddTenantOpts ¶
type TenantsApiService ¶
type TenantsApiService service
func (*TenantsApiService) AddTenant ¶
func (a *TenantsApiService) AddTenant(ctx context.Context, body Tenant, localVarOptionals *TenantsApiAddTenantOpts) (Tenant, *http.Response, error)
func (*TenantsApiService) DeleteTenantById ¶
func (a *TenantsApiService) DeleteTenantById(ctx context.Context, tenantId string, localVarOptionals *TenantsApiDeleteTenantByIdOpts) (Tenant, *http.Response, error)
func (*TenantsApiService) GetAllTenants ¶
func (a *TenantsApiService) GetAllTenants(ctx context.Context, localVarOptionals *TenantsApiGetAllTenantsOpts) (TenantsList, *http.Response, error)
func (*TenantsApiService) GetTenantById ¶
func (a *TenantsApiService) GetTenantById(ctx context.Context, tenantId string, localVarOptionals *TenantsApiGetTenantByIdOpts) (Tenant, *http.Response, error)
func (*TenantsApiService) UpdateTenantById ¶
func (a *TenantsApiService) UpdateTenantById(ctx context.Context, body Tenant, tenantId string, localVarOptionals *TenantsApiUpdateTenantByIdOpts) (Tenant, *http.Response, error)
type TenantsList ¶
type TimeSeriesProps ¶
type TrafficMatchCriteria ¶
type TrafficMatchCriteria struct {
// source zone to match
MtchSrcZone string `json:"mtch_src_zone,omitempty"`
// destination zone to match
MtchDestZone string `json:"mtch_dest_zone,omitempty"`
// source ip address to match
MtchSrcIp string `json:"mtch_src_ip,omitempty"`
// source mac address to match
MtchSrcMac string `json:"mtch_src_mac,omitempty"`
// source port range to match
MtchSrcPort string `json:"mtch_src_port,omitempty"`
// source vlan to match
MtchSrcVlan int32 `json:"mtch_src_vlan,omitempty"`
// destination vlan to match
MtchDstVlan int32 `json:"mtch_dst_vlan,omitempty"`
// destination ip address to match
MtchDestIp string `json:"mtch_dest_ip,omitempty"`
// match all internet bound client traffic
MtchDestInternet bool `json:"mtch_dest_internet,omitempty"`
// destination ports to match
MtchDestPort string `json:"mtch_dest_port,omitempty"`
// application id from a list of predefined or user defined applications ids.
MtchAppId []int32 `json:"mtch_app_id,omitempty"`
MtchL4Protocol *L4Protocols `json:"mtch_l4_protocol,omitempty"`
}
type UpdateEdgeInput ¶
type UpdateEdgeInput struct {
// The display name of the edge
Name string `json:"name,omitempty"`
// Additional notes about the edge
Description string `json:"description,omitempty"`
Role *EdgeRole `json:"role,omitempty"`
// Serial number of the edge
Serialnumber string `json:"serialnumber,omitempty"`
// Version of the software manifest assigned to this edge
Swversion string `json:"swversion,omitempty"`
// URL of the software manifest assined to this edge
Swmanifest string `json:"swmanifest,omitempty"`
Psk string `json:"psk,omitempty"`
BgpConfiguration []EdgeBgpConfiguration `json:"bgpConfiguration,omitempty"`
StaticRoutes []StaticRoute `json:"staticRoutes,omitempty"`
AssignedPolicy *PolicyRef `json:"assignedPolicy,omitempty"`
One2OneNatRules []InboundNatRule `json:"one2OneNatRules,omitempty"`
PortForwardingNatRules []InboundNatRule `json:"portForwardingNatRules,omitempty"`
Interfaces *[]InterfaceSettings `json:"interfaces,omitempty"`
ClientConfiguration *ClientConfiguration `json:"clientConfiguration,omitempty"`
}
type User ¶
type User struct {
// Time object record was created in ISO 8601 format. For example 2019-05-08T05:30:30.206Z
DateCreated time.Time `json:"dateCreated,omitempty"`
// Time object record was last modified in ISO 8601 format. For example '2019-05-08T05:30:30.206Z'
DateModified time.Time `json:"dateModified,omitempty"`
CreatedBy *UserRef `json:"createdBy,omitempty"`
ModifiedBy *UserRef `json:"modifiedBy,omitempty"`
// A unique ID assigned to the user.
Id string `json:"id,omitempty"`
// Usernames may contain lowercase latin characters, numbers, dots, or underscores
Name string `json:"name"`
// Email ID of the user
Email string `json:"email"`
// User roles.
Roles []UserRole `json:"roles"`
// If true user is disabled
IsDisabled bool `json:"isDisabled,omitempty"`
}
type UserGroupRef ¶
type UserGroupRef struct {
Id string `json:"id,omitempty"`
}
type UsersApiAddUserOpts ¶
type UsersApiGetAllUsersOpts ¶
type UsersApiGetUserByIdOpts ¶
type UsersApiService ¶
type UsersApiService service
func (*UsersApiService) AddUser ¶
func (a *UsersApiService) AddUser(ctx context.Context, body User, localVarOptionals *UsersApiAddUserOpts) (User, *http.Response, error)
func (*UsersApiService) DeleteUserById ¶
func (a *UsersApiService) DeleteUserById(ctx context.Context, id string, localVarOptionals *UsersApiDeleteUserByIdOpts) (User, *http.Response, error)
func (*UsersApiService) GetAllUsers ¶
func (a *UsersApiService) GetAllUsers(ctx context.Context, localVarOptionals *UsersApiGetAllUsersOpts) ([]User, *http.Response, error)
func (*UsersApiService) GetUserById ¶
func (a *UsersApiService) GetUserById(ctx context.Context, id string, localVarOptionals *UsersApiGetUserByIdOpts) (User, *http.Response, error)
func (*UsersApiService) UpdateUserById ¶
func (a *UsersApiService) UpdateUserById(ctx context.Context, body User, id string, localVarOptionals *UsersApiUpdateUserByIdOpts) (User, *http.Response, error)
type Vrrp ¶
type Vrrp struct {
State string `json:"state,omitempty"`
VirtualRouterId int32 `json:"virtualRouterId,omitempty"`
VirtualIpv4 string `json:"virtualIpv4,omitempty"`
Priority int32 `json:"priority,omitempty"`
AdvertiseInterval int32 `json:"advertiseInterval,omitempty"`
}
define the VRRP config
type WebReputation ¶
type WebReputation string
const ( TRUSTWORTHY_WebReputation WebReputation = "Trustworthy" LOW_RISK_WebReputation WebReputation = "Low Risk" MODERATE_RISK_WebReputation WebReputation = "Moderate Risk" SUSPICIOUS_WebReputation WebReputation = "Suspicious" HIGH_RISK_WebReputation WebReputation = "High Risk" )
List of WebReputation
type WiFiInterfaceSetting ¶
type WiFiInterfaceSetting struct {
Mode string `json:"mode,omitempty"`
Ssid string `json:"ssid,omitempty"`
Bridge string `json:"bridge,omitempty"`
// frequency of the wifi radio
Freq int32 `json:"freq,omitempty"`
// radio channel to use, its ok to leave this emtpy
Channel int32 `json:"channel,omitempty"`
// https://en.wikipedia.org/wiki/List_of_WLAN_channels
CountryCode string `json:"countryCode,omitempty"`
Encryption *WiFiInterfaceSettingEncryption `json:"encryption,omitempty"`
}
Source Files
¶
- api_device_policies.go
- api_devices.go
- api_edges.go
- api_monitoring.go
- api_policies.go
- api_tenants.go
- api_users.go
- client.go
- configuration.go
- model_add_device_policy_input.go
- model_add_edge_input.go
- model_add_policy_firewall_rule_input.go
- model_add_policy_input.go
- model_add_policy_qo_s_rule_input.go
- model_all_of_gateway_wan_paths_and_links_stats_data.go
- model_client_configuration.go
- model_client_ipv4_pool_ranges_inner.go
- model_clone_id_input.go
- model_data_usage_limit_setting.go
- model_dhcp_relay_server_settings.go
- model_dhcp_server_settings.go
- model_dhcp_server_settings_address_ranges.go
- model_dhcp_server_settings_custom_options.go
- model_dhcp_server_settings_mac_address_to_ipv4_bindings.go
- model_edge.go
- model_edge_activation_code.go
- model_edge_bgp_configuration.go
- model_edge_generate_activation_code_input.go
- model_edge_model.go
- model_edge_overlay_configuration.go
- model_edge_overlay_configuration_routable_addresses.go
- model_edge_ref.go
- model_edge_role.go
- model_edge_status.go
- model_edge_status_ds_devstatus_general.go
- model_edge_status_ds_devstatus_general_dsg_geolocation.go
- model_edge_status_ds_flowcounts.go
- model_edge_status_ds_landevices.go
- model_edge_status_ds_pathstats.go
- model_edge_status_ds_pathstats_dsps_pathstats_sample.go
- model_edge_status_ds_pathstats_dsps_ps.go
- model_edge_status_ds_resusage.go
- model_edge_status_ds_resusage_dsr_containers.go
- model_edge_status_ds_resusage_dsr_loadavg.go
- model_edge_status_ds_resusage_dsr_memory.go
- model_edge_status_ds_resusage_dsr_network.go
- model_edge_status_ds_resusage_dsr_network_dsrn_cellular_stats.go
- model_edge_status_ds_resusage_dsr_network_dsrn_if_geolocation.go
- model_edge_status_ds_resusage_dsr_network_dsrn_ifstats.go
- model_edge_status_ds_resusage_dsr_network_dsrn_trafficstats.go
- model_edge_status_ds_resusage_dsr_storage.go
- model_edge_status_ds_userinfo.go
- model_edge_status_ds_userinfo_dsu_users.go
- model_edge_status_ref.go
- model_edges_list.go
- model_firewall_rule.go
- model_gateway_devices_aggregated_device_flow_stats.go
- model_gateway_devices_aggregated_device_flow_stats_data.go
- model_gateway_devices_aggregated_device_stats.go
- model_gateway_devices_aggregated_device_stats_data.go
- model_gateway_interfaces_latest_stats.go
- model_gateway_interfaces_latest_stats_cellular_stats.go
- model_gateway_interfaces_latest_stats_data.go
- model_gateway_interfaces_latest_stats_wifi_stats.go
- model_gateway_paths_latest_stats.go
- model_gateway_paths_latest_stats_data.go
- model_gateway_routes_latest_stats.go
- model_gateway_routes_latest_stats_data.go
- model_gateway_sys_load_stats.go
- model_gateway_sys_load_stats_data.go
- model_gateway_sys_lte_signal_stats.go
- model_gateway_sys_lte_signal_stats_data.go
- model_gateway_sys_memory_stats.go
- model_gateway_sys_memory_stats_data.go
- model_gateway_sys_uptime_stats.go
- model_gateway_sys_uptime_stats_data.go
- model_gateway_sys_wi_fi_strength_stats.go
- model_gateway_sys_wi_fi_strength_stats_data.go
- model_gateway_wan_aggregated_paths_and_links_stats.go
- model_gateway_wan_aggregated_paths_and_links_stats_data.go
- model_gateway_wan_paths_and_links_stats.go
- model_inbound_nat_rule.go
- model_infiot_error_response.go
- model_interface_settings.go
- model_interface_settings_addresses.go
- model_l4_protocols.go
- model_lte_interface_setting.go
- model_managed_device.go
- model_managed_device_list.go
- model_managed_device_policy.go
- model_managed_device_policy_list.go
- model_managed_device_policy_service.go
- model_managed_device_props.go
- model_managed_device_service.go
- model_mqttgcp_configuration.go
- model_mqttgcp_configuration_topic.go
- model_netflow_collector.go
- model_netflow_exporter_setting.go
- model_object_props.go
- model_object_ref.go
- model_overlay_setting.go
- model_paged_response.go
- model_policy.go
- model_policy_class_of_service.go
- model_policy_config.go
- model_policy_config_pcfg_firewall.go
- model_policy_config_pcfg_firewall_pcfg_fw_logging.go
- model_policy_config_pcfg_general_settings.go
- model_policy_config_pcfg_general_settings_pcfg_netflow.go
- model_policy_config_pcfg_url_filter.go
- model_policy_firewall_action.go
- model_policy_link_steering_action.go
- model_policy_link_steering_action_lnks_via.go
- model_policy_link_steering_action_lnks_via_active.go
- model_policy_link_steering_action_lnks_via_backup.go
- model_policy_match_rule.go
- model_policy_pbr_action.go
- model_policy_qo_s.go
- model_policy_qo_s_action.go
- model_policy_ref.go
- model_policy_scheduler_action.go
- model_policy_traffic_action.go
- model_policy_traffic_priority.go
- model_policy_type.go
- model_proxy_arp_setting.go
- model_radius_setting.go
- model_snmp_setting.go
- model_snmp_trap_setting.go
- model_static_route.go
- model_syslog_server.go
- model_tenant.go
- model_tenant_type_input.go
- model_tenants_list.go
- model_time_series_props.go
- model_traffic_match_criteria.go
- model_update_edge_input.go
- model_user.go
- model_user_group_ref.go
- model_user_ref.go
- model_user_role.go
- model_vrrp.go
- model_web_reputation.go
- model_wi_fi_interface_setting.go
- model_wi_fi_interface_setting_encryption.go
- response.go