Billingo API v3 connection returns “[403] No authorization provided” in Make

Questions
1

:bullseye: What is your goal?

Automatically create an invoice in Billingo when a successful purchase/payment event is received from Payhip.
The intended flow is:
Payhip – Watch Events → Billingo – Create an Invoice

:thinking: What is the problem & what have you tried?

I have already created a Billingo connection in Make using a Billingo API v3 key. The API key is active and has both read and write permissions.
The connection appears in the Billingo module and can be selected successfully.
However, when I configure the Billingo – Create an Invoice module, I receive a [403] No authorization provided error under several required fields, for example Client UID and Payment Method.
I have already checked that:

  • I am using a Billingo API v3 key
  • the API key is active
  • the API key has read and write permissions
  • the Billingo connection is selected in the module
  • I have tried reconnecting the Billingo connection
    The issue still persists.
    Since the 403 error already appears while configuring the Billingo module, I assume it may be related to the Billingo authorization/API connection rather than the Payhip data mapping.
    Has anyone experienced this issue with the Billingo integration? Is there anything else I need to configure in Billingo or Make for the API v3 connection to work correctly?

:clipboard: Error messages or input/output bundles

[403] No authorization provided.
The error appears in the Billingo Create an Invoice module while configuring required fields such as Client UID and Payment Method.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Képernyőkép 2026-08-24 091902.png
Képernyőkép 2026-08-24 091902.png666×858 41.2 KB

4

A 403 on Client UID and Payment Method while you are still configuring the module is the lookup GET, not Payhip. The connection can save and still omit the key on those dropdown calls.

Billingo v3 wants X-API-KEY, not a Bearer token. If an HTTP GET to /payment-methods with that header returns 200, the key is fine and the Make Billingo app is not sending it.

Have you tried that one GET outside the module, or only reconnecting the connection?

6

Thank you, this was exactly the right direction. I tested the setup outside the Billingo connector and confirmed that the API key itself was fine. The problem was indeed that the Make Billingo app was not sending the authentication correctly. I switched to Make’s HTTP module and now call the Billingo v3 API directly using X-API-KEY. That solved the 403 issue. Thanks a lot for pointing me in the right direction!