Question by natshiwc_83 · Sep 18, 2018 at 02:51 PM · fulfillment apicreateshppingfulfshippingapiinternal server errorjsonfulfillment orders
CreateShippingFulfillment Error
Hi All,
Is there something i am doing wrong as i am getting an error from eBay saying: "There was a problem with an eBay internal system or process. Contact eBay developer support for assistance
URL Endpoint:
Postfields: {"lineItems": [{ "lineItemId": 10011526199901, "quantity": 2 }], "shippingCarrierCode": "DHLGlobalMail",
"trackingNumber": "GM295117583012073280"}
Header { Content-Type: application/x-www-form-urlencoded Authorization: Bearer $eBaySettings['accessToken'] }
RESPONSE Array ( [errors] => Array ( [0] => Array ( [errorId] => 2003 [domain] => ACCESS [category] => APPLICATION [message] => Internal error [longMessage] => There was a problem with an eBay internal system or process. Contact eBay developer support for assistance [parameters] => Array ( [0] => Array ( [name] => code [value] => 415 ) ) ) ) )
Answer by hun_4973 · Sep 24, 2018 at 01:52 PM
Hi @natshiwc_83
Just wanted to let everyone know we solved the issue for our application. It appears that although in their documentation Ebay states clearly
HTTP request headers
All requests made to eBay REST operations require you to provide the Authorization HTTP header for authentication authorization.
This method has no additional required headers.
Note the : "This method has no additional required headers."
However it appears that the Content-Type header is also required (see Header Content Type) and can only be the value application/json
so your issue would then be because you are sending an incorrect Content-Type and need to instead change the data and Content-Type header to JSON.
When we started doing this our requests started working.
At this point I would like to ask Ebay to update their documentation to reflect that other headers are in fact required. You can even change the phrasing to refer to only the Authorization and other request method specific headers are required.
Furthermore it should also be noted that by returning a 500 Ebay doesn't just fail to act in a RESTful manner but actively spreads false information as a 500 indicates that there is an internal server error and the issue occurs due to a problem internally in Ebay; however because this error occurs due to not having all the necessary headers, or correct values to these headers, Ebay should respond with a 4xx Error Code as it is a bad client request that is causing the error.
I hope someone finds this helpful.
People who like this
Answer by natshiwc_83 · Sep 18, 2018 at 03:01 PM
@devanathan.developersupport@ebay.com, @catherine_developersupport, @shulmani_developer.support, @zhuowei.developersupport@ebay.com
People who like this
Answer by hun_4973 · Sep 20, 2018 at 01:09 PM
Just wanted to add I have the exact same issue, unfortunately my post about has been sitting in "moderation" for almost a week now.
But that being said, I would like to add that I get the same issue no matter what body I send, blank body, only the required fields, etc. I also know the access token works because I can get orders with the same access token.
Any help would be much appreciated by me as well.
People who like this
Answer by marlinpu_75 · Mar 13 at 10:10 PM
At this point I would like to ask Ebay to update their documentation to reflect that other headers are in fact required. You can even change the phrasing to refer to only the Authorization and other request method specific headers are required.
People who like this
Your answer

Follow this Question
Related Questions
Wrong value for orderFulfillmentStatus 0 Answers
How to use Fulfillment api 1 Answer
Order Fulfillment Rest API not working 1 Answer
Getorders pagination offset is ignored 0 Answers
RESTful in Europe/Germany 2 Answers