Skip to main content

Hello, all!

I’ve been having an impossible time getting Zapier to make successful API requests to Filevine using the API Request feature. I’ve been able to make them through Postman without issue, but I always get the following error no matter the endpoint: 

Raw request failed. Problem executing your request: Invalid response

I’ve tried using the base URL listed in their docs as well as my company domain API base URL.

https://api.filevine.io
and https://{myCompanyDomain}.api.filevineapp.com
Both options give me the same error. I’ve also tried adding the “Authorization: Bearer {accessToken}” and “x-fv-sessionid: {refreshToken}” in the additional request headers just to try every possible combination even though the authentication headers are automatically sent. All four combinations produced the same error.
I attached some screenshots of the Zapier requests, the error message and the successful request in Postman. Any help would be greatly appreciated!
 

 

Hi @gford 

Good question.

Can you link to the Filevine API endpoint docs you are referencing to configure the Zap step?


Hello Troy,

Here are the docs: https://developer.filevine.io/docs/v2/45a91cd6e76c6-base-url

I’m using this specific endpoint page in the screenshots, however, I get the same error no matter what endpoint I try.
I’ve tried the Get Project List, Get Contact, Get Contact List and a few others. For each one, I’m able to fetch information in Postman, just not Zapier.

Thanks!


@gford 

Try adding Headers:

Content-Type: application/json

Accept: application/json

 

You may only need 1 of the 2.

 

 


@Troy Tessalone 

I added and tested them with both base URLs. I tested them on their own and with both added to the “Additional Request Headers.” I’m still seeing the same error.


Screenshots of what I input:

 


@gford 

Can you post updated screenshots with how your Zap step is configured?

Make sure to use the base URL.

 


@gford 

The API Request Zap action likely only supports the default base URL.

api.filevine.io

 


@Troy Tessalone 
I’ve tried both URLs. I was only trying my company domain URL because the base URL (api.filevine.io) wasn’t working. It just happened to be the one I took a screenshot of.


@gford 

The error seems to indicate an invalid response.

That may indicate the request was fine.

Either the Zap action behind the scenes is not properly handling the response OR perhaps there was no data returned for the request, thus resulting in an error.

 


@Troy Tessalone 
It seems like it’s leaning towards something behind the scenes in the Zap action because I use the exact same contact id and reach the same endpoints with no issues using Postman. I just wanted to be sure that I had the information entered correctly for the request. I’ll see about possibly opening a ticket with Zapier about it.

Thanks so much for your help, Troy!🙂


@gford 

You can try reporting this via a ticket to Zapier Support: https://zapier.com/app/get-help


I just wanted to update this because it is a bug that has been confirmed by Zapier and Filevine, so currently the only way to make custom requests is by using webhooks.


Reply