apideck-libraries

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

Amazon Seller Central integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Amazon Seller Central. Routes through Apideck with serviceId "amazon-seller-central".

GitHub integration via Apideck's Issue Tracking unified API — same methods work across every connector in Issue Tracking, switch by changing `serviceId`. Use when the user wants to read, write, or comment on tickets and issues in GitHub. Routes through Apideck with serviceId "github".

SAP SuccessFactors integration via Apideck's HRIS, ATS unified API — same methods work across every connector in HRIS, ATS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in SAP SuccessFactors. Routes through Apideck with serviceId "sap-successfactors".

Fourth integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Fourth. Routes through Apideck with serviceId "fourth".

Paylocity integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Paylocity. Routes through Apideck with serviceId "paylocity".

JumpCloud integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in JumpCloud. Routes through Apideck with serviceId "jumpcloud".

Guide for migrating from direct third-party API integrations to Apideck's unified API. Use when a user wants to replace their existing Salesforce, HubSpot, QuickBooks, Xero, or other direct API integrations with Apideck, or when consolidating multiple integrations into a single unified layer.

CharlieHR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in CharlieHR. Routes through Apideck with serviceId "charliehr".

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".

Zendesk Sell integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Zendesk Sell. Routes through Apideck with serviceId "zendesk-sell".

UKG Pro integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in UKG Pro. Routes through Apideck with serviceId "ukg-pro".