Were getting a lot of #INTERNAL_SERVICE_ERROR's through the rest PayPal API. To get more details about the error we have been going the PayPal Tech Support. We've been able to fix some of the issues but it is taking us a lot longer than we would like. I was wondering if there was an API call that I could make that would give me the full details of the error or DebugID?
I am not sure how you are currently consuming the API, but https://developer.paypal.com/webapps/developer/docs/api/ specs the error object which has the debug_id, the PayPal internal identifier used for correlation purposes. The error object has information link and error_details object which has the detailed reasons for the error
If you are using an sdk to consume, it is possible to get the debug_id in your logs: https://github.com/paypal/rest-api-sdk-nodejs#debugging and https://github.com/paypal/rest-api-sdk-python#create-payment show ways to do that in Python and Node.
I myself am looking for the same information. But it appears the debug ID is only so Paypal support can correlate the error to a transaction event. Technically there is no other information associated with the Debug ID.
See Receiving INTERNAL_SERVICE_ERROR REST API
Related
HTTP request failed, status Code: 403, when I try to call Map Api in flutter Here is the screenshot
Anyone please help me out
The url shown in your screenshot returns the following message along with the 403 code:
The Google Maps Platform server rejected your request. You must enable Billing on the Google Cloud Project at https://console.cloud.google.com/project/_/billing/enable Learn more at https://developers.google.com/maps/gmp-get-started
You therefore have to do three things, in you code and on the Google cloud console:
Ensure that you trap and report any error message returned from the api in order to better understand the response code.
Cancel the api key that you have now published to the world and generate a new one for the Google maps api, in cloud console.
Enable billing on your project otherwise Google maps api will never work as it is a chargeable service.
Hope this helps. As I said, NEVER publish api keys nor store them on GitHub or similar.
Sorry to say but error 403 means you don't have any access to that image from the server side.
I'm trying to test out my API in WSO2 API Manager. I've gone to the API Store, logged in as a regular client user, subscribed to the API, and now I'm trying to test it using the API Console. I can see the API just fine, and I'm clicking the "try it out" button. Unfortunately, for all of my API calls, I just get the progress meter going on forever (the "....." thing on the right). It never completes.
There is nothing in the logs that indicates what is going wrong. I have tried turning a ton of different settings in the log4j.properties file to TRACE or DEBUG, and I'm still getting nothing.
I think I'm asking something very basic, but there seems to be no information about it anywhere: How do I just get the product to log when a REST message comes in to the gateway, and log the HTTP it is trying to send to my REST API? I'm sure if I could get that showing in a log, then I could probably figure out what is going wrong.
Here's how you do it in API Cloud (hosted version of API Manager): http://wso2.com/blogs/cloud/trace-api-calls-and-responses/ - I assume that the same mediation sequences are in the latest version of the product too.
I am working on integrating the PayPal REST API in my Symfony 2 web app. Currently I am struggling on implementing the controller that handles the Webhooks.
This is just a event handler, that is called by the PayPal API on different event like updates to an payment.
I configured the Webhook to consume the following events:
PAYMENT.SALE.COMPLETED
PAYMENT.SALE.DENIED
PAYMENT.SALE.PENDING
PAYMENT.SALE.REFUNDED
PAYMENT.SALE.REVERSED
Now I am trying to find out, which events will contain which data. The docs only say:
resource_type string Name of the resource contained in the resource property.
So far so good. But I was not able to find any information about what event will contain what resource_type. There are really a lot of different resource_types and I have no idea which of these are allowed/possible when dealing with the different events.
Does anyone know where to find this information, since the PayPal docu itself is not very help full in this case.
Am implementing the exception handling for the Intuit Customer Account Data API in my application. I get a "null" for the Error code but when I check through the API explorer, I am able to see the error code and message. How do I access this through the AggregationCategorizationException object?
Make sure you are using IPP .Net SDK for Customer Account Data 1.4.0 or later.
There was an update to "provide detailed error codes and messages". See release notes here:
https://developer.intuit.com/docs/0020_customeraccountdata/devkits/0250.net_cad_devkit_1.0/release_notes
If you can't/don't want to upgrade, you could consider using reflection to access the private information in the AggregationCategorizationException object. I know for 1.3 the information was in the object, just private.
Using REST API, sandbox and attempting to get bearer token. Receiving the following error
{"name":"INTERNAL_SERVICE_ERROR","information_link":"https://api.sandbox.paypal.com/docs/api/#INTERNAL_SERVICE_ERROR","debug_id":"5a235c510522b"}
How can I find out what the debug id means?
The 'debug_id' is an internal identifier we can use to pull up the request within PayPal.
You may see our classic API calls refer to this as the 'correlationID'.
Unfortunately I'm not finding anything in our system for this debug_id. Can you log a ticket (www.paypal.com/mts) or email me (address in profile) with details of the call, including your full HTTP request (minus credentials) and the resources you tried to access, as well as the full HTTP response?
I suggest we close this answer as it's not strictly programming-related, but I can continue working on this via mail / ticket with you.
By the way; if you're using the 4111111111111111 credit card: this card number is currently inoperable in the Sandbox environment and may throw 'internal service error' type responses as well. You can use any other card number instead.