← all publishers

apideck-libraries

@apideck-libraries source repo

Report this profile Claim this profile

• 169 skills
• 0 followers
• 1 week ago last updated

1. ▌
   Intercom · apideck-libraries bundle

   Intercom via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Intercom's native API. Use when the user wants to call Intercom (no unified API resource mapping). Routes through Apideck with serviceId "intercom".
   1 install
2. ▌
   Jobadder · apideck-libraries bundle

   JobAdder integration via Apideck's ATS unified API — same methods work across every connector in ATS, switch by changing `serviceId`. Use when the user wants to read, write, or sync jobs, applicants, and applications in JobAdder. Routes through Apideck with serviceId "jobadder".
   1 install
3. ▌
   Kashflow · apideck-libraries bundle

   Kashflow integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Kashflow. Routes through Apideck with serviceId "kashflow".
   1 install
4. ▌
   Loket Nl · apideck-libraries bundle

   Loket.nl 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 Loket.nl. Routes through Apideck with serviceId "loket-nl".
   1 install
5. ▌
   Lucca Hr · apideck-libraries bundle

   Lucca 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 Lucca. Routes through Apideck with serviceId "lucca-hr".
   1 install
6. ▌
   Netsuite · apideck-libraries bundle

   NetSuite integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in NetSuite. Routes through Apideck with serviceId "netsuite".
   1 install
7. ▌
   Onedrive · apideck-libraries bundle

   OneDrive integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in OneDrive. Routes through Apideck with serviceId "onedrive".
   1 install
8. ▌
   Onelogin · apideck-libraries bundle

   OneLogin 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 OneLogin. Routes through Apideck with serviceId "onelogin".
   1 install
9. ▌
   Personio · apideck-libraries bundle

   Personio 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 Personio. Routes through Apideck with serviceId "personio".
   1 install
10. ▌
    Sesamehr · apideck-libraries bundle

    Sesame HR via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Sesame HR's native API. Use when the user wants to call Sesame HR (no unified API resource mapping). Routes through Apideck with serviceId "sesamehr".
    1 install
11. ▌
    Shopware · apideck-libraries bundle

    Shopware 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 Shopware. Routes through Apideck with serviceId "shopware".
    1 install
12. ▌
    Shortcut · apideck-libraries bundle

    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".
    1 install
13. ▌
    Silae Fr · apideck-libraries bundle

    Silae 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 Silae. Routes through Apideck with serviceId "silae-fr".
    1 install
14. ▌
    Workable · apideck-libraries bundle

    Workable integration via Apideck's ATS unified API — same methods work across every connector in ATS, switch by changing `serviceId`. Use when the user wants to read, write, or sync jobs, applicants, and applications in Workable. Routes through Apideck with serviceId "workable".
    1 install
15. ▌
    Zoho Crm · apideck-libraries bundle

    Zoho CRM 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 Zoho CRM. Routes through Apideck with serviceId "zoho-crm".
    1 install
16. ▌
    Picqer · apideck-libraries bundle

    Picqer 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 Picqer. Routes through Apideck with serviceId "picqer".
    1 install
17. ▌
    Remote · apideck-libraries bundle

    Remote 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 Remote. Routes through Apideck with serviceId "remote".
    1 install
18. ▌
    Rillet · apideck-libraries bundle

    Rillet integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Rillet. Routes through Apideck with serviceId "rillet".
    1 install
19. ▌
    Sdworx · apideck-libraries bundle

    SD Worx 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 SD Worx. Routes through Apideck with serviceId "sdworx".
    1 install
20. ▌
    Stripe · apideck-libraries bundle

    Stripe integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Stripe. Routes through Apideck with serviceId "stripe".
    1 install
21. ▌
    Tiktok · apideck-libraries bundle

    TikTok Shop 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 TikTok Shop. Routes through Apideck with serviceId "tiktok".
    1 install
22. ▌
    Trinet · apideck-libraries bundle

    TriNet 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 TriNet. Routes through Apideck with serviceId "trinet".
    1 install
23. ▌
    Adp Run · apideck-libraries bundle

    RUN Powered by ADP 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 RUN Powered by ADP. Routes through Apideck with serviceId "adp-run".
    1 install
24. ▌
    Bol Com · apideck-libraries bundle

    bol.com 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 bol.com. Routes through Apideck with serviceId "bol-com".
    1 install
25. ▌
    Clickup · apideck-libraries bundle

    ClickUp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to ClickUp's native API. Use when the user wants to call ClickUp (no unified API resource mapping). Routes through Apideck with serviceId "clickup".
    1 install
26. ▌
    Dropbox · apideck-libraries bundle

    Dropbox integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in Dropbox. Routes through Apideck with serviceId "dropbox".
    1 install
27. ▌
    Hubspot · apideck-libraries bundle

    HubSpot 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 HubSpot. Routes through Apideck with serviceId "hubspot".
    1 install
28. ▌
    Liantis · apideck-libraries bundle

    Liantis 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 Liantis. Routes through Apideck with serviceId "liantis".
    1 install
29. ▌
    Magento · apideck-libraries bundle

    Magento 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 Magento. Routes through Apideck with serviceId "magento".
    1 install
30. ▌
    Paychex · apideck-libraries bundle

    Paychex 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 Paychex. Routes through Apideck with serviceId "paychex".
    1 install
31. ▌
    Sympa · apideck-libraries bundle

    Sympa 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 Sympa. Routes through Apideck with serviceId "sympa".
    1 install
32. ▌
    Acerta · apideck-libraries bundle

    Acerta 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 Acerta. Routes through Apideck with serviceId "acerta".
    1 install
