Using the HTTP request

Automations Builder
1

I have been trying to figure out how to use an https POST request, but am failing and need some help.

If the following works and returns a 201 with a valid record and new key

image
image1147×374 42.8 KB

Then would this not be the equivalent?

image
image338×872 40.6 KB

This errors every time.

{
  "body": {
    "error": "System.ArgumentException: The value 'sales-invoice-form' is not a valid GUID. Please provide a valid GUID in the correct format, for example: 'FA896E59-5EAF-450E-AA6B-E2321D96026B'. (Parameter 'input')\n   at Manager.GuidExtensions.ToGuid(String input) in 

Any way to see the cURL.

What am I not understanding in how the HTTP request wokflow node works?

Thanks all.
2

Hello @valsoar1,

Is the example in your initial screenshot something you’re able to do yourself, or have you been sent that screenshot? I’m just curious if you can execute the request yourself, manually.

This message:

The value ‘sales-invoice-form’ is not a valid GUID. Please provide a valid GUID

Definitely makes it sound like that endpoint doesn’t exist. Does the domain (underneath the censored bit) match what is in the screenshot?

Based on the configuration in the second screenshot, it should work.

Cheers,

Peter Evans

3

Yes, the first screen shot was executed by me. Get valid response via other tools, just not from Baserow?

4

OK, thanks for the confirmation! Based on that error message, we are sending an HTTP request to that endpoint, it’s the endpoint that is telling us that sales-invoice-form isn’t a valid GUID.

The only thing I can think of is there are additional characters in the Endpoint URLfield, would you mind typing it out again (not copy→pasting) in case it matters?

If that doesn’t work, would you mind sharing the full domain with me? Based on the endpoint, and some Googling, I can guess what product you’re using, but it’d help narrow things down further!

Cheers,

Peter Evans

5

Retyped by hand. No change in the result. The endpoint is iaccount.manager.io/api2/sales-invoice-form

The screenshots were from Swagger. It works fine from Swagger or Postman.

The same ‘sales-invoice-form’ can be used as a GET

image
image1488×111 7.52 KB

When sent as a POST it doesn’t need a GUID {Key}, but it does as a GET. Any chance that Baserow is somehow sending a GET instead of a post? If it were a GET the returned message would make sense to me.

6

Good morning!

That makes sense, you’re POSTing to their list endpoint, whereas the key would be for a detail endpoint.

We’re definitely sending POSTs, but I did re-check in just in case :grimacing:

A few more ideas, if you don’t mind!

  1. Could you try sending a POST to https://webhook.site (the site will give you a random URL to test with), and check what is being sent?
  2. I can see line breaks, or whitespace, before your X-API-KEY and Content-Type headers, mind remove them? I don’t actually think they’re the cause, but it’s worth a try.
  3. Is the API key a formula, or a raw string?
  4. Are you a baserow.io user, or are you self-hosting?

I’ve sent a variety of requests to that endpoint from baserow.io, and I never get that GUID error, so I have to assume it’s something that appears after authentication is successful.

Cheers,

Peter Evans

7

OK, sent to webhook.site and the body looks correct. I’m at a loss. I’ve posted to Manager.io forum also.

I’m new to this so I could well be missing something. Manager definately seems to think it needs a GUID when sent from Baserow. Any chance a '/’ is being appended to the POST so that it thinks it should be expecting a {key} parameter?

image

8

No, and even if you manually add it and send the request (e.g. with curl, or an HTTP library), you’ll get a 404 back from their API.

Mind covering points 2 → 4 for me? They could give us some more clues.

Cheers,

Peter Evans

9

2 - I removed them - retried,authentication error (missing X-API-KEY), rekeyed by hand, same result, make into a forumula using strip(), same result

3 - Right now it is just a raw string until I get it to work

4 - baserow.io

10

I’m stumped I’m afraid @valsoar1, I’m trying this out on baserow.io as well, and the only error responses I get are:

  • 404: if I add a trailing slash
  • 401: if I dispatch to the correct URL, but they reject my X-API-KEY

I’m really not sure why you get that error from them, but it must happen after authentication, which is why I don’t see it.

My apologies for the inconvenience, this is an odd one!

Cheers,

Peter Evans

11

OK - I’ve sent details to Manager.io and will see if any suggestions from their end. I don’t get it either.

1 Like
13

OK, I think I figured it out. Here is the issue - It appears the issue is caused by redirection. When the POST is sent to https://{{subdomain}}.manager.io/api2, it is apparently automatically redirected to a regional endpoint such as https://{{subdomain}}.us-east-1.manager.io/api2

I updated the URL to directly reference the regional endpoint and:

{
  "body": {
    "Key": "9638205e-ff7d-4f97-83ef-a3a1c9d41552",
    "Reference": "IAC-8"
  },
  "headers": {
    "Date": "Fri, 27 Feb 2026 15:21:50 GMT",
    "Vary": "Accept-Encoding",
    "Server": "Kestrel",
    "Served-By": "iaccount",
    "Connection": "keep-alive",
    "Content-Type": "application/json",
    "Cache-Control": "no-cache, no-store",
    "Content-Encoding": "gzip",
    "Transfer-Encoding": "chunked",
    "Access-Control-Allow-Origin": "*",
    "Access-Control-Allow-Headers": "*",
    "Access-Control-Allow-Methods": "*"
  },
  "raw_body": "{\"Reference\": \"IAC-8\", \"Key\": \"9638205e-ff7d-4f97-83ef-a3a1c9d41552\"}",
  "status_code": 201

Yikes.