Storipress API is written in GraphQL. This forum post will show how you can integrate GraphQL APIs inside Pabbly Connect.
We are taking the example of signUpSubsriber Endpoint and will add the same to Pabbly Connect.
Authorization
The authorization of the Storipress API is done through Bearer Access Token. More details below.
Notice 3 things in the image below.
1. The subdomain: The default is api as the subdomain in api.stori.press. We will keep it as a dynamic variable while building the integration as a safety measure just incase the subdomain is changed in future. We will also use the default value as api in that variable. This is an optional thing to do down below while building action inside Pabbly Connect.
2. client_id: This would be received by the user from the Storipress account. We will ask the users to enter it on Pabbly Connect.
3. Authorization is Bearer Type and the access_token for same will also be received by the user from the Storipress account. We will ask the users to enter it on Pabbly Connect.
Query
Variables
Response
Running same API inside Postman:
1. Setting Authorization as Bearer Token
2. Running the API and copying the CURL request from Postman to use the same on Pabbly Connect.
This is how the app is connected and built inside Pabbly Connect. This is the App Detail dashboard.
1. Enabling Bearer Token will take care of the access_token. Users will be asked for the bearer token(access_token) during the authentication.
2. We used client_id as a global parameter on the application level.
3. We use subdomain variable as a global parameter on the application level.
Inside of client_id variable, Appears on pressing the gear icon.
Inside of subdomain variable, appears on pressing the gear icon.
This is how the action is setup for the Sign Up Subscriber endpoint.
Inside of the email parameter. Other parameteres referrer and from are setup the similar way.
This is the final integration on the Pabbly Connect platform. Completely built.
Image 1: Selecting Storipress App with Sign Up Subscriber Endpoint.
Image 2: On pressing Connect
Image 3: After execution
We are taking the example of signUpSubsriber Endpoint and will add the same to Pabbly Connect.
Authorization
The authorization of the Storipress API is done through Bearer Access Token. More details below.
Notice 3 things in the image below.
1. The subdomain: The default is api as the subdomain in api.stori.press. We will keep it as a dynamic variable while building the integration as a safety measure just incase the subdomain is changed in future. We will also use the default value as api in that variable. This is an optional thing to do down below while building action inside Pabbly Connect.
2. client_id: This would be received by the user from the Storipress account. We will ask the users to enter it on Pabbly Connect.
3. Authorization is Bearer Type and the access_token for same will also be received by the user from the Storipress account. We will ask the users to enter it on Pabbly Connect.
Query
Variables
Response
Running same API inside Postman:
1. Setting Authorization as Bearer Token
2. Running the API and copying the CURL request from Postman to use the same on Pabbly Connect.
This is how the app is connected and built inside Pabbly Connect. This is the App Detail dashboard.
1. Enabling Bearer Token will take care of the access_token. Users will be asked for the bearer token(access_token) during the authentication.
2. We used client_id as a global parameter on the application level.
3. We use subdomain variable as a global parameter on the application level.
Inside of client_id variable, Appears on pressing the gear icon.
Inside of subdomain variable, appears on pressing the gear icon.
This is how the action is setup for the Sign Up Subscriber endpoint.
Inside of the email parameter. Other parameteres referrer and from are setup the similar way.
This is the final integration on the Pabbly Connect platform. Completely built.
Image 1: Selecting Storipress App with Sign Up Subscriber Endpoint.
Image 2: On pressing Connect
Image 3: After execution
Attachments
Last edited:
