# Admin: Notify (Cluster)
## Endpoint
`/api/admin/cluster/secondary/notify`
## Method
GET
## Description
Made by the Primary node to all Secondary nodes whenever there is any change in the configuration that the Secondary nodes must sync. The Secondary nodes must use the Transfer Config call to sync the config changes when this notification is received. The notification also includes the latest details of the Primary node. This call can only be made at the Secondary node (i.e., the Primary calls this endpoint on each Secondary).
## Authentication
Required. Token must be provided via the `token` parameter.
## Permissions
Administration: Delete
## Parameters
| `token` | string | Yes | No | The session token generated by the `login` or the `createToken` call. |
| `primaryNodeId` | integer | Yes | No | The calling Primary node's ID to allow identification at the Secondary node. |
| `primaryNodeUrl` | string | Yes | No | The calling Primary node's API web service URL. |
| `primaryNodeIpAddresses` | string | Yes | No | A comma-separated list of the calling Primary node's IP addresses. |
## Response Fields
No response body fields beyond the status. Response is simply:
```json
{
"status": "ok"
}
```
## Conditional Logic Notes
- This call is made at the Secondary node, by the Primary node.
- This is a machine-to-machine API call; it is not intended for direct use by administrators.
- Upon receiving this notification, the Secondary node should initiate a Transfer Config call to the Primary to sync changes.
- The Primary node's details (URL, IP addresses) included in the notification allow the Secondary to update its record of the Primary.
## Edge Cases
- If the `primaryNodeId` does not match what the Secondary expects, the notification may be rejected for security.
- This is a push notification mechanism; if the Secondary is unreachable, the notification is lost and the Secondary will sync on its next scheduled config refresh.