WOW ! this is it !!!
wrapping the URN brought correct results.
@Troy Tessalone : I really appreciate your support on this issue. Thanks a lot : you made my day !
@djrlambert
Did you try wrapping the right side values in List(URN) as indicated by the API docs?
shares = List(urn:li:share:7132564752928563200,urn:li:share:7132402731377438720)
thank you for your patience ! here are the screen captures
@djrlambert
For us to have context about the error, we would need to see updated screenshots with how the entire Zap step is configured.
it seems the parameter issue has been fixed, but running this ZAP now results in a different type of error :
Zapier troubleshoot AI gives no detailed explanation.
@djrlambert
Example from the API docs:
https://learn.microsoft.com/en-us/linkedin/marketing/community-management/organizations/share-statistics?view=li-lms-2024-06&tabs=curl
shares=List(urn:li:share:7132564752928563200,urn:li:share:7132402731377438720)
Instead of sharess0] use shares
Hi @Troy Tessalone
I’ve retried my Zap with the following set-up :
it’s still generating an error message.
Error message :
According to Troubleshooting Beta IA, the shares>0]
parameter might be causing the issue.
@djrlambert
You should not need to encode the query string parameter values as those will get encoded when the request is sent.
This warning is presented on all Linkedin API.
I’m using the versioned API , ie : https://api.linkedin.com/rest/
the unversioned looked like https://api.linkedin.com/v2/
below is a screen capture of the Zap Action Tab :
@djrlambert
From the link you provided...
Hi @djrlambert
Can you link to the LinkedIn API endpoint documentation you used to configure the Zap step?