You can update parent records via OpenApply's API using a PATCH request with a JSON body.
If you are syncing information between ManageBac and OpenApply, please check with the Support team to confirm that OpenApply is the master application for the field before you send any requests. If it is not the master application, any changes you make could be overwritten by the automatic sync.
We recommend downloading our Postman collection of OpenApply endpoints, which includes full annotation and sample responses for a quick way to get started with the API. For help to set up authentication see: OpenApply v3 API Authentication
In OpenApply the endpoint to update a parent is:
For example, when using my test site, f1.openapply.com, and parent with id: 2509217
You'll need to use the OpenApply ID rather than your Parent ID, which you can find in:
Please note this endpoint is paginated with 50 results per page by default.
Enter the OpenApply ID in the parameters of the patch request, e.g.
Enter the key or keys that you would like to update in the body of the request in JSON format. The keys that can be updated for a parent are:
- First name (first_name)
- Last Name (last_name)
- Other Name (other_name)
- Preferred Name (preferred_name)
- Parent ID (parent_id)
- Address (address)
- Address 2 (address_ii)
- City (city)
- State (state)
- Postal Code (postal_code)
- Email (email)
- Mobile phone (mobile_phone)
- Phone (phone)
When you send your request you will see the update in the response received. The response will include additional keys (such as "full_address") which are combinations or summaries of other fields, and cannot be updated directly.
Please note: If the update fails, the changes requested will be skipped. You will still receive a Status 200 response.
Possible reasons why this could occur are that the key specified doesn't match one of the keys exactly, or the parent entity has not been declared.