How Creating a Contact Actually Works in GetResponse
Creating a contact requires specifying the campaign (list) ID it joins -- GetResponse contacts don't exist independently of a list the way some platforms maintain one universal contact database.
Real API Details
Depending on that campaign's confirmation setting, a newly created contact may land as pending double opt-in confirmation rather than immediately active and sendable -- creating the contact via the API doesn't bypass the list's own subscription rules.
Practical Considerations
The same real person subscribed on two different lists exists as two separate contact records with separate IDs -- there's no automatic account-wide contact merging across campaigns, so deduplication across lists has to be handled by whatever's calling the API.
Use cases
Automatically enroll new leads from a form into a GetResponse list.
- Sync CRM new contacts to GetResponse for immediate nurturing.
- Apply tags or segments upon creation in GetResponse.
- Trigger welcome sequences in GetResponse once a contact is added.
- Validate contact data and prevent duplicates during ingestion.