I am using CE 10.4 and this example from Stephen Ball:
https://github.com/DelphiABall/Azure-Cognitive-Services
From that example, I tried "Speech Service" and always get a 401:
Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource.
Fiddler shows, that subscription-key is sent in the Body, not Header.
My Key works in other Application.
As the Code is published from an official Embarcadero Representative, I assume, the Code is right.
Can anybody confirm this behavior - and/or knows, how to change the Code?
Ciao Luigi
In the meantine, the issue is fixed.
Stephen updated the repository.
Related
For the past several months I have a native iOS application that uses the embedded signing API to generate an embedded signing URL. My parameter for returnUrl uses a URL with a custom scheme, say, for example, foo. I was using this custom scheme to intercept when the signing is complete and transition to another part of my application. This is now broken and get the following response:
{
"errorCode": "INVALID_REQUEST_PARAMETER",
"message": "The request contained at least one invalid parameter. 'returnUrl' parameter must be an absolute URL."
}
When I try using the schemes http or https the request works just fine. For example:
https://docusign/complete works
http://docusign/complete works
foo://docusign/complete broken
bar://docusign/complete broken
This is in the dev sandbox and I am not aware of this being broken in production. Is this change intentional or a bug? If intentional, why are you breaking the behavior of the client being able to choose their own URL for redirection? Using this custom scheme, I am able to unequivocally determine that my application is responding to a completion event, without having to introspect any other parts of the URL.
This breaking change is a bug that was introduced by mistake. Thank you for your report on it. I'm escalating it.
This issue is now tracked internally as DocuSign IM-32736
Please contact DocuSign customer support and ask them to add your contact information to IM-32736. Thank you.
This bug has now been declared as a release blocker. It will not go to production. The bug is being fixed and tested. It will probably arrive on demo.docusign.net sometime on Friday. I will update this answer as more progress is made.
Update
The bug has been fixed and the fix has been pushed to demo.docusign.net.
Please advise if this is still an issue. Thank you again for reporting it.
I am trying to implement SCIM Integration with OneLogin. Create, Delete works fine, but on updating a user, my server sends a 200 OK response, still OneLogin server provides me an error without any further description.
Its an "INTERNAL PROVISIONING ERROR"
How to check whats wrong within the scim application with only this detail?
Reach out to developer support at OneLogin (scim-support#onelogin.com). At the end of the day, you're probably sending badly formatted JSON which causes the parser on their end to barf.
One item I've noticed recently is that folks are including // comments in their JSON and that's No Bueno (at least for OneLogin's parsers)
I'm trying to follow the instructions at https://developer.paypal.com/docs/classic/mass-pay/integration-guide/MassPayUsingAPI/#id101DEJ0100A for paying a customer. https://www.paypal.com/us/cgi-bin/webscr?cmd=_profile-api-signature# tells me the API username, API password and and signature. I paste those values directly into my program, and POST those parameters (as well as other parameters) to https ://api-3t.paypal.com/nvp and I get this response back:
TIMESTAMP=2015%2d05%2d06T23%3a58%3a01Z&CORRELATIONID=6eef131f4a296&ACK=Failure&VERSION=2%2e3&BUILD=16566018&L_ERRORCODE0=10002&L_SHORTMESSAGE0=Security%20error&L_LONGMESSAGE0=Security%20header%20is%20not%20valid&L_SEVERITYCODE0=Error
Any tips for troubleshooting what might be going on here?
Thanks in advance!
Kevin
That error means the API credentials you're using are not accurate. Double the check the values themselves and make sure you didn't miss any characters or add any extra white space on the ends of the values. Also, make sure you're not sending sandbox credentials to the live PayPal server or vice-verse. That's usually what's happening when people run into this.
when I try to get few people profile use instagram api it shows error message APIAgeGatedError, what does this mean? how to solve it
I can't find documentation about this exception, but I think this problem is related with your IP, I changed IP-adress and problem was solved. Or try to use proxy-server.
The APIAgeGatedError type error is generated because the content from the requested profile is restricted to a minimum age. You can't reach the content for sure with your "general token". Perhaps with an token that has been authorized from the page you are trying to get content from. However Instagram has no provided documentation about this.
I have a premium Spotify account and I am trying to generate an application key to use with libspotify. I am doing this using the form here: https://developer.spotify.com/technologies/libspotify/request-key/, but the generation of the key always fails with a message "There was an error generating your application key".
I tried formatting my application name differently (e.g., spaces, no spaces, no dashes, etc), but the outcome is still the same.
Not sure if it's of any relevance, but I am logged in through facebook and my user name on the application form is shown as a number.
Is it possible that there is something wrong with my account ?
Thanks in advance,
-Kal.
I suspect that something is up with the API key registration page. I've filed an internal bug report with the team that maintains that (I work at Spotify), and hopefully it'll be up and running soon! I'll update this answer if it turns out to be something other than that.
Edit: The error was on Spotify's website, everything seems to be working again.