> For the complete documentation index, see [llms.txt](https://docs.iotcore.omnicore.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotcore.omnicore.korewireless.com/overview/universal-device-broker/mqtt-and-http-devices/guides/connect/authentication/http-device.md).

# HTTP Device

Complete these steps before using the HTTP bridge:

* Set up one or more device registries, including a Cloud Pub/Sub topic for telemetry events
* Create devices

### Authenticating devices[​](https://docs.omnicore.korewireless.com/docs/Universal%20Device%20Broker/MQTT%20&%20HTTP%20Devices/Guides/Connect/Authentication/HTTP%20Device#authenticating-devices) <a href="#authenticating-devices" id="authenticating-devices"></a>

Each request to the HTTP bridge must include a JSON Web Token (JWT) in the header.

Http Device Authentication

```
curl -H 'authorization: Bearer JWT' -H 'cache-control: no-cache' 'https://demo-http.api.cloud.korewireless.com/http/subscriptions/{subscription-id}/registries/{registry-id}/devices/{device-id}/config'
```

The full path of the device can end in the device ID.

Each request must include the JWT, even if you send several requests in quick succession. OmniCore does not "remember" authentication over the HTTP bridge. For more information about authentication and JWTs, see the sections on [device security](/overview/universal-device-broker/mqtt-and-http-devices/guides/security/device-security.md) and [device credentials](/overview/universal-device-broker/mqtt-and-http-devices/guides/connect/authentication/managing-credentials/using-json-web-tokens-jwts.md).