Delivery Modalities
Once a workflow is designed, it can be delivered to end-users, employees, or partners through three primary modalities:
- Hosted Public Share Links (Zero-code web portals)
- Embedded Client SDKs (Web, React Native, Flutter)
- Headless Server-to-Server REST APIs
1. Hosted Public Share Links
Hosted Share Links allow you to generate a secure, standalone URL for any active workflow directly from the dashboard. This allows you to onboard users or vendors without writing a single line of frontend code.
Access Control & Security Modes
When generating a share link, you can configure strict security parameters:
| Setting | Options | Behavior |
|---|---|---|
| Access Mode | public | restricted_email | In restricted_email mode, only pre-authorized emails can access the verification session. |
| OTP Verification | true | false | Enforces a one-time password sent to the applicant's email or phone before starting. |
| Usage Mode | single_use | reusable | single_use links expire immediately upon first completion or attempt. |
| Expiration Date | ISO 8601 Timestamp | Automatically revokes link validity after a designated date and time. |
2. Branding Customization
Ensure hosted verification links match your corporate brand identity seamlessly. Under Settings > Widget Branding (or via per-workflow branding overrides), you can configure:
- Brand Assets: Custom organization logo, mobile app icon, and favicon.
- Color Palette: Brand primary color, secondary accent, border radius, and surface tints.
- Typography: Custom font families matching your web presence.
- Theme Modes: Force light mode, force dark mode, or adapt to the user's system preferences.
3. Client SDK Integration
For applications that require deeply integrated, in-app experiences, Prembly provides native SDKs that launch verification flows inside modals or native viewports:
import Prembly from '@prembly/verify-web';
const verify = new Prembly({
widgetId: 'YOUR_WORKFLOW_CONFIG_ID',
onSuccess: (response) => {
console.log('Verification completed:', response.process_id);
},
onError: (error) => {
console.error('Verification error:', error);
},
onClose: () => {
console.log('User closed modal');
}
});
verify.open();4. Headless REST API
If you prefer to maintain full control over your frontend UI, you can trigger workflows server-to-server and submit step inputs via API:
curl -X POST https://api.prembly.com/api/v1/processes/ \
-H "X-API-Key: YOUR_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_123456789",
"customer": {
"first_name": "Jane",
"last_name": "Doe",
"email": "jane@example.com"
}
}'The system executes the workflow, evaluates decisions in the background, and streams status updates directly to your registered webhook URL.