Custom_Vision_Prediction_3.0 REST API Giving 401 error

Question

I am trying to call Custom Vision Prediction Classification RestAPI Endpoint (https://southcentralus.dev.cognitive.microsoft.com/docs/services/Custom_Vision_Prediction_3.0/operations/5c82db60bf6a2b11a8247c15)

I am using South Central US endpoint

I got the required Training and Prediction key from Keys section In Resource Management Azure Portal

Following is the response I am getting back if I call the Custom Vision Prediction classification RestAPI Endpoint

{

"error": {
"code": "401",
"message": "The ClassifyImage Operation under Custom_Vision_Prediction_3.0 API is not supported with the current subscription key and pricing tier Custom_Vision.Training.S0."
}
}

I can see that It saying that my current pricing tier is not supporting 3.0 API but the plan S0(Standard) costing me 0.35 USD per 1k images and my subscription plan is Pay-As-You-Go

Then Why I am getting this error?

Any help appreciated

did you double-check that you are using the Prediction key for the API call, not the training key? — silent, Sep 09 '19 at 07:51
@silent There is total 2 key in Keys Section of Azure Portal and I have tried with both, no luck :( — Indrajit Sinh Rayjada, Sep 09 '19 at 08:18
Are you sure that you are looking at the correct resource in the Azure Portal? It should show "API type: Custom Vision Prediction" — silent, Sep 09 '19 at 08:25
There are two resources created for you when you created Custom vision. One for Training and one for Prediction — silent, Sep 09 '19 at 08:26
OMG! I was not aware of that @silent So when I tried with other resources as you have mentioned it worked! Thanks :) — Indrajit Sinh Rayjada, Sep 09 '19 at 08:30

score 5 · Accepted Answer · answered Sep 09 '19 at 08:55

When you create a Custom Vision in your Azure subscription, two resources are created for you: One for Training and one for Prediction. Each has a dedicated set of API keys.

Make sure to use the correct resource for either Training or Prediction usage.

score 0 · Answer 2 · answered Mar 08 '23 at 10:16

0

Had the exact same issue but our problem was caused by not publishing the iteration we were trying to access.

Once we published the iteration and used the prediction key the issue was resolved.

answered Mar 08 '23 at 10:16

Ken

1,155
2
19
36

Custom_Vision_Prediction_3.0 REST API Giving 401 error

2 Answers2