Overview

We are trying to develop a page for the daily cash count up at the end of the night - and to work out the float that is needed.

Hello! Thank you for your post. Unfortunately, we don't have "cash" and "charge" parameters in the API. It would be helpful if you could share me a use case of cash and charge parameters.

Hello! Due to our API’s restrictions that disallow direct calls from the browser, please utilize a backend proxy such as Nginx or a similar tool in their local environment. [References] https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Hello! I seem to be getting 403 Forbidden wwhen I'm trying to get a receipt. These started trickling in 17th Nov about 1300H UTC in a few of my requests, now all are showing Forbidden for any bearer token. Would there be a rate limit IP ban? Works same requets from other IPs and I'm well below the 300 requests/300 seconds limit. I look out for 429 (too many requests) but didn't get any. If it is an IP ban, how long? and what are the new rate limits? Thanks!

Loverse is obviously tracking the Cash amount - and the amount the receipt is for - as you can see here, the customer got 20p back... But the API - does not return the cash amount anywhere - just the money_amount... Where is this "cash" and "change" amount being stored?

I saw a discussion from 2022 asking the same thing, but it seems nothing has changed. Honestly, it's really frustrating for those of us who work with Loyverse — there are so many things we could automate or improve, but the API is still very limited. Are there any plans to expand its capabilities soon?

Hello, I hope someone can help me resolve this issue. I am trying to use the API with an access token, but when I make the request, I get a 401 CORS ‘Access-Control-Allow-Origin’ error, and the details say “Access token is not valid.” I am working in Angular. Thank you in advance.

I just realized that the link in my OP is only available to logged in N8N users, sorry about that! ... still learning Here's the public link with some more information: https://n8n.io/workflows/10420-automated-daily-financial-analysis-from-loyverse-pos-with-google-sheets-and-email/ Any feedback is highly welcome! I also understand that for a Loyverse user new to N8N the initial setup required to make this workflow work with your POS can be overwhelming. You think you know your numbers because you check them monthly/weekly? You will be surprised how much you can learn from daily reports boiled down to the metrics actually relevant to your business! ... or maybe you're thinking, 'Does it really matter how many of my vegan food customers drink Gin tonics?' And honestly, you're probably right! But why not just track it anyway? Who knows, maybe one day you'll be lying awake at 3 AM dying to know the answer! The workflow can be easily adjusted to capture all this random data in Google Sheets, which is great because trying to pull and connect those specific data points from the standard Loyverse reports later on is a huge pain. Invest 20-30 minutes in setting up and fine-tuning this free add-on for your POS ... store all data combined in a single spreadsheet. This provides the perfect foundation, both retrospectively and for the future, should you, a government agency, or your partners want to take a closer look at your figures! ..send yourself or your responsible employee a daily report that briefly and concisely summarizes the most important daily data for quick operational decisions (see screenshot of my report below)... or build a report that goes into detail on key performance indicators specific to your business. You need the "integrations" subscription since API access is required but the N8N template is available free. Anyone who needs help with setting this up or customizing it, feel free to get in touch

Hello. Could you give me a your request and response body?

Amazing! Thank you!

Hi everyone, I have created a free Loyverse workflow template that exports daily sales to a google sheet and sends a report via email the next day. You can access the workflow here: https://creators.n8n.io/workflows/10420 There are some metrics defined already like NOP and rolling 30 days NOP or you just add your own. It also come very handy to have numbers that are available through the internal loyverse reports but spread between different pages in the backend / different export files combined in just one Spreadsheet.

This would be a required feature for us too: Online orders need to be fulfilled by the kitchen and not just archived in the back office. Online orders should be treated by the POS just like any order entered by the staff, and sent/split to the configured KDS and/or printers. The POS/KDS would also ideally display an appropriate order source tag, and allowing the staff to accept/reject the order would be nice-to-have. Expecting restaurants to purchase yet another integration/service/hardware specific to online orders nowadays is antiquated. Loyverse appears to have done such a great job with every other aspect of the systems and API, it would be amazing if this could be added too. And if I could add one more thing to the API wishlist it would be Loyalty, so that online orders can share (contribute to and redeem) the same rewards.

Hi i posted

For Variant_id "6a1ba6c5-5495-4884-ac4a-670785802281" Only show one Store "8a8cf25e-d5a3-4210-a8c6-09264d3a916f" in invenrtory

