Skip to main content
Best answer

403 Error when sending message via API using Zapier – what am I doing wrong?

  • June 3, 2025
  • 8 replies
  • 168 views

Hi everyone,

I'm trying to send a message via the Lodgify API following this documentation:
https://docs.lodgify.com/reference/post_v1-reservation-booking-id-messages

This is the JSON I used via my Mac Terminal that works great:

curl --request POST
--url https://api.lodgify.com/v1/reservation/booking/14326014/messages
--header 'X-ApiKey: XXXXXXX'
--header 'accept: application/json'
--header 'content-type: application/*+json'
--data '
[
{
"subject": "Hei",
"message": "Hello",
"type": "Owner",
"send_notification": true
}
]
'

When I try to send it using Zapier (Webhooks by Zapier – POST), I get the error 403 (see attached image).

 

Has anyone successfully done this via Zapier?
Can someone point out what I might be doing wrong?

Thanks in advance!
— Gianluca

Best answer by Troy Tessalone

@NM-Apart 

Turn Data Pass-Through? = False

 

TIP: Click underlined field labels to see tooltips with more info.

Also, looks like you have some extra trailing whitespace line breaks that should be removed.

 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

8 replies

MohSwellam
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+8
  • Zapier Orchestrator & Solution Partner
  • 902 replies
  • June 3, 2025

Hi ​@NM-Apart ,

 

I would something (a quick test), instead of using the Post request, use the Custom Request, it allows you to do a JSON (i have a feeling its the boolean value being passed as a string) 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34032 replies
  • June 4, 2025

Hi ​@NM-Apart 

Things to check/try:

  • If you want to use a raw JSON body, you can use this Zap action: Webhooks - Custom Request
    • Method: POST
  • For Zap action: Webhook - POST
    • For the field: URL
      • Make sure you are using a Message ID that still exists
    • For the field:  Wrap Request In Array
      • Change to YES
        • API endpoint documentation and your previous example shows the data wrapped in an array
    • For the field: Payload Type
      • Try changing the Payload Type to: Form
        • The Headers may handle the conversion to JSON

 

 

 

 

 


  • Author
  • Beginner
  • 6 replies
  • June 4, 2025

Hi guys,

@Troy Tessalone 
@MohSwellam 

Thanks a lot for your tips — I’ve tried to implement them, but unfortunately it’s still not working.

I've attached a screenshot again so you can double-check whether I really applied everything correctly.

One thing I’m wondering about: in fields like Headers, do I need to use special characters like single or double quotes (' or ") manually, or does Zapier handle that automatically?

The message ID is definitely still valid — I can still successfully send messages using the Mac Terminal, and they arrive as expected.

Here’s what I’ve tested:

When I use Webhooks – Custom Request:
No 403 error — the request seems to go through, but the message does not arrive.

When I use Webhooks – POST (with the settings Troy suggested):
Still getting the 403 error, just like before.

Any idea what could be causing this or what I might still be missing?

Thanks again in advance!

With Webhook Custom Request:
 

With Webhook POST:
 

 

 


MohSwellam
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+8
  • Zapier Orchestrator & Solution Partner
  • 902 replies
  • June 4, 2025

Hi ​@NM-Apart ,

Regarding the quotation marks, you are doing them right, my concern regarding the POST request VS the Custom request is that the send_notification value will be also wrapped in quotation marks, which is incorrect.

 

My only suggestion, in the CUSTOM request, wrap the Data in an Array. (i.e.: add [ ] ) and give it a try.


  • Author
  • Beginner
  • 6 replies
  • June 4, 2025

I’ve tried it – see the screenshot. Unfortunately, the message still doesn’t come through :( Is it correct like this?

 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34032 replies
  • June 4, 2025

@NM-Apart 

You have a Header label with a typo.
Should be X-ApiKey

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34032 replies
  • Answer
  • June 4, 2025

@NM-Apart 

Turn Data Pass-Through? = False

 

TIP: Click underlined field labels to see tooltips with more info.

Also, looks like you have some extra trailing whitespace line breaks that should be removed.

 


  • Author
  • Beginner
  • 6 replies
  • June 4, 2025

Great, it worked!

I had overlooked the typo in the Post Zap, but in the end it worked with the Custom Request – I set "Turn Data Pass-Through?" to false and cleaned up the whitespace, and voilà.

Many thanks to both of you, and have a great rest of your day!