Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Speaker Recognition API returns bad request with no further message #95

Open
snake-doctor opened this issue Apr 18, 2017 · 1 comment
Open

Comments

@snake-doctor
Copy link

Hi

I am sending my wav file to api see below

RequestMessage {Method: POST, RequestUri: 'https://westus.api.cognitive.microsoft.com/spid/v1.0/identificationProfiles/034f5efa-a536-4d9b-a90f-38686c8eb263/enroll?shortAudio=True', Version: 1.1, Content: System.Net.Http.MultipartFormDataContent, Headers:
{
Ocp-Apim-Subscription-Key: 72d89b96c4434b7ba8377b51aaaeb211
Content-Type: multipart/form-data; boundary="54a6b99e-b621-4c65-b445-08476656aec2"
Content-Length: 223
}} System.Net.Http.HttpRequestMessage

I get the ff in return

clientResponse {StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
Pragma: no-cache
apim-request-id: e82122b7-4dc1-4a96-bd51-7be46dc05a7e
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
Cache-Control: no-cache
Date: Tue, 18 Apr 2017 12:50:28 GMT
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Content-Length: 83
Content-Type: application/json; charset=utf-8
Expires: -1
}} System.Net.Http.HttpResponseMessage

Kindly help

@NeelBhatt
Copy link

I am facing the same issue. Does anyone know the solution?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants