Unable to get appointments suddenly
79 views
Skip to first unread message
Daniel Newsome
Jan 6, 2025, 3:41:36 PMJan 6
to DrChrono API Developers
We've had some production code running for years that gets/sets appointments which suddenly broke a few days ago. I can confirm that nothing really changed as far as permissions.
CONFIDENTIALITY NOTICE: This e-mail, including any attachments, may contain confidential information which is intended only for the use of the individual(s) or entitled named. If you receive this e-mail message in error, please immediately notify the sender by e-mail and delete it. Dissemination, forwarding, printing or copying of this e-mail without prior consent of the sender is strictly prohibited. Thank you for your compliance.
I've tried re-minting the token, checking permisions, etc.
The call looks something like
And the response looks something like
<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>403 ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nBad request.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront)\nRequest ID: WdxobHvI40vFasff539ZQSBjkHP4bOy7kLuzrSwu2ZCKdurSqDuixQ==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>
Can anyone assist?
CONFIDENTIALITY NOTICE: This e-mail, including any attachments, may contain confidential information which is intended only for the use of the individual(s) or entitled named. If you receive this e-mail message in error, please immediately notify the sender by e-mail and delete it. Dissemination, forwarding, printing or copying of this e-mail without prior consent of the sender is strictly prohibited. Thank you for your compliance.
Francisco Jose Mendoza Holguin
Jan 10, 2025, 2:24:03 PMJan 10
to DrChrono API Developers
https://groups.google.com/g/drchrono-api/c/LtfimfwGu0U/m/U7oX_gmcAAAJ
Hi team, I see new errors for /api/appointments/ (create, delete).
Hi team, I see new errors for /api/appointments/ (create, delete).
Response for delete https://app.drchrono.com/api/appointments/331815681: 403 {'detail': 'You do not have permission to perform this action.'}.
I checked the required scopes and I see that we passed them.
Hello!While "scopes" grants access for users to programmatically interact with various data points within your DrChrono account, you must configure user-based "permissions" to allow access to your "scope" options. The most common fix for your specific issue is to visit "Account" > "Staff Permissions" then locate your API-connected user and click "View" to access the permissions modal. In the modal, locate the permission "Access Scheduling" and ensure the checkbox is "checked" then save your changes.
Let me know if that works for you.
---
Aaron Bethea | DrChrono ETL Migrations / API Specialist
EverHealth
Hey there I saw this issue before, and this response; However I was having the same issue but in my case, it was not anything regarding the permission set instead was the redirect_uri, redirect_uri_enconded changed, and didn't that change on my end after updating it everything just work fine for me. Hope that at least gives a starting point to try but it might end up being another issue.
Hey there I saw this issue before, and this response; However I was having the same issue but in my case, it was not anything regarding the permission set instead was the redirect_uri, redirect_uri_enconded changed, and didn't that change on my end after updating it everything just work fine for me. Hope that at least gives a starting point to try but it might end up being another issue.
DrChrono API Developers
Jan 10, 2025, 2:29:57 PMJan 10
to DrChrono API Developers
Hi,
This is likely coming from a rule change from when we moved from clouflare to cloudfront, this occurred in a few user instances.
If you include an empty request with your GET call, it will cause this type of error.
Best,
Assaad
Daniel Newsome
Jan 22, 2025, 10:43:40 AMJan 22
to DrChrono API Developers
I was able to fix my issues by removing the body of my request which was blank, but triggered no errors for the last 4 or so years until around two weeks ago. Was able to try it out in Postman and got successful requests
Kuldeep Barod
Jan 22, 2025, 10:43:40 AMJan 22
to DrChrono API Developers
I also face the same issue and resolved by making my request AlwaysMultipartFormData = false; or you can remove this (
AlwaysMultipartFormData ) from your api request.
Edmilson100%
Feb 13, 2025, 12:34:41 PMFeb 13
to drchro...@googlegroups.com
Ok.
Obrigado.
--
You received this message because you are subscribed to the Google Groups "DrChrono API Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drchrono-api...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/drchrono-api/9a407c08-6b25-4472-a4f7-98b88075812dn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages