Postman vs Gumloop requests to Beehiiv API are different

Get Help
1

Hey guys,

I have tried run code and call api node and both of these get a valid response (201) from the Beehiiv API, however the post is not ending up on the Beehiiv dashboard.

I’ve been debugging with their support to ensure I’m sending the right payload and I can confirm it runs correctly and ends up on the Beehiiv dashboard when calling the api from Postman or my local copy of the python code from my run code block (executed locally).

I am in touch with them to see if I can get some more information on the ones that are seemingly failing.

However, I also need to ask you guys if there’s anything else being sent with the request that could be causing issues?

As always, thanks for your support!

@wasay: I’ve shared the workbook with you.

https://www.gumloop.com/pipeline?workbook_id=6J3ayDNCPPQPxnA5r46eVJ&tab=2

2

Hey @mutty! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

  1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

  2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
    GIF guide

  3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

3

Hey @mutty – We do not send any additional information with the payload, its a direct API call. Let us know if you get more information from them and we can look into it further.

4

Hey wasay,

So, no luck from there end. This was their response to my questions around additional logs.
It’s really strange because I’ve tried the run code node and the api call node, but both result in a 201 with no email created. But the same call from postman results in 200 and the email is created in the Beehiiv.

Hi Umut,

I’m not sure I have much helpful information in our logs. Here’s an example of what we store for send api requests:

[
	{
		"id": "--uuid--",
		"publication_id": "--uuid--",
		"params": {
			"title": "Some Blog Title",
			"blocks": [
				{
					"text": "Some title",
					"type": "heading",
					"level": "2"
				},
				// ...
			],
			"subtitle": "Some subtitle",
			"recipients": {
				"web": {
					"include_segment_ids": ["--uuid--"]
				},
				"email": {
					"include_segment_ids": ["--uuid--"]
				}
			},
			"scheduled_at": "2030-01-01T12:00:00Z"
		},
		"errors_response": {
		},
		"status": 0,
		"completed_at": null,
		"created_at": "2025-03-25 07:19:35.504404",
		"updated_at": "2025-03-25 07:19:35.504404"
	}
]

For all of the requests we have saved for your publication, none have an error_response. Which makes sense because we are returning at 201 created response which is a success and not an error, even though the posts aren’t being built ultimately. I hope Gumloop might be able to use our Docs along with what they can see on their end to identify where the issue is. Or maybe you will be able to see some thing useful in the logs that I’m missing.

Not really sure what to do here, but I understand if there’s nothing you guys can do from your end.

5

Got it. Unfortunately, I don’t think we’ll be able to dig into this further since the run code/call API nodes send the request directly without anything being transformed in between. Looping in @rahul-gumloop here in case he has any additional thoughts.

6

Hey can you send the exact cURL / Postman request that is working?

You can send me an email rahul@gumloop.com – please include all headers, query parameters, json body, etc.

7

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.