When registering end devices, I recommend registering them via the CLI unless you are totally sure you have JavaScript under control.
And even if you do, don’t use live data until you are sure it is working.
And do not attempt to delete via Javascript unless you are 110% sure of what you are doing and have tested it on non-live data.
PS, most of us don’t have the API calls memorised, so we too just look at the most likely areas as well or use the search tool at the top of the docs page.
Hey Nick , while I think on it may also be worth reposting the link to your cli overview webpage/tool (for ttn-lw-cli) as useful to many I’m sure - is it updated for latest TTS(CE) builds or still reflecting one of the earlier builds? (3.11 IIRC)
I know I know, was just saying as I found it useful in similar context (trying to figure out capabilities and what is available - cli vs Api as you say) and figured that as with many such useful links on the forum over the years it will have got lost in the ensuing layers of follow on posts… old but not unuseable Now same for API - there’s an idea… No fear, no surprise!
For my understanding, what is “live data”? Is it the data coming from LoRa network?
I’m looking at “EndDeviceRegistry.Create” documentation but there are very few information. For example, I don’t see a description of the format that I should use to send the data concerning the device to add (for example the DevEUI). Where is it documented?