Troubleshooting PandaDoc API Sandbox Integration Issues

Ben C. · 2024-09-02 11:01:36.014024+00

Hey all. I am trying to get a PandaDoc integration to work.I have been trying to set up their "Sandbox" API but running into errors. I thought I get the API keys and headers correct so not sure what the issue is. Has anyone done this before ? I will share my Clay table. and screenshots. thank you for your help :pray::skin-tone-3:

Troubleshooting PandaDoc API Sandbox Integration Issues | Clay

12 comments

· Sorted by Oldest

Ben C.
·
·
https://app.clay.com/workspaces/34750/tables/t_vSiQg5AbJEzc/views/gv_u2KhymQtrvmA
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Ben C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 🔒[private user].
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Ben C.
·
·
https://www.loom.com/share/b8ae4644f21c4bcb82f041d2cafd08e7 still running into the issue 😞
Ben C.
·
·
deleted the "bearer" and same issue unfortunately
Bo (.
·
·
Hey Ben, I saw your message in Slack, but it looks like you might have missed my replies. It seems like some changes were made again, which brought us back to square one. Did you verify your email as instructed? I've remade the changes so you could see that error again:
Bo (.
·
·
This was my previous message just in case: Hey Benjamin, Jetlag really does suck—good luck with your interview tomorrow! 😅 The video was super helpful, thanks for that! So the issue turned out to be with the Authorization header—it should be formatted as API-Key {yourapikey}. I’ve added that into the table, but now I’m getting another issue. It failed again due to a 403 Forbidden error, and the error message indicates that the email is not verified: "type": "permissions_error", "detail": { "message": "Email not verified", "code": "email-not-verified" Steps to resolve: 1. Verify the email: • The API call to PandaDoc is being rejected because the email associated with your API key isn’t verified. You’ll need to verify the email address tied to your PandaDoc account. 2. Retry the request: • Once the email is verified, try sending the API request again, and it should resolve the issue. If the problem continues after verifying the email, feel free to reach out—I’m happy to assist further! 😊 Best of luck with everything!
Ben C.
·
·
Thanks for your help Bo. My pandadoc uses benjaminjcrane+1@gmail.com, while my clay email is benjaminjcrane@gmail.com. Could youshow me where i could alter my email in the integration ? thank you
Loading attachments
Bo (.
·
·
So this error is entirely from Pandadoc, you would need to reach out to them to get your email verified there. Not with us 🙂
Bo (.
·
·
By the way, this thread has been dropped and hasn’t been picked up again. For any further questions, feel free to create a new thread, as I might not see this one. 😊
1

Ben C.
·
·
https://app.clay.com/workspaces/34750/tables/t_vSiQg5AbJEzc/views/gv_u2KhymQtrvmA
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Ben C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 🔒[private user].
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Ben C.
·
·
https://www.loom.com/share/b8ae4644f21c4bcb82f041d2cafd08e7 still running into the issue 😞
Ben C.
·
·
deleted the "bearer" and same issue unfortunately
Bo (.
·
·
Hey Ben, I saw your message in Slack, but it looks like you might have missed my replies. It seems like some changes were made again, which brought us back to square one. Did you verify your email as instructed? I've remade the changes so you could see that error again:
Bo (.
·
·
This was my previous message just in case: Hey Benjamin, Jetlag really does suck—good luck with your interview tomorrow! 😅 The video was super helpful, thanks for that! So the issue turned out to be with the Authorization header—it should be formatted as API-Key {yourapikey}. I’ve added that into the table, but now I’m getting another issue. It failed again due to a 403 Forbidden error, and the error message indicates that the email is not verified: "type": "permissions_error", "detail": { "message": "Email not verified", "code": "email-not-verified" Steps to resolve: 1. Verify the email: • The API call to PandaDoc is being rejected because the email associated with your API key isn’t verified. You’ll need to verify the email address tied to your PandaDoc account. 2. Retry the request: • Once the email is verified, try sending the API request again, and it should resolve the issue. If the problem continues after verifying the email, feel free to reach out—I’m happy to assist further! 😊 Best of luck with everything!
Ben C.
·
·
Thanks for your help Bo. My pandadoc uses benjaminjcrane+1@gmail.com, while my clay email is benjaminjcrane@gmail.com. Could youshow me where i could alter my email in the integration ? thank you
Loading attachments
Bo (.
·
·
So this error is entirely from Pandadoc, you would need to reach out to them to get your email verified there. Not with us 🙂
Bo (.
·
·
By the way, this thread has been dropped and hasn’t been picked up again. For any further questions, feel free to create a new thread, as I might not see this one. 😊
1