PUT
/communication
Usage Notes
When
- Update contact values (email address, phone number)
- Change communication type classification
- Transfer communication ownership between entities
Requirements
- CommunicationID or ExternalCommunicationId to identify the record
- Complete DTO required (retrieve current data via GET first)
Notes
- PUT replaces entire record - include all data to retain
- Email addresses must remain globally unique
- ExternalCommunicationId cannot be changed after creation
- Entity ownership can be transferred by changing entity ID fields
Description
Updates a communication record by complete replacement. To transfer ownership, clear current entity ID and set new entity ID. Only one entity association allowed.
Required Headers - See Authentication
| Header | Value | Description |
|---|---|---|
| Authorization | {accessToken} | Bearer token for API access |
| Version | 2.0 | API version identifier |
| Content-Type | application/json | Content type for request body |
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
CommunicationID |
integer | 7G platform identifier for communication record to update. Cannot be changed - used only for record targeting. | |
externalCommunicationId |
string(50) | Optional |
Your external identifier for this communication record. Cannot be changed after creation. |
CommunicationTypeID |
integer | Classification of communication method determining system routing, validation rules, and uniqueness requirements. Email addresses must be globally unique across the platform; phone numbers allow duplicates for shared lines. | |
name |
string(255) | Updated communication value (email address, phone number with country code, or fax number). Format validation applied based on communicationTypeID classification. | |
BizEntityID |
integer | Updates communication linkage to business entity. Use when transferring communication ownership or maintaining entity-level association for investor correspondence. | |
externalBizEntityId |
string(50) | Your external ID for the business entity (alternative to bizEntityID). | |
PersonID |
integer | Updates communication linkage to individual person. Use when transferring ownership or maintaining person-specific contact information. | |
externalPersonId |
string(50) | Your external ID for the person (alternative to personID). | |
OrganisationID |
integer | Updates communication linkage to organisation. Use when transferring ownership or maintaining corporate-level contact information. | |
externalOrganisationId |
string(50) | Your external ID for the organisation (alternative to organisationID). |
CommunicationID
7G platform identifier for communication record to update. Cannot be changed - used only for record targeting.
externalCommunicationId
Your external identifier for this communication record. Cannot be changed after creation.
CommunicationTypeID
Classification of communication method determining system routing, validation rules, and uniqueness requirements. Email addresses must be globally unique across the platform; phone numbers allow duplicates for shared lines.
name
Updated communication value (email address, phone number with country code, or fax number). Format validation applied based on communicationTypeID classification.
BizEntityID
Updates communication linkage to business entity. Use when transferring communication ownership or maintaining entity-level association for investor correspondence.
externalBizEntityId
Your external ID for the business entity (alternative to bizEntityID).
PersonID
Updates communication linkage to individual person. Use when transferring ownership or maintaining person-specific contact information.
externalPersonId
Your external ID for the person (alternative to personID).
OrganisationID
Updates communication linkage to organisation. Use when transferring ownership or maintaining corporate-level contact information.
externalOrganisationId
Your external ID for the organisation (alternative to organisationID).
Entity Ownership Transfer
To transfer communication ownership, provide the new entity association:
- Clear current ownership by setting all entity IDs to null
- Set new owner using bizEntityID, personID, or organisationID
- Only one entity association is allowed per communication record
Important: Communication ownership changes affect compliance notifications and investor correspondence routing.
Example Requests
bash
# Update communication email address
curl -X PUT "https://api.7g.com.au/communication" \
-H "Content-Type: application/json" \
-H "Authorization: {accessToken}" \
-H "Version: 2.0" \
-d '{
"communicationID": 12345,
"externalCommunicationId": "EMAIL-001",
"communicationTypeID": 2,
"name": "john.smith.updated@example.com",
"bizEntityID": 789
}'
# Transfer communication ownership to different entity
curl -X PUT "https://api.7g.com.au/communication" \
-H "Content-Type: application/json" \
-H "Authorization: {accessToken}" \
-H "Version: 2.0" \
-d '{
"communicationID": 12345,
"externalCommunicationId": "EMAIL-001",
"communicationTypeID": 2,
"name": "john.smith@example.com",
"bizEntityID": null,
"personID": 456
}'Response Examples
json
{
"result": true,
"message": "Communication updated successfully",
"recordCount": 1,
"data": {
"communicationID": 12345,
"externalCommunicationId": "EMAIL-001",
"communicationTypeID": 1,
"name": "john.smith.updated@example.com",
"bizEntityID": 789,
"externalBizEntityId": null,
"personID": null,
"externalPersonId": null,
"organisationID": null,
"externalOrganisationId": null
}
}