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 · Connection guide
Gotchas: page
ServiceNow docs: https://developer.servicenow.com/dev.do
Homepage: https://servicenow.com

servicenow

ServiceNow (via Apideck Proxy)

Quick facts

When to use this skill