Getting 403 on calendar_entries.json

[Azam Khan]

Is anyone else getting a 403 Forbidden when trying to perform any action against https://app.clio.com/api/v4/calendar_entries.json

This isn't a 401 and so I'm pretty much dead in the water.  Any thoughts?

{

• error: 

  {

  • type: "AccessDenied",
  • message: "You don't have permission to access this, due to insufficient feature privileges."

  }

}

[Tony Valenti]

Hi Azam,

I've had issues with the Calendar_Entries API in the past and gave up working with it.  I just tested it again and I'm bumping into the same issue that you are.

Always glad to help,

Tony Valenti Software Engineer T: 402-401-7568 E: Tony.V...@AlphaDriveForClio.com W: www.AlphaDriveForClio.com   Schedule a Meeting with Me

This message contains confidential information and is intended only for the intended recipients. If you are not an intended recipient you should not disseminate, distribute or copy this e-mail. Please notify us immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

--
You received this message because you are subscribed to the Google Groups "Clio Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clio-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Azam Khan]

Thanks Tony. It’s strange cause they asked me to migrate to v4 cause of access token issues on v2 but now v4 api isn’t working. So now I have a hybrid auth via v4 but functional acccess against v2

To unsubscribe from this group and stop receiving emails from it, send an email to clio-develope...@googlegroups.com.

[Tony Valenti]

Hi Azam,

I’m definitely a big fan of V4 but I’ve noticed that since ClioCon, it seems as though the API team may have been moved to other projects.  Formerly, when I submitted a bug report, it would be resolved either same day or next day. It was pretty awesome. Right now it there are two  critical issues affecting the stability of bulk API listing that I’m suffering with and one of them I’ve had a ticket open for over 3 weeks and am still waiting for a human response.

--

[Azam Khan]

Ah that’s interesting. And has been my experience as well. Though I’m new to developing software that integrates with Clio, it took me two weeks to get a response on an access-token expiration. Clio team said it should not have happened and gave no explanation why. Just told me to go to v4. 

I hope they put some energy back into this area - otherwise it’ll be hard to keep putting my company’s time and energy towards an unstable product. Reflects poorly when my site doesn’t work properly due to api issues. 

Appreciate you insight, Tony. 

Thanks,

Azam

[matthe...@clio.com]

Hi Adam.

A quick introduction, I'm Matt Hoag.  Product Manager for Platform at Clio.

We've recently detected this bug as well.  As you can see by the 403 it is a permissions related issue.

We don't have many people working on the API V4 calendar end point at this time.  

I'd be curious to chat with you.  Can I reach out to you in a DM?

Matt

[matthe...@clio.com]

Sorry Azam.. Spell checker sabotaged me on changing your name.

[Azam Khan]

Just a quick update - this is now resolved thanks to the awesome Clio dev team