When trying to update my modal using Slack's views.update endpoint, I get an "error": "not found" message in the return body.
According to Slack's documentation, this means that the view ID or external ID could not be found, but I've made sure to check the initial view ID to make sure it matches and I've tried generating unique external IDs to ensure that the correct modal is being referenced.
Any help would be appreciated.
Related
I am using Postman to successfully create a booking business using a POST method Http request to:
https://graph.microsoft.com/beta/bookingBusinesses.
The request body is like:
{
"DisplayName" : "TEST",
"Email" : "orgmailbox#xxxbuisiness.onmicrosoft.com"
}
The response contains an id.
I am not succeeding when attempting to delete the booking using the REST API here: https://learn.microsoft.com/en-us/graph/api/bookingbusiness-delete?view=graph-rest-beta&tabs=http
The Id use in the DELETE request is that extracted from the response body when the booking business was created.
I get Response code 404 ("Unkown Error").
As per the documentation the registered App in Azure AD has the required Bookings.Manage.All permissions
Does anyone know what might be wrong / how to resolve?
I can reproduce your problem. If you have deleted it, you will get a 404 error when you run the delete again, so please make sure you have deleted it. There may be some delay.
By the way, when you request the api, do not supply a request body for this method, and do not add unnecessary request parameters.
You can use graph-explorer testing.
First delete request：
Second delete request：
The issue we had was due to MFA (Multi-Factor Authentication). When we disabled the requirement for MFA for the user, we were able to successfully make the calls to delete the entry using Postman.
We are implementing the Sign In with Apple functionality for web application. We are following the ReST based approach. The authorization call is working fine and we are getting the 'code' and 'state' values on the return request object. But I am not getting the customer info.
Authorization end point : https://appleid.apple.com/auth/authorize
The user info section is completely missing on the apple doc. Is anyone know which endpoint to hit for getting the user info and what is the request format.
I have tried the token API call from Apple and I'm getting the response as 'unsupported_grant_type'
Endpoint : appleid.apple.com/auth/token
Header : svc.addHeader("Content-Type", "application/x-www-form-urlencoded");
Body :
{'client_id' : client_id, 'client_secret_key' : client_secret_key,
'grant_type' : grant_type, 'code' : code, 'redirect_uri' : redirect_uri}
grand_type value we set as 'authorization_code'.
Response service=AppleSignInTokenService status=ERROR errorCode=400 errorMessage={"error":"unsupported_grant_type"}
Please let me know where I'm going wrong.
If you getting 400 error, check the redirect URL exist at Service ID redirect section or not. Make sure the client id is the same as the Service ID Identifier or not.
If you getting 200, but no user information returns. That could be you already do sign in with apple with your site, you could go to https://appleid.apple.com/account/manage, then click APPS & WEBSITES USING APPLE ID under security. If you see your site then click stop using Apple ID. Now, when you back to the site to do sign in again, the user information will be included. Seems like apple only returns user information on first time.
I am working on an application that integrates with Instagram API to access the user information. I successfully fetch the Access Token using the authorize url but unable to fetch the userId using access_token url:
i am tried both the endpoints:
https://api.instagram.com/oauth/access_token?client_id=48275564e2c445f6b8e1356djfha3e0c&client_secret=ab2062da9f314e3489dke7ae9cbe6e5d&redirect_uri=http://localhost&grant_type=authorization_code
https://api.instagram.com/oauth/access_token
with the post body as:
client_id=48275564e2c445f6b8e1356djfha3e0c&client_secret=ab2062da9f314e3489dke7ae9cbe6e5d&redirect_uri=http://localhost&grant_type=authorization_code&code=1351860224.4827556.5dc92c4d15ea4a4ea1b0d33eaf0eef19
(The data in the request is modified), But i am getting the follwing
{
"code": 400,
"error_type": "OAuthException",
"error_message": "No matching code found."
}
I have seen tons of queries and questions but could not find any solution to the problem.
The couple of questions i have is:
1) is the field code in the URL is same as access_token, if not how could i get the code field's value.
2) is there any other mechanism(API) to fetch the user details given the username is not known.
Please help me as i am completely stuck and running out my deadlines.
For me unchecking Disable implicit OAuth in instagram developer -> manage clients fixed the issue
I found that using either form-data or application/x-www-form-urlencoded works fine. The most important is the code you get from redirect uri is only used by one request. It means you could request the access token once for the code. If the you request more than one time with same code, you'll get the error like this:
{
code: 400,
error_type: "OAuthException",
error_message: "Matching code was not found or was already used."
}
Wish you all the best ;)
Try to urlEncode the redirect_uri param to
http%3A%2F%2Flocalhost
And your code param contains the "." character which might be a error.
code=1351860224.4827556.5dc92c4d15ea4a4ea1b0d33eaf0eef19
might caused the problem
"error_message": "No matching code found."
"5dc92c4d15ea4a4ea1b0d33eaf0eef19" seems to be the correct code
I got same error. It seems that instagram's spam system disable user's access to any non-official application. Just change user's password. In my case it was help.
Also try create another application.
UPD
From my answer to another question
It looks like users get more than one code, and you see first code, but need second. Try relogin users, if you gets error. User will not see instagram page with confirm button, just redirections.
Possible algorithm of error:
1. User click auth link.
2. Get first code.
3. User click auth link (twice, redirection problem, public auth system, etc.)
4. Get another code (even on the same client_id, redirect_uri).
5. You get first code.
6. But first code already doesn't exists.
The problem is here that need redirect url set as http://localhost/signin-instagram
signin-instagram part is very important
So go to Instagram.com/developer ->Manage Client-> Security -> Valid redirect URIs set with that end http:/../signin-instagram
Off late instagram python snippet fails due to missing content-type HTTP header
response, content = http_object.request(url, method="POST", body=data,headers = {"Content-type": "application/x-www-form-urlencoded"})
adding application/x-www-form-urlencoded worked for me
I will mention what worked for me.
Step 1. Generate a new client secret from you panel.
Step 2. Follow the step 1 mentioned here to obtain the code again.
Step 3. Send the request again with the changed parameters.
Make sure you are logged in the browser when you send the request. You will get the required response.
Go into Facebook for Developers > Your app. Click on "Roles" and add an Instagram test-account under "Instagram Testers".
Log into instagram.com and go to: Settings > Security > Apps and Websites, where you will accept the test invitation.
Prepare your URL link, which you will paste into the web browser. Make sure to use a valid redirect URI from "Valid OAuth Redirect URIs" from the Instagram Basic Display settings.
If you did everything right, the Instagram tester account for the app, will have the option to gain access to user_profile,user_media. Continue the process to get the code which you can exchange for a short-lived access token.
This question already has answers here:
DocuSign ID Check with Embedded signing
(2 answers)
Closed 8 years ago.
I have a website where in the user is shown a docusign template for his signature on the sales contract. Before i do that i need to verify if the user is a legitimate user. Is there a way to have the ID check that Docusign Provides in their website implemented through the web page i'm working on. I tried searching for some useful links ,
http://community.docusign.com/t5/DevCenter-Program-Feedback/Phone-ID-Check-authentication-through-the-API/td-p/2521
http://community.docusign.com/t5/Dev-Zone-MOVED-TO-STACK-OVERFLOW-Use-tag-DocuSignAPI-old/ct-p/dev_zone
but they show access denied (I have a demo account).
Please do let me know if you need any more details. Appreciate the help
There might be a bug here, but I got this to work by specifying the RSA ID Check in the template recipient authentication settings, then when I reference that template in an Embedded Signing API call it starts out on the ID Check before allowing access to the envelope.
Doing this confirms that you can combine RSA ID Check with Embedded Signing, so that's the answer to that part. However the fact that I had to set the RSA authentication at the template level in the Console and the requireIdLookup property in my requests seems to be ignored makes me think that there's a bug.
I will follow up with DocuSign with regards to that property not having an effect on the envelope, however for now you should be able to get this to work as specified above. If you sometimes use that template and do NOT want the RSA ID Check for recipients, then you can simply make another template that's exactly the same but add the ID check in, and reference that new template in your API calls and use the first template when you don't want RSA ID Check.
I have a Gosquared widget in my Geckoboard that is tracking one of my site.It is working perfectly fine.Now,I want to add another Gosquared widget to track another site. I entered all data correctly(site name, site ID and API key), also I have put the Gosquared tracking code on my rails application. When i try to create the widget, the connection breaks down with following error "Account does not exist.".I have no clue why its not working.Please help me!!
Try testing that data is being sent from the GoSquared API successfully by accessing the GoSquared API URL directly using your credentials:
http://api.gosquared.com/concurrents.json?sid={SITE_ID}&api_key={API_KEY}
Make sure you replace {SITE_ID} and {API_KEY} in that URL with your respective details.
If you receive a JSON object like {"concurrents":150,"range_max":187} then the problem may be with Geckoboard somewhere. If you get an error on the GoSquared API, contact us on support#gosquared.com or message me here!
Geoff
GoSquared