API host confusion. eu1 vs nam1

Hi,

I am tad confused where to send the API calls. Some calls need to be sent to the eu1.cloud domain whilst others need to be sent to the regional nam1.cloud domain.

e.g.

https://eu1.cloud.thethings.network/api/v3/users/ehogeweg/gateways
https://eu1.cloud.thethings.network/api/v3/gateways/my-gateway-id

vs
https://nam1.cloud.thethings.network/api/v3/gs/gateways/my-gateway-id/connection/stats

What is the underlying logic here?

Kind Regards,

Erwin

Nobody? @johan ?

Have you just tried using the region prefix you are in?

They do effectively map back to the same central puddle of data / servers in the end.

But the regional server set will be quicker to reach and quicker for the response to come back.

What’s the worst that can happen?

Hi Nick,

Yes, That is where I started and that didn’t work (404). That’s why I decided to try eu1 and lo-and-bohold, that worked. Then I kept using that host for all calls but now the gateway details calls failed so I tried those on my regional server (nam1) and that worked… So all is working, but now I am in a confused state :slight_smile:

Cheers,

Erwin

@ehogeweg see Addresses | The Things Stack for LoRaWAN