Hi @Ilinca
I’m using this plugin to build for a client. We already have Sumsub integrated with their app, now they want to build a specific feature to allow enterprise users to add documents to applicants via API.
To achieve that, we created a backend workflow with API enabled. This workflow receives an applicant’s unique id (which is used to find the applicant on Bubble and fetch its Sumsub applicant id), metadata and the document file. Because Bubble needs to receive the document file through API, it’s been sent as a JSON object containing the file name and its content base64 encoded, which is a known method to do that.
Inside the workflow we have actions from Zeroqode’s plugin:
- The “API Health” action to check the API status;
- The “Adding ID Document” action to effectively send the document to Sumsub;
- A “Return data from API” to send back to the client information like the plugin response, API health status, document ID and an eventual error message;
When we try the backend workflow’s endpoint on Postman though, we receive the following response containing no error message, stating that the API health is ok, but no response.
No error is shown in the app’s logs too, and if I copy the file URL and paste it into my browser, I can see the document image as expected. This leads me to think that an error is being generated in the plugin’s integration with Sumsub, but it’s not being transmitted to our side.
I would appreciate it if you could test this action and help me set it correctly. Please let me know if you need any help to replicate the issue, or more details from my side.
Thanks,
Vini