Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Hi,

i’m facing problems than never before using complex attribute object names via API Request on LinkedIn app.

Assuming that API Request doen’t support restli version 2.0, it perform url-encoding to query parameters in prepare phase.

Linkedin API rejects request as validation error when some complex parameter is defined ‘object.attribute’.

Many Linkedin APIs are defined with that parameters syntax. How to handle them correctly?

Hi @theorangepen, welcome to the Community!

Would you mind sharing the full error message you’re getting? I’d like to see exactly what’s its saying about the validation issue it found.

The API Request action for the LinkedIn app is still in Beta so there isn’t any documentation available for me to confirm whether those types of parameters are supported. But, does the same request work successfully when recreated in a service like Postman? 

Looking forward to hearing from you on this!

Reply


Terms & Conditions