Hello. Could you post screenshots that show how the number of stock is different between the Back office and API? For your information, both variant_id and store_id are in UUID format, such as f81d4fae-7dec-11d0-a765-00a0c91e6bf6 (example).

I understand that each variant_id can be in each store. For example: variant_id = 1 store_id = 1 variant_id = 1 store_id = 2 variant_id = 1 store_id = 3

I'm reading the inventory_levels object the variables variant_id store_id in_stock updated_at I'm retrieving them correctly, but the stock doesn't match the actual stock. How do I get the actual stock? There's only one variant_id for each item. Can you help me?

Hello. Thank you for your question. This problem is occurring because the API endpoint and the structure of the JSON payload you are sending do not match. The API is reporting that object.store_id is missing because it expects to find the store_id field at the outermost (top) level of the JSON you sent. Currently, your store_id is inside an array named receipts, which is why the API cannot find it. Cause of the Problem The URL you are sending to is https://api.loyverse.com/v1.0/receipts. This endpoint is for creating a single receipt and expects a single receipt object as the request body (e.g., { "store_id": "...", "receipt_date": "...", ... }). However, the payload you are sending is in the format {"receipts": [ ... ]}. This is the format for the batch endpoint, which is used to create multiple receipts at once. Solution Continue using the POST /v1.0/receipts endpoint, but remove the receipts array wrapper from your payload. Send the single receipt object directly.

Hello Loyverse Community, I am trying to create a new receipt using the v1.0 API from a Node.js application, but I am stuck on a persistent 400 Bad Request error. The API response is always the same: { "errors": [ { "code": "MISSING_REQUIRED_PARAMETER", "details": "Field must be set", "field": "object.store_id" } ] } The strange thing is that I am 100% sure the store_id is present in my request payload. I have even hardcoded the values directly into my code to ensure there are no issues with environment variables, but the error persists. Here is a simplified version of my Node.js code using fetch: // My credentials are hardcoded for this test const LOYVERSE_API_TOKEN = "77e5158ae30642a295f1c7a6a0e057c6"; // This is a valid token const STORE_ID = "d88730d4-82ef-4585-844a-c665ca2b3f2a"; // This is my correct Store ID const EMPLOYEE_ID = "d88730d4-82ef-4585-844a-c665ca2b3f2a"; // I'm using the Store ID as Employee ID // The payload I'm sending const payload = { receipts: [{ receipt_date: new Date().toISOString(), store_id: STORE_ID, // As you can see, the store_id is set here employee_id: EMPLOYEE_ID, receipt_type: 'SALE', total_money: 17000, line_items: [{ variant_id: "b0fe8eb7-9028-4608-8774-c7e6014e478a", // Example: Hawaiana Grande quantity: 1, price: 17000 }], payments: [{ payment_type_id: "ba69d7c5-cce1-4192-89d3-0d8e92288ed9", // Cash amount: 17000, paid_at: new Date().toISOString() }] }] }; // The API call fetch('https://api.loyverse.com/v1.0/receipts', { method: 'POST', headers: { 'Authorization': `Bearer ${LOYVERSE_API_TOKEN}`, 'Content-Type': 'application/json' }, body: JSON.stringify(payload) }) .then(res => res.json()) .then(json => console.log(json)); Things I have already tried: Confirmed my STORE_ID is correct by checking the URL in my Back Office. Generated brand new Personal Access Tokens. I know the token is authenticating correctly because a GET request to /receipts with cURL returns a 402 PAYMENT_REQUIRED error, not a 401 UNAUTHORIZED error. Hardcoded all credentials to rule out any .env file reading issues. Checked my code files for any invisible characters or encoding problems. My question is: Why would the API claim store_id is missing when it is clearly present and hardcoded in the JSON payload? Could this be a known issue or something specific to my account configuration? Thank you in advance for any help or ideas.

Hi @Yasuaki, thank you for your reply. I understand that it’s not possible directly through the Loyverse API at the moment. Is there any other way to handle this so that the orders created from my app can appear in the KDS or within Loyverse? For example, through an indirect integration, webhooks, a middleware service, or some kind of POS synchronization? Any suggestions would be very helpful. Thanks!

Hello! Sorry for delay. But the temporary webhook delay was already sorted out. Thank you for being patient.

Updates: ours seems ok since 10 hours ago.

Still working really slow for me... hours delays for webhook to fire?

We have been having these issues as well since yesterday. first with 1 merchant now with other merchants as well. We are now forced to do manual synchronization and hope Loyverse Tech can fix this soon.