Your mobile app, accounting system, partners and AI assistants all work with your shop through an API. If the shop has no API, or the one it has lacks operations, we will design it, build it and document it. You usually don’t have to move the website for this: the API takes data from the shop database and from the accounting system.
We agree the list of operations with you before work starts. Below is what shops need most often.
Products, categories, attributes, prices and promotions. Stock levels for each warehouse.
Create an order, check its status, show a customer’s purchase history.
Products, prices and stock come from accounting, and orders go back the other way. We have worked with 1C:Enterprise for many years. It is our main line of work.
Each API client has its own key and its own permissions. Request rates are limited, and every call is logged.
Every operation is described with example requests and responses, so another team can connect without our help.
On the same API we build an MCP server, through which Claude, ChatGPT and other assistants fill a basket in your shop.
About MCP for shops →The app shows the same prices and stock as the website and places orders into the same database.
Stock on the website is updated from the accounting system, and sold items are written off there without manual entry.
A supplier or marketplace gets access only to its own operations, with its own key.
Through an MCP server the assistant finds products and builds the basket. The customer pays for the order on your website.
We look at where the data lives: the shop database, the accounting system, external services. Then we list who needs which operations.
We agree the operations and the response format with you. Your team can start integrating from the specification alone.
We build the API with automated tests and check it in a test environment on your data.
We install it on your server or on ours in the EU, hand over the documentation and keep supporting it.
A platform API covers the common tasks. You need your own when data is spread across the website, accounting and the warehouse, or when the platform lacks an operation you need. Sometimes a thin layer on top of the platform API is enough. We will tell you which fits after the discovery stage.
Elixir and Phoenix. The API returns JSON, and we write the documentation in OpenAPI format, which most developer tools can read.
Rights to the code are set out in the contract.
We give a price after the discovery stage. It depends on how many systems need connecting and how many operations to expose.
Tell us which platform your shop runs on, which systems need connecting and who will use the API.
