Skip to main content
PUT
/
v1
/
update-community
/
{community_id}
Update Community
curl --request PUT \
  --url https://api.getbluejay.ai/v1/update-community/{community_id} \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <x-api-key>' \
  --data '
{
  "title": "<string>",
  "description": "<string>",
  "digital_human_ids": [
    123
  ]
}
'
{
  "id": "<string>",
  "title": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "description": "<string>",
  "digital_human_ids": [
    123
  ]
}
Integration Prompt for AI Agents
# Bluejay — Testing & Monitoring Platform for Conversational AI Agents

You are a senior backend engineer integrating the Bluejay API. Think step-by-step: first understand the endpoint, then plan the integration, then implement with minimal changes.

## Update Community — PUT /v1/update-community/{community_id}

> **What this endpoint does:** Update a specific community by ID.

**Endpoint:** PUT `https://api.getbluejay.ai/v1/update-community/{community_id}`
**Auth:** `X-API-Key` header
**Content-Type:** application/json

### Required Parameters
| Name | Type | Description |
|------|------|-------------|
| community_id | string |  |
| X-API-Key | string | API key required to authenticate requests. |

Review the full parameter list at https://docs.getbluejay.ai/api-reference/endpoint/update-community and include any optional parameters (e.g., `title`, `description`, `digital_human_ids`) that serve your integration's use case and align with Bluejay's testing and monitoring capabilities.

### Request Body
```json
{
  "title": "string",
  "description": "string",
  "digital_human_ids": [
    123
  ]
}
```

### Example
**PUT with body:**
```python
import requests

def update_community(community_id: str, payload: dict, api_key: str) -> dict:
    url = f"https://api.getbluejay.ai/v1/update-community/{community_id}"
    headers = {"X-API-Key": api_key}
    response = requests.put(url, headers=headers, json=payload)
    response.raise_for_status()
    return response.json()
```

### Constraints
- Minimal changes — only add/change files needed for this integration.
- Match existing codebase patterns (naming, file structure, error handling).
- Include error handling for 422: Validation Error.

### Integration Checklist
Before writing code, verify:
1. Which module/service owns this API domain in the codebase?
2. What HTTP client and error-handling patterns does the project use?
3. Are there existing types/interfaces to extend?

Then implement the integration, export it, and confirm it compiles/passes lint.
This endpoint allows you to update an existing community. Provide the community ID and updated details to update the metric.

Headers

X-API-Key
string
required

API key required to authenticate requests.

Path Parameters

community_id
string<uuid>
required

Body

application/json
title
string | null

Title of the community

description
string | null

Description of the community

digital_human_ids
integer[] | null

List of digital human (test case) IDs to associate this community with (replaces existing associations)

Response

Successful Response

Response model for community operations

id
string
required

Unique identifier for the community

title
string
required

Title of the community

created_at
string<date-time>
required

When this community was created

description
string | null

Description of the community

digital_human_ids
integer[]

List of digital human (test case) IDs associated with this community