Receiver works with API key as bearer token, but not in the URL

OttoFMS
1

I set up a webhook, and it’s succesful hitting my server when I’m using the bearer token method of including the API key.

However, when I use the method of the API key in the URL as a parameter, or at the beginning, it doesn’t work.

Can’t share too many URLs on here, so I will share them in a brief video:

I need one of the other methods to work, because as far as I can tell Stripe cannot use the Bearer Token method.

thanks for any advice.

2

Hello Chris

Welcome to the Community :slight_smile:

You can use the Webhook Test and View option in OttoFMS Webhooks Screen,

TG2024-09-19 at 11.39.46
TG2024-09-19 at 11.39.461156×121 27.6 KB

That method uses the apiKey in the URL. You should get a response that looks like this.

{
    "success": true,
    "scriptError": 0,
    "scriptResult": {
        "messages": [
            {
                "code": 0,
                "message": "No Error"
            }
        ],
        "response": {
            "messageQueue": [
                "A64E9BB3-F635-48A0-BFD6-6B97CAA69804"
            ]
        }
    },
    "messageRecordId": "1853717",
    "successMessage": "Message Accepted"
}

In the otto-receiver.log file It shows this

2024-09-19T18:32:47.546Z	info	receiving webhook for channel: edd.test
2024-09-19T18:32:47.568Z	info	webhook published to channel: edd.test

What do you get when you try it?

Todd

1 Like
3

Based on your video, it looks like you are trying to call directly through to the DataAPI proxy. Use the dashboard to create your webhooks and it will provide you a slightly different URL structure-- even including the API key in the URL for you to easily copy/paste

1 Like