In case you've notice problems with our XING E-Recruiting API we will help you. To do this as quickly as possible please provide us detailed logging information about what went wrong. This guide will show you how such logfiles should look like.
Your logfiles should contain the following data:
X-Logjam-Request-Id
headerHere you see an example logfile separated into its two main parts:
> Date: Fri, 18 Aug 2017 09:35:36 GMT
> PUT /vendor/jobs/postings/30675491 HTTP/1.1
> Host: api.xing.com
> User-Agent: curl/7.51.0
> Accept: */*
> Content-Length: 237
> Content-Type: application/x-www-form-urlencoded
>
> oauth_token=3d28d6dabd1a5c1a8d19&oauth_consumer_key=84ea471edca164b18325&oauth_signature_method=PLAINTEXT&oauth_signature=b3849cc73fcdd00825871bf3e2ddf0e2bed6a68a%269f65b788a2b460085c839f4c37ccb26a17169e1b&
> { "function": "New Job Title" }
< HTTP/1.1 204 No Content
< Date: Fri, 18 Aug 2017 09:35:38 GMT
< Server: Apache
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET,POST,OPTIONS
< Access-Control-Allow-Headers: Content-Type
< Access-Control-Allow-Credentials: false
< Access-Control-Max-Age: 60
< Content-Disposition: {}
< X-XING-Deprecation-Status: {}
< Cache-Control: no-cache
< X-Logjam-Request-Id: xws-production-d28f2f7926e447368e93a5091646c926
< X-Logjam-Request-Action: Vendor::ProxyController#jobs
< X-Request-Id: d4a66719-b1ff-45e1-97fc-53af36570aa4
< X-Runtime: 0.126141
< X-Powered-By: Phusion Passenger 4.0.60
< Set-Cookie: {}
< Set-Cookie: c_=h3l3n4m31n5ch47z1chl13b3d1ch; domain=.xing.com; path=/; expires=Sat, 19 Aug 2017 09:35:38 -0000; secure; HttpOnly
< Location: {}
< Status: 204 No Content