About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Domain filter issue with cvent

  • 29 August 2023
  • 10 replies
  • 159 views
Bill Mische

Cvent has two ways of adding attendees either by adding them as an invite or registering them. Our account is set up to use the invite route.

With how our cvent account is set up I’m unable to use the pre-built “add Attendee” step, which uses the register route, so I’ve added an API request step. Unfortunately when I try to use the URL from their developer portal (https://api-platform-eur.cvent.com/ea/attendees ) I get an error “Domain did not match expected domain filter `io.cvent.com`” which I think refers to a previous version of the API.   When I amend the request to use the equivalent io.cvent.com URL I get a 403 error. 

Is there a way round this other than dropping back to pure webhooks?

 

10 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @Bill Mische 

Good question.

To help us have full context, please post screenshots with how your Zap step is configured.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Bill Mische

Thanks Troy

Please find attached.  The first couple of steps catch and format the details from our CRM. Then it’s a matter of picking up & updating the contact, getting the details of the event and adding the attendee.  It’s just the last step I’m stuck on.

 

The API documentation cvent pointed me at is at https://developer-portal.cvent.com/documentation#tag/Attendees/operation/createAttendee

1 Attachment
Troy Tessalone
Userlevel 7
Badge +14

@Bill Mische

Couple things to address…

 

Try adding this header:

Content-Type: application/json

 

 

The Query String Parameters need to be removed.

 

The Body section needs to be populated with the JSON structure.

[{
	"event": {
		"id": "[ID]"
	},
	"contact": {
		"id": "[ID]"
	}
}]

 

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Bill Mische

Thanks Troy - I’m still getting the domain error.

Troy Tessalone
Userlevel 7
Badge +14

@Bill Mische 

We would need to see updated screenshots with how your Zap step is configured.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Bill Mische

Hi Troy - this is the current version.

1 Attachment
Troy Tessalone
Userlevel 7
Badge +14

@Bill Mische 

You may need to open a ticket with Zapier Support: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
TechTaps
Userlevel 2
Badge

Hello @Bill Mische , 403 errors generally indicate authorization issues.

I was looking through the authentication part : https://developer-portal.cvent.com/documentation#section/Getting-Started/Authentication

Can you check if you have the scopes that is needed for the account?

Your request seems fine. It should be mainly a permission issue.

A

Hi @Bill Mische 

I have just come across this exact issue. Did you manage to find a solution?

S

@Bill Mische

Couple things to address…

 

Try adding this header:

Content-Type: application/json

 

 

The Query String Parameters need to be removed.

 

The Body section needs to be populated with the JSON structure.

[{
	"event": {
		"id": "[ID]"
	},
	"contact": {
		"id": "[ID]"
	}
}]

dragon city hack gems 99999 download

 

When I attempting to utilize a custom API request for a distinctive "AR Experience Trigger" action. Despite diligently adapting the API endpoint to align with the platform's expectations, an unexpected error surfaced: "Quantum Signature Mismatch." It appears that the AR platform employs advanced quantum encryption. 

Reply


Terms & Conditions