Skip to main content
  • EN

Hi everyone,

Has anyone recently encountered issues making API requests to a Freshsales instance?

I'm consistently getting an "Incorrect or expired API Key" error for a query that was working perfectly just a few weeks ago. I've already tried resetting the API key, but the issue persists.

Here's what I've checked and observed:

  1. Previous Functionality: The exact same API request with the same authentication method was working fine a few weeks ago.
  2. API Key Reset: I have reset the API key for my user account, but this did not resolve the error.
  3. Authorization Header & Encoding:
    • I've also looked into the Authorization header. When I send the API key in the way I believe is correct (and which worked previously), I receive the "Incorrect or expired API Key" error.
    • As a test, if I try sending the request without what I believe to be the correct encoding/formatting for the key in the header, I instead get a "You do not have permission to perform this operation" error. This suggests the API is reacting differently based on the Authorization header, but ultimately still failing with the "Incorrect or expired API Key" when the header is formatted as it was when it worked.
  4. User Permissions: I've confirmed that the user account whose API key I'm using has administrator privileges.
  5. Testing with Other Admin Keys: To further isolate the problem, we've also tried:
    • The API key from my colleague from Marketing who has an admin account on the client's instance.
    • An API key from one of the client's own administrator user accounts.

Unfortunately, all these attempts with different admin API keys result in the same "Incorrect or expired API Key" error.

Has anyone else experienced a similar sudden issue, or does anyone have suggestions on what else we could check? Could there be an instance-specific issue or a recent change we might be unaware of?

Thanks in advance for any insights!

Hey There Cristobal,

 

Utilizing FreshService here - I am using the basic auth with username and password, the Username is my Key/Token and password is just a singular value (like a 1 or an ‘a’) - have you tried this method? 

 

 

I just tested and got a 200 Response along with the expected Payload - however, you may be on to something with it being realm/instance specific. I would think you wouldn’t have hit your plan’s API Call limit already for the given time period. 

I was able to do what i was trying to do.
Long story short; the deal needed a sales account to be created. A new or an existing one.

i just had to change the payload including the name of a sales account (not existing in my instance, so this will create a new one)

 



The error message was not descriptive so i had to figure out this at my own.

Reply


Terms of Use