Agora Connector ✨ New and recommended

⭐ Recommended method for connecting Agora to haddock

haddock Connector is a small program that is installed on your restaurant computer and automatically sends sales from Agora to haddock. Once configured, it runs by itself and you do not have to do anything else.

📄 Download full PDF guide

What do I need before starting?

• The computer where Agora is installed must be turned on and running Agora.
• You need access to that computer to install the program. If you are not physically at the venue, you can ask someone there to give you remote access with AnyDesk or TeamViewer - these are free programs that let you see and control the computer from another location.
• Have the Agora API Token handy: it does not exist out of the box, it is the key you define when enabling the integration module in the "Before installing - set up Agora" section (usually done by your Agora reseller).
• And the haddock authentication code (you will find it in the haddock web app, under Restaurant settings > My integrations > Agora Connector).

💡 Tip: If you do not have all the details or do not feel confident doing the installation, the easiest option is to send everything to your Agora reseller or IT technician. Share the PDF guide and the haddock authentication code with them - they will be able to do the installation and setup remotely without you having to handle anything technical.

Before installing - set up Agora

The connector reads sales through Agora's integration HTTP API. Before installing it, that module has to be enabled and the key the connector will use (the API Token) defined. You need Agora 6.0.6 or later and an Agora license that includes the Integration Services module (Módulo de Servicios de Integración) - your reseller enables it.

✅ If something is already set up, do not change it: write down the value and move on to the next step. Steps B and C are look-ups only, they change nothing in Agora.

A - Enable the module and get the API Token

1. In the Agora Monitor (the server, not the POS), open Herramientas > Activar Módulos Adicionales.

   
   

   
   
2. Check the Activar Módulo de Servicios de Integración box in the left-hand column.

   
   

   
   
3. Click Configurar Servicios de Integración right below it, enable the integration HTTP API, and enter a key. It can be any value, but use a long, unique key: it grants access to the POS sales. Write it down, because that key is the API Token from Step 2.
4. Press Aceptar to save.

That API uses port 8984 by default, the same one the connector already has under Advanced settings.

⚠️ If the box cannot be checked, your license does not include the module: ask your Agora reseller to enable it. Without it, the connector will fail on the API license active check.

Already done? If the box is already checked and the HTTP API already has a key, copy that key as it is (it is your API Token) and move on to step B. Do not change it: if another integration uses it, you would break it.

B - Get the Location Id (Workplace ID) - only with ACMS

In the connector, this value goes in the Workplace IDs field.

Only needed if you have ACMS (Agora Central Management System), that is, a central installation managing several locations; it makes the connector pull only this restaurant's sales. With a single location, leave the "Workplace IDs" field empty — it is on your restaurant's card, in the connector's Properties section — and move on to step C.

In the Agora web administration, go to Administración > Locales: the Id column is the value you need (in the example, "La Macarena" has Id 1). If one haddock restaurant collects sales from several locations, enter them separated by commas: 1, 2.

C - Get the POS Id (Punto de Venta) - only if you split POS terminals

Only needed if a single location has several POS terminals and you want each one to go to a different haddock restaurant (for example, a bar and a terrace invoiced separately). In any other case - the most common one - skip this step: haddock will collect the sales of every terminal in the location.

In the Agora web administration, go to Administración > Puntos de Venta: the Id column of each terminal is the value you need. The Local column tells you which location it belongs to, and Tipo whether it is a POS, an order-taking handheld, a tablet, and so on. For several, separate them with commas: 1006, 1009.

⚠️ Do not confuse Puntos de Venta with Grupos de Puntos de Venta: the groups only filter reports inside Agora and are not valid here.

💡 The connector only filters by location (Workplace ID), it has no POS Id field. If you need to split the terminals of one location, write these Ids down and contact haddock support chat.

Step 1 - Download and install

1. On the computer where Agora is installed, download the haddock Connector installer from bit.ly/haddockconnector.
2. Open the downloaded file. If Windows asks for permission (Windows protection screen), click "More info" and then "Run anyway".

   
   

   
   

   
   

   
   
3. Follow the installer steps:
4. • Welcome screen:

• Select the destination folder:

• Make sure the "Create a desktop shortcut" option is checked.

• Review the summary and click "Install".

4. When installation finishes, make sure "Launch haddock Connector" is checked and click "Finish". The program will open automatically.

   
   

   
   

Step 2 - Configuration

When the program opens, you will see a screen with several fields to fill in:

1. POS System:
Select Agora from the drop-down menu.

2. Agora connection details:

• API Token: the integration HTTP API key you defined in step A of the section above.
• Advanced settings: Expanding this option lets you configure the port (default 8984).

3. Properties / Establecimientos:

Add each restaurant you want to sync, with its own authentication code.

• Authentication Code: Go to the haddock web app, open Restaurant settings > My integrations > Agora Connector, and copy the 10-digit code shown there. Paste it into this field. Each property has its own code.
• Workplace IDs: the Agora location Id whose sales you want in this restaurant (step B). Leave it empty if you have a single location — sales from all of its tills will then come through. For several, separate them with commas: 1, 2.

