Generate intent summary

Generate an intent summary for a test case when intent exceeds a character limit.

POST /v1/generate-intent-summary

Generate Intent Summary Endpoint

cURL

curl --request POST \
  --url https://api.getbluejay.ai/v1/generate-intent-summary \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <x-api-key>' \
  --data '
{
  "test_case_id": 123
}
'

200

{
  "test_case_id": 123,
  "intent_summary": "<string>",
  "skipped": false
}

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.

## Generate intent summary — POST /v1/generate-intent-summary

> **What this endpoint does:** Generate intent summary for a test case (only if intent exceeds character limit). **400** if the test case tags indicate workflow playback (tag lowercased contains `workflow`): workflow-tagged digital humans use enriched playback on the agent; intent summary is not applicable.

**Endpoint:** POST `https://api.getbluejay.ai/v1/generate-intent-summary`
**Auth:** `X-API-Key` header
**Content-Type:** application/json

### Required Parameters
| Name | Type | Description |
|------|------|-------------|
| X-API-Key | string | API key required to authenticate requests. |
| test_case_id | integer | ID of the test case |

### Request Body (required fields)
```json
{
  "test_case_id": 123
}
```

Refer to the full schema at https://docs.getbluejay.ai/api-reference/endpoint/generate-intent-summary. Include optional fields that serve the goal of setting up for testing and monitoring on Bluejay.

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

def generate_intent_summary(payload: dict, api_key: str) -> dict:
    url = "https://api.getbluejay.ai/v1/generate-intent-summary"
    headers = {"X-API-Key": api_key}
    response = requests.post(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 400: Workflow-tagged test case: intent summary not applicable; 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.

For some workflow-driven digital humans this route returns 400; see the constraints above and the OpenAPI description.

Headers

X-API-Key · string · required

API key required to authenticate requests.

Body

application/json

Request model for generating intent summary.

test_case_id · integer · required

ID of the test case

Response

200

application/json

Successful Response

Response model for generating intent summary.

test_case_id · integer · required

ID of the test case

intent_summary · string | null

The generated intent summary, or null if intent is short

skipped · boolean · default: false

True if summary was skipped because intent is short