Find the API documentation and describe your integration to get help with the right part of the platform.
This guide is for developers and store owners who want to connect an external system or build their own store frontend. The API is available for stores with an active Abicart subscription, including Go, Plus, and Pro. It does not automatically provide access to features or external services that the store lacks.
1. Start with a demo and the API documentation
Create a free demo store if you first want to explore the admin and the platform's workflow. Available demo features and production agreements are not the same thing. Use separate test data and check what each call does before connecting to a live store.
On Abicart's developer portal you will find an introduction, authentication, methods, objects, selection, and error handling. The API's main interface is JSON-RPC 2.0 over HTTP. You can call it from environments like PHP, .NET, or others that can send the documented calls; your integration does not need to be in the same programming language as the platform.
2. Distinguish between frontend, admin, and integration
To change an existing theme's appearance: start with the theme's settings, HTML, and CSS. This does not mean that custom PHP or .NET code runs within Abicart's server environment.
To build your own frontend: check the public API methods and how customer login, shopping cart, and ordering are handled.
To manage orders, customers, or products administratively: use documented administrator authentication and the methods intended for the task.
The API has both read and write methods. Never assume a connection is harmless just because you call it a test or use an AI tool. Administrator tokens can grant extensive permissions. Store them on a secure server, not in public HTML, JavaScript in the store, screenshots, or a regular support ticket.
3. Describe order events and AI connections concretely
If you want to react to new or changed orders, distinguish between reading orders regularly via the API (polling) and receiving a push event. Polling requires correct selection, pagination, change handling, and protection against processing the same order multiple times. An API method for reading orders does not automatically mean there is a general webhook for any recipient.
Describe which event you need, which system will receive it, and whether you need to read or modify data. This allows the correct integration path and any special event support to be checked for your specific solution. An AI tool that requires an MCP needs a compatible MCP connection or a special integration; the API documentation itself is not an MCP server or a promise of a ready-made connection.
4. Contact support with the right information
Log in to the relevant store's admin and open the contact/customer service function in the user menu. You can also contact hello@abicart.se. Provide:
Store ID and whether it concerns a demo or production environment.
What you want to achieve and which external system is to be connected.
Whether the question concerns a theme, the API, order events, permissions, or an existing integration.
The relevant method name, time, error code, and a minimal example with test values, without personal data or secrets.
If the question concerns migration to Abicart, describe the current platform, what data needs to be moved, and which external connections must work. Distinguish this from an API error that has already occurred.
Quick start
Explore the demo and the developer portal.
Choose the right path: theme customization, custom front end, or administrative integration.
Check authentication and which calls perform write operations.
Contact support with the store ID and a specific, anonymized problem.
Subscription and responsibility
The API is available with an active Abicart subscription. Features, external services, and custom adaptations may have separate requirements or agreements. The developer needs to handle security, test data, and error handling in their own solution.