33. ▌
    Banqup · apideck-libraries bundle

    banqUP integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in banqUP. Routes through Apideck with serviceId "banqup".
    1 install
34. ▌
    Copper · apideck-libraries bundle

    Copper 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 Copper. Routes through Apideck with serviceId "copper".
    1 install
35. ▌
    Digits · apideck-libraries bundle

    Digits integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Digits. Routes through Apideck with serviceId "digits".
    1 install
36. ▌
    Fourth · apideck-libraries bundle

    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".
    1 install
37. ▌
    Github · apideck-libraries bundle

    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".
    1 install
38. ▌
    Gitlab · apideck-libraries bundle

    GitLab 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 GitLab. Routes through Apideck with serviceId "gitlab".
    1 install
39. ▌
    Holded · apideck-libraries bundle

    Holded 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 Holded. Routes through Apideck with serviceId "holded".
    1 install
40. ▌
    Linear · apideck-libraries bundle

    Linear 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 Linear. Routes through Apideck with serviceId "linear".
    1 install
41. ▌
    Mollie · apideck-libraries bundle

    Mollie via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Mollie's native API. Use when the user wants to call Mollie (no unified API resource mapping). Routes through Apideck with serviceId "mollie".
    1 install
42. ▌
    Monday · apideck-libraries bundle

    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".
    1 install
43. ▌
    Namely · apideck-libraries bundle

    Namely 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 Namely. Routes through Apideck with serviceId "namely".
    1 install
44. ▌
    Notion · apideck-libraries bundle

    Notion via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Notion's native API. Use when the user wants to call Notion (no unified API resource mapping). Routes through Apideck with serviceId "notion".
    1 install
45. ▌
    Payfit · apideck-libraries bundle

    PayFit 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 PayFit. Routes through Apideck with serviceId "payfit".
    1 install
46. ▌
    Keka · apideck-libraries bundle

    Keka HR 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 Keka HR. Routes through Apideck with serviceId "keka".
    1 install
47. ▌
    Myob · apideck-libraries bundle

    MYOB integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in MYOB. Routes through Apideck with serviceId "myob".
    1 install
48. ▌
    Odoo · apideck-libraries bundle

    Odoo integration via Apideck's CRM, Accounting unified API — same methods work across every connector in CRM, Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Odoo. Routes through Apideck with serviceId "odoo".
    1 install
49. ▌
    Okta · apideck-libraries bundle

    Okta 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 Okta. Routes through Apideck with serviceId "okta".
    1 install
50. ▌
    Wave · apideck-libraries bundle

    Wave integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Wave. Routes through Apideck with serviceId "wave".
    1 install
51. ▌
    Xero · apideck-libraries bundle

    Xero integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Xero. Routes through Apideck with serviceId "xero".
    1 install
52. ▌
    Yuki · apideck-libraries bundle

    Yuki integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Yuki. Routes through Apideck with serviceId "yuki".
    1 install
53. ▌
    Asana · apideck-libraries bundle

    Asana via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Asana's native API. Use when the user wants to call Asana (no unified API resource mapping). Routes through Apideck with serviceId "asana".
    1 install
54. ▌
    Attio · apideck-libraries bundle

    Attio 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 Attio. Routes through Apideck with serviceId "attio".
    1 install
55. ▌
    Ciphr · apideck-libraries bundle

    CIPHR 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 CIPHR. Routes through Apideck with serviceId "ciphr".
    1 install
56. ▌
    Close · apideck-libraries bundle

    Close 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 Close. Routes through Apideck with serviceId "close".
    1 install
57. ▌
    Hibob · apideck-libraries bundle

    Hibob 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 Hibob. Routes through Apideck with serviceId "hibob".
    1 install
58. ▌
    Kenjo · apideck-libraries bundle

    Kenjo 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 Kenjo. Routes through Apideck with serviceId "kenjo".
    1 install
59. ▌
    Lever · apideck-libraries bundle

    Lever integration via Apideck's ATS unified API — same methods work across every connector in ATS, switch by changing `serviceId`. Use when the user wants to read, write, or sync jobs, applicants, and applications in Lever. Routes through Apideck with serviceId "lever".
    1 install
60. ▌
    Nmbrs · apideck-libraries bundle

    Visma Nmbrs 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 Visma Nmbrs. Routes through Apideck with serviceId "nmbrs".
    1 install
61. ▌
    Act · apideck-libraries bundle

    Act 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 Act. Routes through Apideck with serviceId "act".
    1 install
62. ▌
    Box · apideck-libraries bundle

    Box integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in Box. Routes through Apideck with serviceId "box".
    1 install
63. ▌
    Wix · apideck-libraries bundle

    Wix 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 Wix . Routes through Apideck with serviceId "wix".
    1 install
64. ▌
    Afas · apideck-libraries bundle

    AFAS Software 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 AFAS Software. Routes through Apideck with serviceId "afas".
    1 install
65. ▌
    Deel · apideck-libraries bundle

    Deel 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 Deel. Routes through Apideck with serviceId "deel".
    1 install
66. ▌
    Ebay · apideck-libraries bundle

    eBay 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 eBay. Routes through Apideck with serviceId "ebay".
    1 install
67. ▌
    Etsy · apideck-libraries bundle

    Etsy 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 Etsy. Routes through Apideck with serviceId "etsy".
    1 install
68. ▌
    Folk · apideck-libraries bundle

    Folk 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 Folk. Routes through Apideck with serviceId "folk".
    1 install
69. ▌
    Jira · apideck-libraries bundle

    Jira 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 Jira. Routes through Apideck with serviceId "jira".
    1 install