Getting An error has occurred while creating Constituents

Nikunj Prajapati

Hey folks,

i am trying to create constituent into RENXT through api but many times i am getting “An error has occurred.” message.

Request URL : constituent/v1/constituents

Below one is my sample request

{

"first": "Nikunj",

"last": "Lg",

"phone": {

"do_not_call": false,

"inactive": false,

"number": "212-212-2131",

"primary": true,

"type": "Work"

},

"address": {

"address_lines": "Test, Test",

"city": "Miami",

"postal_code": "TRFSS",

"country": "United States",

"state": "Ohio",

"type": "Home"

},

"email": {

"address": "nikunj+lg@xxxx.com",

"primary": true,

"type": "Email"

},

"preferred_name": "Nikunj",

"import_id": "EGf2c05dc230af434190",

"type": "Individual"

}

And below is the response i am getting

{

"Message": "An error has occurred."

}

The important thing that however it is throwing error in api but still the Constituent is created.

can some one please help me?

Alex Wong

@Nikunj Prajapati
you only provided a JSON body for the creation so it is hard to determine what might be wrong. Here's a few situation:

• have you been able to do a GET constituent? (meaning you already took care of authentication to call API)
• does the app and user has right to create constituent record
• the request body json looks right, but
  • is “Work” a valid phone type in your RENXT instance
  • is “Home” a valid address type in your RENXT instance
  • is “Email” a valid email type in your RENXT instance
  • Suggestion, try a basic request without any “table entries” issue to resolve:
    {
    "first": "Nikunj",
    "last": "Lg",
    "type": "Individual"
    }

Nikunj Prajapati

@Alex Wong Thanks for your quick response, actually the issue was importid in my case where i was passing same value for every constituent create request.

Alex Wong

@Nikunj Prajapati
glad you found the issue.

Note that import id is optional, you do not need to provide that info. Import ID is automatically assigned properly (unique value) by RE directly. So unless your org requires import id to be in specific formatting, don't need to provide specific import id to use.