-
-
Notifications
You must be signed in to change notification settings - Fork 201
Mail function not working #488
Comments
Thank you @Nitwel – good catch. We're fixing this one now... |
Hey @Nitwel, are you making sure the request Can you tell me more about how are you making this request? |
@Nitwel Well this is progress in a way, this is a different type of error. I tested and there's a bug with the default configuration of mailing transport, and it seems this may be the same issue you are experiencing. Can you look at your logs in Directus in the |
Yes, as said, I tested many programms, the image is from a different programm. Here is the error from the last test (the request from the image) |
That error means that the body of the payload is invalid. Can you dump the whole payload you are using. To me it seems the one that's one the documentation. Is there a way I can test this with your instance? @Nitwel Also, make sure to not reveal your whole url + secret token in public (the screenshot). |
The payload is the same as in the doc. How can I contact you via PM? |
I feel this is something going on with either #489 (error with the default transport) or there's an issue sending this payload as json with the tools you are using. You can contact us on Slack https://slack.getdirectus.com I marked this as |
I am going to close this ticket as the error is an expected error when the payload content is an unknown type. |
When trying to make a simple POST request to the "[project]/mail" endpoint, I always get the error: "code": 13,
"message": "Invalid or Empty Payload"
I just used the example code from the API Doc, which obviusly should work.
Api Version: 2.0.1
The text was updated successfully, but these errors were encountered: