Hi,
I’m POSTing data to a bubble endpoint. It works in postman and returns a dataset that has ‘nested’ fields (profile: …):
{
“id”: “676133161”,
“quantity”: 1,
“profile”: {
_ “first_name”: “Polly”,_
_ “last_name”: “Pocket”,_
_ “email”: "[email protected]",_
}
},
“event_id”: “26835849749”,
“order_id”: “536707466”,
“ticket_class_id”: “52933328”
}
I’m able to get the ‘non-nested’ fields: event_id, order_id, etc… to populate into my database using the API workflow, but the ‘nested’ fields profile:first_name, last_name & email don’t populate.
If I make profile_email a required field the POST fails and returns an error that the field profile_email doesn’t exist.
How have others handled these ‘nested’ json fields in the API workflow?