question

Hi @Moach_2000

What endpoint are you using/what curl command if you don't mind sharing it.

The endpoint should be:

https://vrm-api-docs.victronenergy.com/#/operations/users/{idUser}/get-site-id

Where {idUser] is replaced with your user ID

So the curl command would be:

curl --request GET \ --url https://vrmapi.victronenergy.com/v2/users/{idUser}/installations \ --header 'Content-Type: application/json' \ --header 'x-authorization: Bearer <bearer_token_value>'

With your bearer token in the place of <bearer_token_value> and your User id in place of {idUser}

Hi Matt1309!

Thanks for your support in this topic.

I used VRM Portal to do the tests in different combinations (https://vrm-api-docs.victronenergy.com/#/operations/users/idUser/installations):

curl --request GET \

--url https://vrmapi.victronenergy.com/v2/users/123456/installations \

--header 'Content-Type: application/json' \

--header 'x-authorization: Bearer <abc-123-xyz>'

e.g. 123456 = it's not my real user, just as an example. I used the userid which is visible in the VRM Portal in the URL (6 digits).

Reagrding the token - I created two new one (in the portal in the menu - access token; one was already there and I created two more) and tried both but always the same output (depends on which token I use for the try):

401 Unauthorized

{  "success": false,  "errors": "Invalid accesstoken received",  "error_code": "invalid_token"}

401 Unauthorized

{  "success": false,  "errors": "Token is invalid",  "error_code": "invalid_token"}

Any ideas?

Br, Chris