# Servicenow

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

- Skill: `apideck-libraries/servicenow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add apideck-libraries/servicenow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/apideck-libraries/servicenow/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/servicenow

---


# ServiceNow (via Apideck Proxy)

Access ServiceNow through Apideck's **Proxy API** with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to ServiceNow's native API — you keep using ServiceNow'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 ServiceNow to a unified-API resource model — your code talks ServiceNow'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:** `servicenow`
- **Mode:** Proxy-only (no unified API resources)
- **Auth type:** oauth2
- **Status:** beta
- **Apideck setup guide:** [OAuth credentials](https://unify.apideck.com/connector/connectors/servicenow/docs/application-owner+oauth_credentials) · [Connection guide](https://unify.apideck.com/connector/connectors/servicenow/docs/consumer+connection)
- **Gotchas:** [page](https://developers.apideck.com/apis/proxy/servicenow/gotchas)
- **ServiceNow docs:** https://developer.servicenow.com/dev.do
- **Homepage:** https://servicenow.com

## When to use this skill

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

1. That ServiceNow routes through Apideck's **Proxy API**, not a unified resource API
2. The correct `serviceId` to pass on every call (`servicenow`)
3. How to keep using ServiceNow'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:** OAuth 2.0
- **Managed by:** Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.
- **User setup:** Users authorize via the Vault modal. Connection state progresses `available → added → authorized → callable`.
- **Token refresh:** automatic. Expired tokens are refreshed transparently on the next API call.

## Calling ServiceNow via the Proxy API

Send any HTTP request to `https://unify.apideck.com/proxy`. Apideck looks up the user's stored ServiceNow credentials by `x-apideck-consumer-id` + `x-apideck-service-id`, injects them on the way out, and returns ServiceNow'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: servicenow" \
  -H "x-apideck-downstream-url: <target endpoint on ServiceNow>" \
  -H "x-apideck-downstream-method: GET"
```

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

See [ServiceNow's API docs](https://developer.servicenow.com/dev.do) for available endpoints.

## See also

- [Apideck OAuth setup guide for ServiceNow](https://unify.apideck.com/connector/connectors/servicenow/docs/application-owner+oauth_credentials)
- [Apideck connection guide for ServiceNow](https://unify.apideck.com/connector/connectors/servicenow/docs/consumer+connection)
- [ServiceNow gotchas](https://developers.apideck.com/apis/proxy/servicenow/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
- [ServiceNow official docs](https://developer.servicenow.com/dev.do)