# Monday

> monday.com via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to monday.com's native API. Use when the user wants to call monday.com (no unified API resource mapping). Routes through Apideck with serviceId "monday".

- Skill: `apideck-libraries/monday` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add apideck-libraries/monday`
- Raw SKILL.md: https://api.skillmd.com/api/skills/apideck-libraries/monday/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- License: Apache-2.0
- Author: apideck-libraries (https://skillmd.com/u/apideck-libraries)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/apideck-libraries/monday

---


# monday.com (via Apideck Proxy)

Access monday.com through Apideck's **Proxy API** with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to monday.com's native API — you keep using monday.com's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.

> **Auth-only / proxy-only connector.** Apideck does not map monday.com to a unified-API resource model — your code talks monday.com's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.

## Quick facts

- **Apideck serviceId:** `monday`
- **Mode:** Proxy-only (no unified API resources)
- **Auth type:** apiKey
- **Status:** beta
- **Apideck setup guide:** [OAuth credentials](https://unify.apideck.com/connector/connectors/monday/docs/application_owner+oauth_credentials)
- **Gotchas:** [page](https://developers.apideck.com/apis/proxy/monday/gotchas)
- **monday.com docs:** https://developer.monday.com/api-reference/docs
- **Homepage:** https://monday.com/

## When to use this skill

Activate this skill when the user wants to call monday.com via Apideck — for example, "call the monday.com API" or "fetch data from monday.com". This skill teaches the agent:

1. That monday.com routes through Apideck's **Proxy API**, not a unified resource API
2. The correct `serviceId` to pass on every call (`monday`)
3. How to keep using monday.com's native request/response shapes while Apideck handles Vault auth

If you need a unified-API surface (one method shape across many vendors), see the connector skills in this catalog whose serviceId is mapped to a unified API.

## Auth

- **Type:** API Key
- **Managed by:** Apideck Vault — the user pastes their monday.com API key into the Vault modal; Apideck stores it encrypted and injects it on every request.
- **Rotation:** if the user rotates their key, they re-enter it in Vault. No code changes needed.

## Calling monday.com via the Proxy API

Send any HTTP request to `https://unify.apideck.com/proxy`. Apideck looks up the user's stored monday.com credentials by `x-apideck-consumer-id` + `x-apideck-service-id`, injects them on the way out, and returns monday.com's raw response.

```bash
curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: monday" \
  -H "x-apideck-downstream-url: <target endpoint on monday.com>" \
  -H "x-apideck-downstream-method: GET"
```

For `POST`/`PATCH`/`PUT`/`DELETE`, change `x-apideck-downstream-method` and pass the body as you would to monday.com directly. Apideck does not transform the body — it forwards bytes.

See [monday.com's API docs](https://developer.monday.com/api-reference/docs) for available endpoints.

## See also

- [Apideck OAuth setup guide for monday.com](https://unify.apideck.com/connector/connectors/monday/docs/application_owner+oauth_credentials)
- [monday.com gotchas](https://developers.apideck.com/apis/proxy/monday/gotchas)
- [Apideck Proxy API reference](https://developers.apideck.com/apis/proxy/reference)
- [`apideck-rest`](../../skills/apideck-rest/) — REST patterns including the Proxy
- [`apideck-best-practices`](../../skills/apideck-best-practices/) — Vault, error handling, retries
- [`apideck-unified-api`](../../skills/apideck-unified-api/) — when to use unified vs proxy
- [monday.com official docs](https://developer.monday.com/api-reference/docs)