Provision
Keep the single owner API credential in your server secret store.
01 Integrations
Place Zulde between your system and the shared access layer.
A small API surface makes Zulde straightforward to call from procurement, CRM, supplier, or customer operations tools.
Open with a code →
02 Process
A visible sequence with a protected core.
Issue
Send one recipient email to POST /end/delivery.
Share
Deliver the returned six-character code through your existing channel.
Revoke
Disable the code through the API when access should end.
03 Detail
Built around a smaller access surface.
Your system owns delivery
Zulde returns the code and local share URL but does not send email or SMS in the first release.
- No messaging credentials
- No email templates
- No delivery tracking
Downstream stays separate
Destination creation remains the responsibility of the dedicated shared service, reached only from the Zulde server.
- No browser API key
- No stored destination
- Dedicated site identity