Tree Building rights

There are two access rights: The access right for the application (to get an Oauth 2 access code), and the access right the user running the application have. If you as a user have access to read and add profiles in an area manually an application the user are using will have the same rights.

If an application causes problems for Geni it is easy for them to block all usage of it by pulling the authorization rights.

When reading the documentation of some tools I understood that the rights of users to use tree maker capabilities by API needs to be granted by a curator (at least that happened to me for SmartCopy).

Essentially I tried to use the API for creating a child and did not work, giving me an strange error. Notice that I used sandbox on purpose to not create "dummy data".

Is there any example "ready to test" where I can test that I am doing the POST right?

FYI: The "granting of rights" for SmartCopy is managed within the application; that is a layer "on top of", if you will, the Geni-granted authorization.

Arg... SmartCopy "granting rights" was what confused me together with the specification in v1 of the API saying the need of specific rights.

Anyhow I fixed on my own... I am just going to introduce here which was my problem in case anybody else is having the same problem...

So I was making a POST call to this address:

Privateadd-child?first_name=Mike&names[de][first_name]=Mike?access_token=mytokengoeshere

Essentially I made 2 mistakes:

- There are 2 id numbers for the profile, one needs a "g" before and another is a longer number without the need of such number. I missed the "g" before.
- Parameters is REST calls should by separated by a "&" not a "?".

The correct address was:

https://www.sandbox.geni.com/api/profile-g1149101/add-child?first_n...

Hope this helps somebody in the future