Import records into a REDCap longitudinal project via the API with instrument-event mapping validation

Steps

1. First export the project's instrument-event mappings via action=export, content=formEventMapping to confirm which instruments are assigned to which events in each arm
2. Structure the import payload as a JSON array where each object contains record (record ID), redcap_event_name (unique event name), and field values; include redcap_repeat_instance for repeating instruments
3. POST with content=record, action=import, format=json, type=flat, overwriteBehavior=normal (or overwrite to replace existing values) and data containing the serialized JSON array
4. Check the API response for the count of records imported and inspect any errors array for field-level validation failures before committing downstream processes
5. For branching-logic fields, ensure dependent fields are included only when their branching condition is met; the API does not enforce branching logic but mismatched data may cause discrepancies in reports
6. After import, call content=generateNextRecordName to auto-generate the next record ID if the project uses auto-numbering, ensuring sequential record IDs