#Pipedrive API Issue: Use x-api-token Header and Include /v1/ in Base URL

1 messages · Page 1 of 1 (latest)

unkempt sorrel
#

Hey @vapid hound ,

I’ve connected a Pipedrive account with a valid API token and provided the domain name. However, there appears to be an issue with how authentication is currently being handled.

From reviewing the Pipedrive API docs, I noticed:

  1. The API token needs to be passed as a header: x-api-token, rather than Bearer token
  2. I also checked if the issue was with the domain-specific API base URL, and found that the version is missing.
    The base URL should follow this format:
    https://<domain>.pipedrive.com/v1/
    instead of just https://<domain>.pipedrive.com/.

Please help us with a quick fix. Thanks

image.png image.png image.png image.png
ebon solsticeBOT
#

Hi Naik, I've forwarded the Issue to the Integration team and they'll be working on a fix.

unkempt sorrel
#

@vapid hound can you share the timeline for this fix?

ebon solsticeBOT
#

I have to check with the team, I'll update you when we have an ETA.

unkempt sorrel
#

Cool, this is a bit urgent on our end—would really appreciate it if you could prioritize this. @vapid hound

unkempt sorrel
#

Hey @vapid hound any update on this ?

ebon solsticeBOT
#

Hi Naik, we've prioritised this and I'll keep you updated.

unkempt sorrel
#

Thank you.

unkempt sorrel
#

hey @vapid hound any update on this ?

ebon solsticeBOT
#

Hi Naik, Team is low on bandwidth and will be picking this Issue up next week. I'll keep you updated.

ebon solsticeBOT
#

this issue has been fixed

unkempt sorrel
#

@honest quest the issue still persists, the api version is missing in the endpoint and also the teams actions points to projects , these are only few checks I have made, please verify this from your end. Thanks

image.png image.png