Can HumDay connect to Apideck POS?

Yes. HumDay reads Apideck POS's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 46 operations are documented.

Do I need to write code to automate Apideck POS?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Apideck POS account.

What can HumDay do in Apideck POS?

28 of the 46 documented operations change something in Apideck POS, and 18 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Apideck POS account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Apideck POS is held behind that approval.

Automate Apideck POS

HumDay reads Apideck POS’s own published API description and derives 46 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Apideck POS is

Welcome to the POS API. You can use this API to access all POS API endpoints. ## Base URL The base URL for all API requests is `https://unify.apideck.com` We also provide a [Mock API](https://developers.apideck.com/mock-api) that can be used for testing purposes: `https://mock-api.apideck.com` ## Headers Custom headers that are expected as part of the request. Note that [RFC7230](https://tools.iet

API host: unify.apideck.com

What HumDay can do in Apideck POS

28 documented operations change something in Apideck POS.

POSTCreate Item/pos/items
POSTCreate Order/pos/orders
POSTCreate Payment/pos/payments
POSTCreate Order Type/pos/order-types
DELETEDelete Item/pos/items/{id}
PATCHUpdate Item/pos/items/{id}
DELETEDelete Order/pos/orders/{id}
PATCHUpdate Order/pos/orders/{id}
DELETEDelete Payment/pos/payments/{id}
PATCHUpdate Payment/pos/payments/{id}
POSTCreate Tender/pos/tenders
POSTCreate Location/pos/locations
POSTCreate Merchant/pos/merchants
POSTCreate Modifier/pos/modifiers
POSTPay Order/pos/orders/{id}/pay
POSTCreate Modifier Group/pos/modifier-groups
DELETEDelete Order Type/pos/order-types/{id}
PATCHUpdate Order Type/pos/order-types/{id}
DELETEDelete Tender/pos/tenders/{id}
PATCHUpdate Tender/pos/tenders/{id}
DELETEDelete Location/pos/locations/{id}
PATCHUpdate Location/pos/locations/{id}
DELETEDelete Merchant/pos/merchants/{id}
PATCHUpdate Merchant/pos/merchants/{id}
DELETEDelete Modifier/pos/modifiers/{id}
PATCHUpdate Modifier/pos/modifiers/{id}
DELETEDelete Modifier Group/pos/modifier-groups/{id}
PATCHUpdate Modifier Group/pos/modifier-groups/{id}

What HumDay can read from Apideck POS

These are the operations a schedule or a trigger can watch.

GETList Items/pos/items
GETList Orders/pos/orders
GETList Payments/pos/payments
GETList Order Types/pos/order-types
GETGet Item/pos/items/{id}
GETGet Order/pos/orders/{id}
GETGet Payment/pos/payments/{id}
GETList Tenders/pos/tenders
GETList Locations/pos/locations
GETList Merchants/pos/merchants
GETList Modifiers/pos/modifiers
GETList Modifier Groups/pos/modifier-groups
GETGet Order Type/pos/order-types/{id}
GETGet Tender/pos/tenders/{id}
GETGet Location/pos/locations/{id}
GETGet Merchant/pos/merchants/{id}
GETGet Modifier/pos/modifiers/{id}
GETGet Modifier Group/pos/modifier-groups/{id}

How automating Apideck POS works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Apideck POS account.
Grant access, then go live. You approve the specific Apideck POS operations it may use — and only those.