On this page
Every online store relies on other software. Payments go through a payment provider. Parcels go out with a courier. Sales end up in accounting software. Stock may live in a warehouse system. Something has to carry information between all of them, so you are not copying orders from one screen to another by hand. That something is usually an API.
What an API is
API stands for application programming interface. It is a set of rules that lets one piece of software ask another for information, or ask it to do something, and get a reply.
A restaurant is a handy way to picture it. You do not walk into the kitchen and cook your own meal. You tell a server what you want, choosing from a menu of things the kitchen can make. The server takes the order to the kitchen and brings back your food, or comes back to say the dish is not available. An API is the menu and the server together: it lists what you can ask for, carries the request and returns the answer.
You use APIs every day without seeing them. When an app lets you sign in with an account you already have, shows a map, takes a card payment or displays the weather, it is very likely asking another service for that through an API.
How a request and a response work
Most store APIs work over the web, much like a browser loading a page. Each exchange has two halves.
The request. One program sends a message to an address the API provides. The message says what it wants, for example a list of today's orders, or a new stock count for a product. It also says what kind of action it is. The common ones are reading information, creating something new, updating something and deleting something.
The response. The API checks the request, does the work and replies. The reply includes a status that says whether it worked, and usually some data, most often in a format called JSON. JSON is plain text arranged as labeled fields, such as an order number, the customer's name, the items and the total, so both people and programs can read it.
If something goes wrong, the response says so: the item does not exist, a required field is missing, or the caller is not allowed to do that. A well-built integration reads those replies and acts on them instead of failing silently.
Keys and tokens: who is asking
An API that can read your orders or change your prices has to know who is asking. That is what keys and tokens are for.
- An API key is a long secret string that identifies an app. The app sends it with each request.
- An access token does a similar job. It often lasts for a limited time and is usually issued after someone signs in or approves an app.
- Permissions, sometimes called scopes, decide what a key or token is allowed to do. An app that prints shipping labels might be able to read orders but not change prices.
Treat keys like passwords:
- Give each app only the permissions it needs.
- Never paste a key into an email, a chat or a public code repository.
- Remove keys for apps you no longer use.
- If you think a key has leaked, revoke it and create a new one.
Webhooks: being told instead of asking
A plain API call is like phoning a shop to ask whether your order is ready. You get an answer, but only when you call. If you need to know quickly, you end up calling again and again.
A webhook turns this around. You give the store an address and choose the events you care about, such as a new order, a refund or a product selling out. When one of those events happens, the store sends a message to that address straight away.
Webhooks are what make integrations feel instant. A warehouse system can start packing an order moments after it is placed, without checking for new orders over and over. Because the receiving address is open to the internet, a careful webhook receiver checks a signature on each message to confirm it really came from the store.
Rate limits: sharing fairly
An API is shared by many apps at once, so most APIs cap how many requests one app can send in a given period. This is a rate limit. It protects the service from overload, whether from a bug that sends the same request in a loop or from a deliberate attack.
When an app goes over the limit, the API replies with an error asking it to slow down, and often says how long to wait. Well-written apps wait and try again, spread large jobs out over time, and ask for many records in one request rather than one record at a time.
What a store uses an API for
Here are some of the most common jobs:
- Stock sync. If you sell in more than one place, such as your own store, a marketplace and a physical shop, an API keeps stock counts matching so you do not sell the same last item twice.
- Shipping labels. When an order comes in, a shipping app reads the address and parcel details, buys a label from the courier and sends the tracking number back to the order, so the buyer can follow it.
- Accounting. Orders, refunds, taxes and fees flow into your accounting software, so your books stay current without retyping.
- Bulk updates. Changing prices or descriptions across many products at once, from a spreadsheet or another system.
- Customer and marketing tools. Sharing order history with an email or support tool, so messages are based on what a buyer actually bought.
- Custom storefronts. Some businesses build their own website or app and use the store's API behind it for products, carts and checkout. This is often called headless commerce.
Do you need to write code?
Not always. Many integrations come as ready-made apps that you install and approve, and the app handles the API calls for you. There are also no-code tools that connect services by letting you pick a trigger, such as a new order, and an action, such as adding a row to a spreadsheet.
If you want something custom, a developer will usually read the API documentation, create a key with only the permissions the job needs, build and test the integration on a test store, and only then connect it to your live store.
Where to start
Begin with the task that eats the most of your time each week, such as typing orders into your accounting software or updating stock in two places. That is usually the first job worth handing to an API.
Tanqory has an API, and its developer documentation is at docs.tanqory.com. It is a good place to send a developer, or to see for yourself what a store's API can reach.



