Confusion regarding the "Constituent (Convert)" endpoint

Austin Stallman

I have had difficulties using this API to convert a non-constituent individual relationship into a constituent record. I am providing the system record ID of the non-constituent individual relationship listed in the properties of the relationship, but I am receiving a 404 error. Whenever I provide this same ID to the Relationships endpoint, it pulls up the relationship I expected to find. Is this not the ID this endpoint is expecting? If not, which ID is it expecting, and where could I find it?

Austin Stallman

I have also tried providing the relation_id returned by the Relationship endpoint, but that gives me a 400 error.

Trevor Kelly

Hi Austin!

You're going to want to use the System Record ID of the non-constituent as the input for that API call. The easiest way to find that is to access the non-constituent's record from the RE NXT webview, and take the ID from the URL bar- see example below. In this example, I can call the following API and it will make Camelia into a full-blown constituent record.

Austin Stallman

Thanks for the response! I found out that the issue was with the ID I was using for the constituent code, not the non-constituent ID. Once I found the right ID for the constituent code, the API worked as expected.