Start a new topic

API key visibility in eWeLink

Itead has recently, in V3 firmware, made available a HTTP REST API  (many thanks for this, it is great progress and I think will broaden the uptake of your devices)

For device not branded DIY, encryption is turned on and the 'api_key' is needed to use the REST API.

This api_key is currently available during pairing, but not after.

Could the eWeLink application which stores the key made available during pairing, make the key visible under 'settings' so users with custom integrations can more easily access the api-key and thus use the HTTP REST functionality.

3 people like this idea

The API documentation shows the cloud interface. How does one use the API locally without depending on the cloud? This link is the local API. I have not seen the cloud API, where is that published
Login or Signup to post a comment