New profile elements: parent_unions and partner_unions ?

Hmm, the parent_unions and partner_unions fields are gone.

I really liked them compared to the messy immediate-family records and secondly it saved you from an extra request to find parents, partners and siblings.

Hi,

I would also like this function to come back!

The immediate-family request works, but is kind of mis-matched in relation to other APIs as it gives a lot of redundant information, which slows things down.

Regards, Kenneth

I already asked Amanda about these (in Tr8n) - got no answer.

Kenneth, - you only need to load immediate-family records when following a line since immediate-family also contains the profile records, so parent_unions is not needed, but as you say: you have an overload since you also get all spouses and siblings, but that is needed if you want to process a descendants line.

I am able to load 10 generations of ancestors in 29 seconds now and I am not finished fine tuning my code yet.

Thanks. This worked quite nicely.

Hmm.. I'm not seeing how to get marriage date this way. What am I missing?

When reading the immediate-family record and have sorted out the union-id for the partner union you want the details on you do a new get for that specific union as https://www.geni.com/api/union (-XXXX for union id)

Oki, thanks. Works nicely.

On some profiles, I get HTTP response 403 as response to my immediate-family request. These are marked as private I assume.

What I do then is to make the simplest possible request i.e. "https://www.geni.com/api/<xrefname>".

Is that expected behaviour, and am I using the correct procedure when it happens? I don't get any relations at all with the fallback request, so it's not ideal...

Private User do you have any opinion on this?

Need an example on this.

The syntax is https://www.geni.com/api/profile/immediate-family, - where you use /profile-nnnn/ for specific profile-ID's

This is my full request:

"https://www.geni.com/api/" + xrefName + "/immediate-family?only_ids=true&fields=first_name,middle_name,nicknames,last_name,maiden_name,name,suffix,occupation,gender,birth,baptism,death,burial,cause_of_death,unions,id,about_me,is_alive,profile_url,mugshot_urls,public";

and this is my "simple" request:

"https://www.geni.com/api/" + xrefName

Hmm.. I just see that pasting gave some strange quotes not present in the real world...

This is my full request:

"https://www.geni.com/api/"; + xrefName + "/immediate-family?only_ids=true&fields=first_name,middle_name,nicknames,last_name,maiden_name,name,suffix,occupation,gender,birth,baptism,death,burial,cause_of_death,unions,id,about_me,is_alive,profile_url,mugshot_urls,public";

and this is my "simple" request:

"https://www.geni.com/api/" + xrefName

Above I use xrefName instead on profile-nnnn of course...

And here is a profile where I need to use the mentioned "trick" to get any data back:

Knut Emanuel Nordgren

What is xrefName?
The API documentation does not refer to any such usage.
Use profile-id or profile guid with a g- in front.

That specific profile is a private living profile outside your family which you would get an access denied of when trying to get immediate family by using for example
https://www.geni.com/api/profile-g6000000012926735630/immediate-family

When not being a curator I get.
{
error: {
type: "ApiException",
message: "Access Denied"
}
}

If you have found a way to bypass this it should be reported and stopped.

For this specific profile however, he should probably be marked as deceased public since he is born in 1908. If you have documentation that he is deceased I can fix this, but for now we can keep it as an example.

xrefName is just my variable name for profile-<id> in C#.

What I get is the same as when viewing a private profile on the web, i.e. the name can be something like "<private> Isaksson".

I am just wondering why I couldn't get that anonymized information from a call including immediate-family ?

OK, as when viewing the profile in a browser?

Usually you don't even come so far in the browser unless you know the profile id. The only useful information you can get is number of children.

At some point the API should stop you processing and I think this is such a case. The union object might reveal the profile-ids of the children.

Ok, then I know it's expected behaviour. Fine with me.

You can discuss if even listig the children as "<private> Isaksson". when viewing the private profiles as you can do on Knut Emanuel Nordgren on is allowed according to GDPR.

We had a situation some years ago when a person added his out of wedlock child to the tree and forgot that the family did not know about it and could see his tree.. He had to go through several rounds of explanations and excuses...

Hmm.. As I understand it I don't get any children nor parents in the union data when doing the non "immediate-family" request.

Perhaps what you are saying is that these private profiles should not be included in unions from their relatives either? Yes, that might be logical.