Read Current Tree Person Expecting 200 Response
This example request illustrates how to query for the Tree person that represents the current user and specify that you expect a 200 OK response code instead of a 303 See Other response code. Note the use of the X-Expect-Override
header. The 303 See Other response code is not always handled well by certain software programs.
JSON
Request
GET /platform/tree/current-person Accept: application/x-gedcomx-v1+json X-Expect-Override: 200-ok Authorization: Bearer YOUR_ACCESS_TOKEN_HERE
Response
HTTP/1.1 200 OK Content-type: application/x-gedcomx-v1+json X-processing-time: 3 Vary: Accept,Accept-Language,Accept-Encoding,Expect Date: Sun, 03 Apr 1836 10:00:00 GMT-5 Cache-control: no-cache, no-store, no-transform, must-revalidate, max-age=0 Location: https://api.familysearch.org/platform/tree/persons/123456 Transfer-encoding: chunked
XML
Request
GET /platform/tree/current-person Accept: application/x-gedcomx-v1+xml X-Expect-Override: 200-ok Authorization: Bearer YOUR_ACCESS_TOKEN_HERE
Response
HTTP/1.1 200 OK Content-type: application/x-gedcomx-v1+xml X-processing-time: 3 Vary: Accept,Accept-Language,Accept-Encoding,Expect Date: Sun, 03 Apr 1836 10:00:00 GMT-5 Cache-control: no-cache, no-store, no-transform, must-revalidate, max-age=0 Location: https://api.familysearch.org/platform/tree/persons/123456 Transfer-encoding: chunked
Sending...
Feedback was sent.
Can't send feedback. Retry in 5 seconds.