Inquiry regarding error code 429 when requesting DCE AP

[뇽박]

I am trying to receive 'power' data using the API provided by DCE, and I used Python and proceeded in the following order.

1) Collect access tokens

2) Check all devices using '/v1/devices'

3) Utilize 'isxcGuid' and '/v1/sensors/[guid]' found in devices to call all APIs for each guid and look up the Total_power(kw) value.

If you search in the above order, most values ​​will return an error code of 429, making the search impossible. (Step 3 requires approximately 3,000 API calls)

I would like to ask if there is a separate guide on how to resolve the 429 error code.

In addition, I would appreciate it if you could tell me how many APIs can be collected at once.

When I tried to access it in a different way because error code 429 occurred, I made a request to '/v1/sensors/type/{type}' with type as NUMBER_POWER, but infinite loading occurred because data was not collected, so the query could not be performed.

[Cory_McDonald]

Hello @뇽박,

The 429 error is due to reaching the rate limit of the API. I recommend making sure you are on the latest version of DCE (8.3.0 as of this response).

I would recommend trying to perform your task in the following way:

1) Collect access tokens

2) Check all devices using '/v1/devices' (keep in storage in program for use with step 3)

3) Use the '/v1/sensors/type/{type}' call with a type of NUMBER_POWER

   - You mentioned that this gave you infinite loading, if it is, please try using the web interface of DCE (https://DCE_IP/isxg/rest) to test this call first.  If it gives you issues there, you may need to contact your local support for further investigation into the issue of the Rest call not working).

4) In your program, filter the results to get just the sensors that you are looking for.  The "podId" in the response body for each sensor should tie to a "isxcGuid" of the device the sensor is associated with.

This should limit your program to only needing to do 2 calls instead of approximately 3001 as long as you can get the type call to work correctly.

Kind Regards,

Cory

[뇽박]

Thanks for your reply!

As I mentioned at the end of my question, 3) using type as NUMBER_POWER in '/v1/sensors/type/{type}' causes infinite loading and data retrieval is not possible. I would appreciate it if you could tell me the solution in this case.

[뇽박]

Thanks for your reply!

When I try to access the DCE web interface (https://DCE IP/isvg/rest) mentioned in the 3rd one, it loads infinitely and returns a 503 error code.
If you have any trouble, you have guided me through the following method. Could you please provide a detailed guide on how to do this?
"If it gives you issues there, you may need to contact your local support for further investigation into the issue of the Rest call not working."

Or is there another way to do this?

[Cory_McDonald]

Hello @뇽박,

In regards to the DCE web interface rest page not loading, please ensure that you are using HTTPS and that the DCEIP is being replaced by the IP address of your DCE Server.  Should look something like this:  https://10.10.10.10/isxg/rest

In your response you had isvg instead of isxg as well, which may cause the issue as that page does not exist.

As the Rest API is still being built out, you could fall back and use the SoapAPI that has a specific type call that may suit your needs: 

Once you have access to DCE's rest API documentation page at the above URL, you should be able to run the command and see if the call isn't work because of DCE or something within your code.

If your program needs to be urgently created while you are working with support, you can fall back to use the SoapAPI calls.  The call works differently than the RestAPI calls as the RestAPIs are still being built out as changes occur with the web interface:

Kind Regards,

Cory