---
title: "Manage the associations of a Rules"
method: POST
path: "/healthmonitoring/rules/{rule_id}/associations"
tags: ["Graph", "Rules"]
---

# Manage the associations of a Rules

`POST /healthmonitoring/rules/{rule_id}/associations`

## Request

- Base URL: `https://console.jumpcloud.com/api/v2`
- URL: `https://console.jumpcloud.com/api/v2/healthmonitoring/rules/{rule_id}/associations`
- Auth: API key in header `x-api-key`
- TypeScript: <https://skmtc.dev/jumpcloud/apis/jumpcloud-api-2/docs/healthmonitoring/rules/:rule_id/associations/post.ts> (a function with typed inputs; its response is checked against the schema)

This endpoint allows you to manage the _direct_ associations of a Health monitoring rule.

A direct association can be a non-homogeneous relationship between 2 different objects, for example Rules and Systems.

#### Sample Request
```
curl -X POST https://console.jumpcloud.com/api/v2/healthmonitoring/rules/{rule_id}/associations/ \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {API_KEY}' \
  -d '{
    "op": "add",
    "type": "system_group",
    "id": "{Group_ID}"
  }'
```

## Headers

- `x-org-id` string

## Request body

- GraphOperationRule
  - `id` string, required: The ObjectID of graph object being added or removed as an association.
  - `op` 'add' | 'remove' | 'update', required: How to modify the graph connection.
  - `attributes` GraphAttributes, nullable: The graph attributes.
  - `type` 'system' | 'system_group', required: Targets which a "rule" can be associated to.

## Response `204`

---

[API](https://skmtc.dev/jumpcloud/apis/jumpcloud-api-2.md) - [All operations](https://skmtc.dev/jumpcloud/apis/jumpcloud-api-2/llms.txt) - [OpenAPI document](https://skmtc.dev/jumpcloud/apis/jumpcloud-api-2/revisions/3f09fe63caaa?raw)