#Events api response with 503 Service Temporarily Unavailable

1 messages · Page 1 of 1 (latest)

radiant pond
#

Hi Mollie team,
one Issue I still have is I get an 503 when I try to use the events api.
path: /v2/events/eventID

What can I do about that?

reponse:

  "status": 503,
  "title": "Service Temporarily Unavailable",
  "detail": "The service is currently unavailable due to an upstream (503) or internal error (500).",
  "_links": {
    "apiStatus": {
      "href": "https://status.mollie.com",
      "type": "text/html"
    },
    "documentation": {
      "href": "https://docs.mollie.com/overview/handling-errors",
      "type": "text/html"
    }
  }
}```
heady wing
#

Hi! Last time Robin was troubleshooting with you, he discovered that 500s are on your end, not ours. As mollie staff, we don’t debug external code or offer debugging support, so you’ll need to investigate this within your setup.

radiant pond
#

Hi @heady wing ,
thanks for your message.

Yes, Robin was troubleshooting with me earlier, and I managed to fix that issue afterwards.

However, this is a completely different problem.

Here’s some more context:
I’m receiving a webhook from Mollie with the new event webhook. When I try to retrieve the information of that webhook, it immediately results in a 500 error with the message mentioned above. I’ve followed everything described in the documentation and even experimented with the testmode flag since I’m currently in test mode. The event ID is definitely correct, and I also tried making the request via Postman, but no luck.

The API token I’m using is a testmode token.
If you need any additional details, just let me know — I’d really appreciate your support on this.

radiant pond
#

Hi @heady wing,
sorry for my message again but Im really stuck with that issue and Im really sure that this is not my fault. It could be some Mollie Account configuration or something.

long coral
#

Hi @radiant pond, what's the event you are trying to subscribe to? could you please share your org ID?

radiant pond
long coral
twin echo
#

one Issue I still have is I get an 503 when I try to use the events api.
path: /v2/events/eventID

This is an events endpoint on our API, not sales invoice-specific 😅

#

So this is for the webhook devs

radiant pond
pliant matrix
#

@radiant pond I can take a look at it 😄
Could you please send me the organizationId and the eventId?

radiant pond
#

Hi Andre
I send it to you via dm

twin echo
pliant matrix
#

Good morning! We have identified the issue and we are working on a solution 😄

radiant pond
pliant matrix
#

Due to Black Friday approaching, the fix will need to be delayed a little

radiant pond
#

Okay thanks. 🙏
but please be aware of it.

radiant pond
#

Any updates?
@pliant matrix

pliant matrix
#

Hey! I just got back from vacation. Let me catch up with the team

pliant matrix
#

@radiant pond could you try again please?

radiant pond
pliant matrix
radiant pond
#

Correct Im already using the testmode field but im asking if I have to authenticate with an oauth key.

pliant matrix
#

Yes, you have to use an OAuth key to access that API

radiant pond
#

Hi André, why do I need to use an OAuth key to authenticate with the events api?
The documentation describes that the service could also use the normal API credentials. see:

Most API credentials are specifically created for either live mode or test mode. In those cases the testmode query parameter can be omitted. For organization-level credentials such as OAuth access tokens, you can enable test mode by setting the testmode query parameter to true.

In my case using the OAuth api will increase the complexity.