Apideck

REST API at unify.apideck.com/crm/contacts (example — path varies per API category). Categories: crm, hris, accounting, file-storage, email-marketing, ecommerce, ats, lead-management. GET /crm/contacts lists contacts (normalized schema). POST /crm/contacts creates a contact. GET /hris/employees lists employees. Passthrough: POST /connector/connectors/{id}/request passes arbitrary requests to the underlying API. Response: normalized JSON with raw_data if requested. Pagination via cursor or limit/offset. x-apideck-consumer-id header identifies the end-user consuming the connection.

Standard HTTP status codes with JSON error responses: type_name, message, detail, ref. 401 for invalid API key, 402 for plan limit exceeded, 404 for missing consumer/connection, 422 for validation errors. Connection not found (consumer has not connected the service) returns 404. Rate limits per plan tier. Webhook events for connection status changes (connected, expired, disconnected). Apideck platform uptime at status.apideck.com. Connector gaps (field not supported) return empty values with metadata indicating passthrough needed.

Apideck provides a unified API layer over multiple SaaS categories: CRM (Salesforce, HubSpot, Pipedrive), HRIS (Workday, BambooHR, Rippling), accounting (QuickBooks, Xero, NetSuite), file storage (Google Drive, Dropbox, OneDrive), email marketing (Mailchimp, ActiveCampaign), e-commerce (Shopify, WooCommerce), and more. Agents integrate once with Apideck's normalized schema and access all connected services without managing individual connectors. Apideck handles OAuth flows for end-user authorization (Vault), connector updates, and schema normalization. Competitive with Merge.dev and Nango; broader category coverage but shallower per-connector depth. Confidence is docs-derived.

Bearer token auth: Authorization: Bearer {api_key}. API keys from Apideck Console → API Keys. x-apideck-consumer-id header required (identifies which user's connection to use). x-apideck-app-id header required (identifies your Apideck application). End-user connections managed via Vault: Apideck-hosted OAuth flow redirects end-users to authenticate with their SaaS tools. Connection tokens stored securely in Apideck Vault. HTTPS enforced. HMAC webhook signatures for event delivery.

developers.apideck.com provides the full unified API reference (all categories, all endpoints), Vault integration guide (hosted OAuth flow), webhook configuration, passthrough API documentation, and getting started tutorial. Documentation quality is excellent with working examples. Getting started requires an Apideck account (free developer plan with 3 consumers). API playground available in the Apideck Console. OpenAPI spec downloadable for code generation. SDKs: Node.js, Python, PHP, Ruby, Go. Community support via Apideck Discord and support portal.