Integration
Connect Bidledger and Loyverse
When something happens in Bidledger or Loyverse, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Bidledger and Loyverse to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Bidledger and Loyverse can do together
From Bidledger to Loyverse
When New tender (polling) in Bidledger
then Create or Update Category in Loyverse
From Loyverse to Bidledger
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Bidledger and Loyverse
Triggers and actions 4 triggers · 51 actions
- New tender (polling)
Fires when a new EU tender notice appears in the daily-rebuilt open-tenders index.
- Find tenders by country
Find all open EU tenders for a given country (ISO3 code).
- Find tenders by CPV division
Find all open EU tenders within a given CPV sector division.
- List countries
List EU countries with their current count of open tenders.
- List CPV codes
List every CPV procurement code in use, with its label and open-tender count.
- List sectors
List the CPV sector divisions with their current count of open tenders.
- List tenders
List the full compact index of all currently open EU tenders.
- Customer Update
Triggers when a customer is updated.
- Items Update
Triggers when an item is updated.
- Receipts Update
Triggers when a receipt gets created or updated.
- Create or Update Category
Creates or Updates a single category.
- Create or Update Discount
Creates or Updates a single discount.
- Create or Update Modifier
Creates or Updates a modifier.
- Create or Update POS Device
Creates or Updates a single POS device.
- Create or Update Receipts
Creates a receipt
- Create or Update Single Customer
Creates or Updates a Single Customer.
- Create or Update Single Item
- Create or Update Supplier
Creates or Updates a single supplier.
- Create or Update Tax
Creates or Updates a tax.
- Create Refund Receipt
Creates a refund receipt. When using the refund API you should take into account these notes: - At the moment refund API allows creating a refund only for sales receipts which are paid by a single payment. For any attempt to make a refund for a sales receipt that has more than one payment Loyverse API will respond with an error. - Refund API doesn't support a refund of receipts paid by integrated payments using Loyverse POS app (e.g. iZettle, Sumup, etc.). For this purpose please use Loyverse POS app. - If a refund is created successfully, it will cause a restock of items specified in a refund receipt.
- Delete Singe Item
Deletes a single item.
- Delete Single Category
Deletes a single category.
- Delete Single Customer
Deletes a single customer.
- Delete Single Discount
Deletes a single discount.
- Delete Single Modifier
Deletes a single Modifier.
- Delete Single POS Device
Deletes a single POS Device.
- Delete Single Supplier
Deletes a single supplier.
- Delete Single Tax
Deletes a single tax.
- Delete Single Variant
Deletes a single variant.
- Get List of Categories
Get list of all categories.
- Get List of Customers
Get list of Customers
- Get List of Discounts
Returns discounts, most recently created first.
- Get List of Employees
Gets a list of employees.
- Get List of Items
Get list of items
- Get List of Payment Types
Get list of Payment Types
- Get List of POS Devices
The list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first
- Get List of Stores
Get list of stores
- Get List of Suppliers
Gets a list of suppliers.
- Get List of Taxes
Get list of taxes
- Get List of Variants
Get lists of item variants.
- Get Merchant Information
Returns the business profile of the connected Loyverse merchant account.
- Get Single Category
Get Single Category.
- Get Single Customer
Get Single Customer
- Get Single Discount
Gets a single discount.
- Get Single Employee
Gets a single employee.
- Get Single Item
Get single item
- Get Single Modifier
Gets a single modifier.
- Get Single Payment Type
Fetches a payment type by ID. An error occurs if the payment type is not found.
- Get Single POS Device
Fetches a POS device by ID. An error occurs if the POS device is not found.
- Get Single Receipt
Get a single Receipt.
- Get Single Store
Get Single Store
- Get Single Supplier
Fetches a supplier by ID. An error occurs if the supplier is not found.
- Get Single Tax
Gets a single tax.
- Get Single Variant
Gets single item variant.
- Update Inventory Levels for Items
Batch updates Inventory Levels for Item Variants.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Bidledger
Bidledger to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Bidledger to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Bidledger to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Bidledger to Google SheetsGoogle Sheets
Bidledger to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Bidledger to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Loyverse
Google Drive to LoyverseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LoyverseActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Bidledger and Loyverse, answered
What can start an automation from Bidledger?
Any of Bidledger's 1 trigger in the catalog, including New tender (polling). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Loyverse when something happens in Bidledger?
Any of Loyverse's 45 actions, including Create or Update Category, Create or Update Discount, Create or Update Modifier and Create or Update POS Device. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Loyverse to Bidledger?
Yes. When something happens in Loyverse, your agent can act in Bidledger too. This page covers both directions: Loyverse's triggers and Bidledger's actions are listed here as well.
Do I have to build a connector for Bidledger or Loyverse?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.