+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: General topics (/forumdisplay.php?fid=15)
+--- Thread: Yealink RPS API error (/showthread.php?tid=47725)
Yealink RPS API error - kov - 05-21-2024 06:26 PM
I'm trying to get started using Yealink RPS for auto provisioning, and am making som test api requests, following the documentation found here:https://support.yealink.com/forward2filesystem/attachment/upload/attachment/2021-2-3/5/49bdb7cd-55de-40c4-a2c6-c88f6e3598f9/Yealink+Json+API+for+RPS+Management+Platform+V3.6.0.30.pdf
I've testet the POST request for listing servers, and the CheckMac api, and both return the same internal server error response, which has a body that indicates the endpoint was not found.
{
"ret": -1,
"data": null,
"error": {
"msg": "service.common.not.found",
"errorCode": 404,
"fieldErrors": []
}
}
For the checkmac request the full uri i'm requesting is
https://api-dm.yealink.com:8443/api/open/v1/device/checkMac?mac=001565123123
I've added the Headers mentioned in the pdf, and created the signature, but i suspect that the backend doesn't get to validating those, when i get a 404 response.
Am i missing something obvious about the URL's for the Yealink RPS API ?
RE: Yealink RPS API error - aspurlock@sipharmony.com - 06-21-2024 10:20 AM
(05-21-2024 06:26 PM)kov Wrote: I'm trying to get started using Yealink RPS for auto provisioning, and am making som test api requests, following the documentation found here:https://support.yealink.com/forward2filesystem/attachment/upload/attachment/2021-2-3/5/49bdb7cd-55de-40c4-a2c6-c88f6e3598f9/Yealink+Json+API+for+RPS+Management+Platform+V3.6.0.30.pdf
I've testet the POST request for listing servers, and the CheckMac api, and both return the same internal server error response, which has a body that indicates the endpoint was not found.
{
"ret": -1,
"data": null,
"error": {
"msg": "service.common.not.found",
"errorCode": 404,
"fieldErrors": []
}
}
For the checkmac request the full uri i'm requesting is
https://api-dm.yealink.com:8443/api/open/v1/device/checkMac?mac=001565123123
I've added the Headers mentioned in the pdf, and created the signature, but i suspect that the backend doesn't get to validating those, when i get a 404 response.
Am i missing something obvious about the URL's for the Yealink RPS API ?
Yealink, can we get some support with this? I am also facing the same issue. My code has been in production for 3 years now, and I also getting the above api error response.
(05-21-2024 06:26 PM)kov Wrote: I'm trying to get started using Yealink RPS for auto provisioning, and am making som test api requests, following the documentation found here:https://support.yealink.com/forward2filesystem/attachment/upload/attachment/2021-2-3/5/49bdb7cd-55de-40c4-a2c6-c88f6e3598f9/Yealink+Json+API+for+RPS+Management+Platform+V3.6.0.30.pdf
I've testet the POST request for listing servers, and the CheckMac api, and both return the same internal server error response, which has a body that indicates the endpoint was not found.
{
"ret": -1,
"data": null,
"error": {
"msg": "service.common.not.found",
"errorCode": 404,
"fieldErrors": []
}
}
For the checkmac request the full uri i'm requesting is
https://api-dm.yealink.com:8443/api/open/v1/device/checkMac?mac=001565123123
I've added the Headers mentioned in the pdf, and created the signature, but i suspect that the backend doesn't get to validating those, when i get a 404 response.
Am i missing something obvious about the URL's for the Yealink RPS API ?
I figured it out. Email me, i'll walk you through what we did wrong. Their docs are outdated.