I am not able to like a feed by a friend of the user. The unlike works if the feed has been posted by the session user. I am using the graph api endpoint /feed-id/likes. Also using the same endpoint i am able to like the feed, facing problems only for unlike. Getting the following response:
{
"error": {
"message": "(#200) Feed story publishing to other users is disabled for this application",
"type": "OAuthException",
"code": 200
}
}
The februrary breaking changes announced that only the call to [user_id]/feed where user-id is different from session user will fail.
Then why am I facing problems while trying to perform a DELETE on feed-id/likes, that too when a POST on feed-id/likes seems to work fine?
i had the same issue and solved in this way:
XXXX_YYYY is your feed-id, you can like it calling feed-id/likes using Method.POST, but for unlike you must use YYYY/likes using Method.DELETE.
PS: be sure that in your permissions you have "publish_stream".
I get
"error": {
"message": "(#100) The parameter url is required",
"type": "OAuthException",
"code": 100
}
when calling YYYY/likes using Method DELETE.
Related
I'm working on a PayPal payment integration using a Java Springboot microservice where in an order is created on PayPal, i'm retrieving the order details from the paypal successfully. Now I want to update the order in the PayPal by adding an attribute invoice_id. But, when the Update Order(PATCH) is being called, Paypal throws a bad Request.
Doc link : https://developer.paypal.com/docs/api/orders/v2/#definition-order_capture_request.customized_x_unsupported_3218_order_application_context
PATCH https://api-m.sandbox.paypal.com/v2/checkout/orders/{{order_Id}}
Request :
{
"op": "add",
"path": "/purchase_units/#reference_id=='default'/invoice_id",
"value": "123456"
}
Error Response: [{"name":"INVALID_REQUEST","message":"Request is not well-formed, syntactically incorrect, or violates schema.","debug_id":"1ef2afd17aa1p", "details":[{"field":"/","location":"body","issue":"MALFORMED_R... (421 bytes)]
Can someone help me on this please.
I tried out multiple things like changing the request body. But, it doesn't seem to be working.
I'm trying to build a bot using Twitter API. I'm testing Filtered stream to read the latest tweets with some words.
To test I create a single rule with a trending topic from Brasil:
{
"data": [
{
"id": "1360964144200110081",
"value": "carnaval lang:pt",
"tag": "Carnaval"
}
],
"meta": {
"sent": "2021-02-14T15:47:31.321Z"
}
}
But when I execute the GET Stream https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/api-reference/get-tweets-search-stream, it never returns. I believe this can be a WebSocket, but I can't find that information on docs.
I'm doing a request on https://api.twitter.com/2/tweets/search/stream?tweet.fields=created_at&expansions=author_id&user.fields=created_at using the Authorization token and I'm getting 200 as a response, but the connection is never closed and no content.
I'm using the following code to call: github.com/vepo/twitter4j
Solved!
The problem is that I was expecting a String, but, as it is a WebSocket, the Response never ends. I change it to an InputStream and it starts working.
I am trying to integrate the YELP API within an application in Android Studio. I am trying to acquire an access token using a post request in Postman. However, when I send the post request I get this error returned in JSON format:
{
"error": {
"code": "VALIDATION_ERROR",
"description": "'client_credentials' is not one of ['authorization_code', 'refresh_token']",
"field": "grant_type",
"instance": "client_credentials"
}
}
I have searched this site and google for what the description line means in particular:
"description": "'client_credentials' is not one of ['authorization_code', 'refresh_token']",
I have not been able to find any results as to what this error means. Here is my project setup in postman:
I simply copy and pasted my client ID and API key from yelp and stored them within the client_id and client_secret in Postman respectively. When I send this requestion I get the 400 Bad Request error and find out that its a validation error. At first I thought that I entered the wrong API key, however, I refreshed the API key and directly copy and pasted it, so I am confident that my API key and client ID are correct. The output should look like this and it should deliver an access token:
I couldn't find any examples that had this specific error message.
You no longer need a refresh token, all you need is an API key in your Authorization header:
Authorization: Bearer {{apiKey}}
Source: https://www.yelp.com/developers/documentation/v3/authentication
I am working on developing a REST-API, ie Alfresco based java-backed webscript.
Where I am supposed to pass a Json as POST request parameter field.
When I try to retrieve the parameter field on server side using:
webScriptRequest.getParameter(json);
I am recieving a corrupted Json.
Based on analysis its getting corrupted because of one of the below fields or may be combination of them,
I don't know exactly which special character is causing this corruption problem.
Can anybody help me out in figuring-out this issue.
My hunch is some special character combination in below field is corrupting the json:
2014-04-23T13:42:24.962-04:00
/case/77777777/doc/x-search-found.pdf
http://temp.com/doc/source/url
/case/77777777/doc/my-findings.pdf
2014-04-23T13:42:24.962-04:00
"docGroupNames": ["working", "suggested"]
If I remove above fields, I start receiving the healthy json on server side.
Below is the sample JSON:
{
"documentAlias": "DocNameForTmngUiDisplay",
"modifiedByUserId": "User XYZ",
"sourceSystem": "TMNG",
"sourceMedia": "electronic",
"sourceMedium": "upload",
"accessLevel": "public",
"scanDate": "2014-04-23T13:42:24.962-04:00",
"docList": [
{
"documentId": "/case/77777777/doc/x-search-found.pdf",
"metadata": {
"modifiedByUserId": "User XYZ",
"documentAlias": "nickname",
"sourceMedia": "paper",
"docSourceUrl": "http://test/doc/source/url",
"docCategory": "web"
}
},
{
"documentId": "/case/77777777/doc/my-findings.pdf",
"metadata": {
"sourceMedium": "fax",
"accessLevel": "public",
"scanDate": "2014-04-23T13:42:24.962-04:00",
"evidenceSourceTypeId": "123",
"docGroupNames": [
"working",
"suggested"
]
}
}
]
}
Additional Disclosure:
This looks like REST-Client issue, try changing your Rest Client is one probable solution to json corruption issue.
This issue is happening specifically on SoapUI 5.0.0 Above issue is NOT happening on DHC 0.7.2.2 (Chrome based rest client extension)
I am using the new version of the payments: Local currency Payments and my tests are given me different results. Sometimes everything is well, but sometimes an error appeared when I am asking to the facebook graph for more details about the payment.
The url that I am using is:
https://graph.facebook.com/PAYMENT_ID?access_token=APP_ACCESS_TOKEN
PAYMENT_ID, is the id of a payment (status=completed) and the APP_ACCESS_TOKEN, is the application access token. Both are good values.
The error that appear sometimes is:
{
"error": {
"message": "An unexpected error has occurred. Please retry your request later.",
"type": "OAuthException",
"code": 2
}
}
I was using restfb and I have tried the same thing by hand, but nothing seems to change.
Has anyone had the same problem?