Crewhu API Patterns git:20260713.1fbd3f3A

Immutable. This exact content is served forever at /api/v1/blob/af2fcb3c7a13619c.

---
name: "Crewhu API Patterns"
when_to_use: >-
  When working with Crewhu authentication headers, pagination, or error handling for the Crewhu
  MCP server. Use when: crewhu api, crewhu authentication, crewhu pagination, crewhu mcp, or
  crewhu token.
description: >
  Use this skill when working with the Crewhu MCP tools — token-based
  authentication via the `X-Crewhu-Api-Token` header, read-heavy tool
  surface, pagination, and error handling.
---

# Crewhu MCP Tools & API Patterns

## Overview

The Crewhu MCP server exposes CSAT/NPS surveys, employee recognition
(badges), and prize/redemption data for MSP teams. The tool surface is
read-heavy — only `crewhu_badges_update_contest` performs writes.

## Connection & Authentication

Crewhu uses an API token passed via header:

| Header | Value |
|--------|-------|
| `X-Crewhu-Api-Token` | The raw API token |

The gateway maps the environment variable `X_CREWHU_APITOKEN` onto the
`X-Crewhu-Api-Token` header automatically.

```bash
export X_CREWHU_APITOKEN="your-crewhu-api-token"
```

## Tool Surface

All 18 tools are exposed flat via `tools/list` — there is no
navigation gating. Tool names follow `crewhu_<domain>_<action>`
across four domains:

- **surveys** (5): list, get, search, detractors, promoters
- **users** (3): list, get, search
- **badges** (5): list, get, history_list, user_recognition, update_contest
- **prizes** (5): list, get, history_list, user_redemptions, pending_redemptions

Only `crewhu_badges_update_contest` performs writes; everything else
is read-only.

## Pagination

Crewhu list endpoints typically accept page/limit-style parameters.
Always check whether more pages exist before claiming a result set is
complete; for survey trend analysis, pull enough history to have a
stable denominator.

## Error Handling

| Status | Meaning | Action |
|--------|---------|--------|
| 401 | Missing or invalid token | Re-check `X_CREWHU_APITOKEN` |
| 403 | Token valid but not authorized for this resource | Check token scope |
| 404 | Unknown survey / user / badge / prize ID | Re-list to confirm |
| 429 | Rate limit | Back off and retry |

## Best Practices

- Treat almost every Crewhu tool as read-only — only
  `crewhu_badges_update_contest` mutates data; flag it explicitly
  before invoking.
- For CSAT trend analysis, pull a wide enough window
  (last 90 days minimum) to avoid sampling noise.
- For multi-team MSPs, group survey results by user/team after fetching.

## Related Skills

- [surveys](../surveys/SKILL.md) - CSAT/NPS analysis (the primary skill)