How to Solve a 403 Error in Pipedream When Setting Up a New <http://Close.io|Close.io> Opportunity Trigger?

This topic was automatically generated from Slack. You can find the original thread here.

i’m getting an error on pipedream when setting up a close.io new opportunity trigger - although API keys and all are correct, i still get a 403 error. does anyone have an idea how to solve this? any help is highly appreciated :pray:

Hi , I don’t have a Close.io account, but was able to reproduce the same error by inputting a invalid API key. I know you mentioned your API key is correct, but could you please triple check?
Note that API keys are per-organization and can be generated and deleted in the Settings page.

hey ! thanks for the reply - yes I’ve tripled checked the API key and its correct. I’ve copied it manually, selected the API key manually and copied, and also used the provided clipboard button. still no luck :disappointed:

Just to make sure, from this docs I see there are API Key IDs and the API Key itself — could you check if you’re copying the value and not the ID?
I say this because the HTTP 403 Forbidden error is related to authentication