4. Sync Settings & Dates:

• Sync interval: How often sales will be sent to haddock, in minutes. You can leave the default value (30 minutes).
• Sync Dates (Start / End): The period from which you want to import sales history. By default, it retrieves the last year of history.

Step 3 - Connect

Click the blue "Connect" button. The program runs a series of checks and shows them as a list of items that turn green one by one:

1. POS reachable — the connector finds Agora on this computer.
2. POS credentials valid — Agora accepts the API Token.
3. API license active — Agora's integration module is enabled.
4. haddock cloud — there is a connection to haddock's servers.
5. haddock auth code valid — your authentication code is correct.

When all of them are green, the connection is ready and sales will start syncing. If an item turns red, that is the source of the problem: look up the message the connector shows in the Errors and solutions section below.

How do I know it is working?

Once connected, you will see the status panel with real-time information: when the last sales sync happened, how many syncs have been completed, and a log of recent activity. If you want to sync right away without waiting, press "Sync Now".

Day-to-day use

• The program runs in the background - you do not need to keep it open. When you close the window, it minimizes to the notification area (bottom right of the Windows desktop) and keeps working.
• To open it again, click the icon in the notification area.
• It updates and restarts itself if there is any problem - you do not need to worry about anything.

🔧 Errors and solutions

If a check turns red when connecting, the connector shows a message. Look it up here to see what to do:

🚨 "API not accessible on localhost:8984. Make sure Agora is running on this machine."

(Check 1 — POS reachable)

✅ Agora is not open, is on another computer, the port is wrong, or a firewall/antivirus is blocking the port. Check that:

• Agora is open and running on this same computer.
• The port under Advanced settings is 8984 (the default).
• If opening http://localhost:8984 in the browser on this machine loads nothing, Agora's API is not listening there: contact your Agora reseller.

🚨 "Agora server is reachable but the API Token was rejected."

(Check 2 — Credentials)

✅ The API Token is wrong or inactive. Ask your Agora reseller for the correct token and to confirm it is active.

🚨 "Integration module is not activated in Agora (501)."

(Check 3 — API license)

✅ The token is valid, but the module is not activated on this installation. Review step A of the "Before installing - set up Agora" section: the Activar Módulo de Servicios de Integración box must be checked and the integration HTTP API enabled. If it cannot be checked, your license does not include the module: contact your reseller.

🚨 "Cannot reach haddock cloud."

(Check 4 — haddock cloud)

✅ The computer has no internet access, or a firewall/proxy/antivirus is blocking the secure (HTTPS) connection to haddock. Check the computer's internet connection and that the firewall or antivirus allows outbound HTTPS traffic to haddock. If the message says the cloud "is reachable but rejected the request", it is a temporary issue: try again in a few minutes.

🚨 "Authentication code is invalid" / "Invalid authentication code format."

(Check 5 — haddock auth code)

✅ The code was copied incorrectly or has expired. Go to the haddock web app (Restaurant settings > My integrations > Agora Connector), generate a new one, and paste it in full. Codes expire if they are not used.

🚨 I do not have the Agora API Token

✅ It is Agora's integration HTTP API key: you will find it (or create it) under Herramientas > Activar Módulos Adicionales > Configurar Servicios de Integración - steps in the "Before installing - set up Agora" section. If you do not have access to the Agora Monitor, ask your reseller for it.

🚨 Everything shows green and connected, but no sales reach haddock

(All 5 checks pass green, but the Workplace ID is wrong)

✅ When the connection shows as connected and syncs run, but no sales appear in haddock, it is almost always caused by a misconfigured Workplace ID on the restaurant's card, in the Properties section.

The Workplace ID tells Agora which location you want sales from, and the connector sends whatever is in that field straight to Agora. Because the token, module, and connection are all valid, the five checks turn green and the connector looks like it is working — but if that field holds anything other than your real location's numeric ID (a wrong number, or leftover text such as WP1 or test), Agora returns no sales for it and nothing reaches haddock.

• If you have a single location: leave the Workplace IDs field empty. The connector will then receive sales from every point of sale. If any value was left there by mistake, clear it.
• If you have multiple locations with ACMS: enter the exact Workplace ID for your location - it is in Administración > Locales, Id column (step B of the "Before installing - set up Agora" section). A wrong number means no sales will come through, even though the connection is green.

After fixing it, press "Save settings" and then "Sync Now" to force a sync. ("Connect" only appears on first setup; when editing an existing configuration the button reads "Save settings".)

The connector was working and now it fails

• I do not see sales right after connecting: the first sync can take a while if there is a lot of history. Press "Sync Now" in the status panel to force it.
• If you see the "Sync has been failing — please check your configuration" notice with a Reconfigure button, press it and use the list above to see which check is red.
• The connector also shows notifications in the Windows notification area (bottom right) when it has been unable to reach the POS or haddock for a while.
• Check that the POS computer is powered on and that Agora is still running.

Still not working after checking this? See How to fix connection problems with my POS or contact haddock support chat.

Integrations may include additional costs not covered by haddock.

Updated on: 26/08/2026