• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

API integration with Spoki

P

Pabblymember11

Guest
Hey @PerformancePPC

Regarding your concern about using the action step of Spoki, you can use the API by Pabbly action step and with the help of Spoki's API documentation you can use its API in your workflow.

1701082070241.png


For a better understanding of the use of API by Pabbly, you can refer to the following video lesson.


Additionally, you have the option to submit the form on our platform https://pabbly.featureos.app/b/Feature-Request. Our integration team will then review it and implement the necessary connections on the platform to accommodate your specific integration requirements.
 
Hi @Supreme I already tried it but it doesn't work, it produce an error:



I also tried adding the Secret key (I don't know if it's correct like this):
 
Last edited:
P

Pabblymember11

Guest
Kindly share the API documentation and the workflow URL in which you have tried the same.
 

ArshilAhmad

Moderator
Staff member
Kindly share a screenshot of the endpoint you are trying to execute from this document.

The link you shared above, is not a direct link to the endpoint you are trying to execute.
 
Kindly share a screenshot of the endpoint you are trying to execute from this document.

The link you shared above, is not a direct link to the endpoint you are trying to execute.
Should be this: we need a POST in order to start a specific automation > https://documenter.getpostman.com/v...ext=POST-,Start Automation,-https://app.spoki
 
Hi to all.
An update.
Now I'm trying to create an automation but I keep receiving an error that seems related to authentication when trying to send the template function of my service [docs https://documenter.getpostman.com/v...ki API-,POST,Send Template,-https://app.spoki].

I wanted to understand if I might be setting some authentication fields incorrectly, which could be causing this error.
This the error:
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta name="robots" content="NONE,NOARCHIVE">
<title>403 Forbidden</title>
<style type="text/css">
html * { padding:0; margin:0; }
body * { padding:10px 20px; }
body * * { padding:0; }
body { font:small sans-serif; background:#eee; color:#000; }
body>div { border-bottom:1px solid #ddd; }
h1 { font-weight:normal; margin-bottom:.4em; }
h1 span { font-size:60%; color:#666; font-weight:normal; }
#info { background:#f6f6f6; }
#info ul { margin: 0.5em 4em; }
#info p, #summary p { padding-top:10px; }
#summary { background: #ffc; }
#explanation { background:#eee; border-bottom: 0px none; }
</style>
</head>
<body>
<div id="summary">
<h1>Forbidden <span>(403)</span></h1>
<p>CSRF verification failed. Request aborted.</p>

<p>You are seeing this message because this HTTPS site requires a “Referer header” to be sent by your web browser, but none was sent. This header is required for security reasons, to ensure that your browser is not being hijacked by third parties.</p>
<p>If you have configured your browser to disable “Referer” headers, please re-enable them, at least for this site, or for HTTPS connections, or for “same-origin” requests.</p>
<p>If you are using the <meta name="referrer" content="no-referrer"> tag or including the “Referrer-Policy: no-referrer” header, please remove them. The CSRF protection requires the “Referer” header to do strict referer checking. If you’re concerned about privacy, use alternatives like <a rel="noreferrer" …> for links to third-party sites.</p>


</div>

<div id="explanation">
<p><small>More information is available with DEBUG=True.</small></p>
</div>

</body>
</html>


Screenshot 2024-11-27 alle 17.40.49.png
 
Top