Does anyone know anything about 'Mr Besst's' software integration process?

APIIntegrationCRMSoftwareTroubleshooting

Registration:
04.11.2021
Messages: 1129

Dmitry_IT Topic author

28.02.2025 20:46

I'm trying to get our legacy accounting system to talk to the new CRM, and I keep seeing 'Mr Besst' mentioned in the forums and documentation. It seems like everyone uses his proprietary API connector, but the official guides are incredibly vague about the setup. Has anyone successfully implemented this connector in a mid-sized business environment? I'm running into authentication errors and I'm not sure if I'm missing a key step or if the documentation is just outdated. Any advice on best practices or recommended support channels would be hugely appreciated.

18 Answers

09.12.2022
Posts: 290

Nick_V

22.03.2025 23:32

Check the sandbox environment first.

04.01.2025
Posts: 1077

Walter_C

10.04.2025 15:00

We used it last year. The documentation is terrible, but it works if you have a dedicated middleware layer. Don't try to connect directly from the accounting system; it's too fragile. Focus on establishing a secure API gateway first. It saved us hours of headaches and prevented several authentication failures. We recommend dedicating a full-time developer just for the integration phase.

02.09.2023
Posts: 802

Ps5Lover

04.05.2025 20:34

Has anyone found a community-built wrapper? The proprietary nature of the connector is a huge blocker.

28.12.2023
Posts: 358

ViperStrike

12.07.2025 18:36

Authentication errors are usually scope-related. Make sure your credentials have read/write access for *all* necessary endpoints, not just the primary ones. Mr Besst's system is notoriously granular about permissions.

12.07.2021
Posts: 366

ConsolePeasant

17.07.2025 08:57

I had similar issues. My advice is to bypass the official documentation entirely and find a partner implementation guide. They often have the real-world workarounds that aren't published.

18.06.2025
Posts: 317

RetroGamer

17.08.2025 21:36

Did you try updating the connector itself? Sometimes the error is just a version mismatch.

28.04.2022
Posts: 1389

RazerFan

21.08.2025 09:15

I think the issue might be related to data type mapping between the legacy system and the CRM. It's rarely the API itself, but how the data is formatted when it passes through the connector. Check date fields and currency codes specifically.

26.09.2024
Posts: 261

Burke_C in response

29.08.2025 04:22

I agree with the middleware suggestion. It adds necessary abstraction and resilience. Without it, you're always one failed endpoint away from a total system crash. It's worth the extra cost for stability.

13.04.2022
Posts: 741

DataMiner

02.09.2025 01:58

The support channels are useless. You have to talk to a third-party consultant who specializes in legacy integrations. They know the undocumented endpoints.

16.11.2023
Posts: 1122

Faris_C

05.09.2025 02:54

How long did your team spend on this? We spent three months and still had minor syncing issues with the invoicing module. It's a marathon, not a sprint.

23.01.2024
Posts: 1258

Bishop_A

04.10.2025 16:32

Are you using the latest version of the CRM? Sometimes the connector needs updating even if the accounting system is fine. It's a dependency chain nightmare.

18.04.2025
Posts: 34

Friend_C

25.10.2025 15:19

I found that using OAuth 2.0 tokens instead of basic API keys solved all my authentication problems. It's much more robust for continuous syncing.

21.03.2024
Posts: 331

Father_C

10.11.2025 17:44

The documentation is vague because they don't want people to know how easy it is to break. Seriously, prepare for frustration. Be patient and focus on small, testable chunks of functionality.

09.07.2022
Posts: 1019

CodeBreaker in response

25.12.2025 06:48

Reply to the user above: Yes, OAuth was the key. Basic keys expire too quickly for a mid-sized business environment that needs continuous, reliable data flow.

07.01.2022
Posts: 439

CyberSamurai

21.01.2026 03:54

Have you checked rate limiting? If your legacy system is sending a burst of data, Mr Besst's API might be throttling you, which would manifest as an authentication failure.

23.09.2025
Posts: 134

Boss_C

28.02.2026 00:08

I recommend looking into an iPaaS solution like Zapier or MuleSoft. They handle the complex data transformation and authentication layers far better than trying to build it manually with the proprietary connector.

17.03.2024
Posts: 796

Mother_C

06.04.2026 01:11

I think the issue might be related to the time zone handling. Both systems need to agree on UTC or a specific local time zone, or the dates will appear corrupted and fail validation.

02.06.2025
Posts: 1240

Crowe_T in response

10.04.2026 08:16

To echo the point about middleware: it's not just a suggestion, it's a necessity for mission-critical systems. Treat the connector as a data pipe, not a direct connection. This adds necessary layers of error handling and retry logic.

Want to join the discussion?

To leave a comment, you must log in to the forum.