A remote computing device for regulating pairing with hardware resources, comprising: pairing request receipt logic to receive, via a Representational State Transfer, "REST", call, a pairing request from an application executed on a computing device (104, 106), wherein the pairing request specifies a hardware resource of the computing device (104,106); intermediary logic, coupled with the pairing request receipt logic, to: provide, via a REST call, request data to the computing device (104, 106), wherein the request data includes an identifier of the application, an Internet Protocol, "IP", address of the application, and an identifier of the hardware resource to the computing device(104, 106), and receive, via a REST call, pairing approval from the computing device (104, 106), wherein the pairing approval is generated by the computing device (104, 106) based on whether the IP address of the application in the request data matches the IP address of the computing device (104, 106); and token generation logic, coupled with the intermediary logic, wherein the token logic is to, in response to receipt of the pairing approval, generate a pairing token for provision to the application, wherein the pairing token is to be provided to the computing device (104, 106) by the application, via an REST call, to pair the application with the hardware resource. pairing request receipt logic to receive, via a Representational State Transfer, "REST", call, a pairing request from an application executed on a computing device (104, 106), wherein the pairing request specifies a hardware resource of the computing device (104,106); intermediary logic, coupled with the pairing request receipt logic, to: provide, via a REST call, request data to the computing device (104, 106), wherein the request data includes an identifier of the application, an Internet Protocol, "IP", address of the application, and an identifier of the hardware resource to the computing device(104, 106), and receive, via a REST call, pairing approval from the computing device (104, 106), wherein the pairing approval is generated by the computing device (104, 106) based on whether the IP address of the application in the request data matches the IP address of the computing device (104, 106); and token generation logic, coupled with the intermediary logic, wherein the token logic is to, in response to receipt of the pairing approval, generate a pairing token for provision to the application, wherein the pairing token is to be provided to the computing device (104, 106) by the application, via an REST call, to pair the application with the hardware resource. provide, via a REST call, request data to the computing device (104, 106), wherein the request data includes an identifier of the application, an Internet Protocol, "IP", address of the application, and an identifier of the hardware resource to the computing device(104, 106), and receive, via a REST call, pairing approval from the computing device (104, 106), wherein the pairing approval is generated by the computing device (104, 106) based on whether the IP address of the application in the request data matches the IP address of the computing device (104, 106); and token generation logic, coupled with the intermediary logic, wherein the token logic is to, in response to receipt of the pairing approval, generate a pairing token for provision to the application, wherein the pairing token is to be provided to the computing device (104, 106) by the application, via an REST call, to pair the application with the hardware resource.