Use API keys and Shortcuts
Connect repeatable capture or transcription workflows without exposing secrets.
- Audience
- Developers and power users wiring Vowise into existing workflows.
- Time
- 18 minutes
- Level
- Advanced
Scenario
Start with the workflow this guide is designed for before moving into the steps.
As an automation builder, I want a repeatable way to send audio to Vowise so I can connect capture tools without manually uploading files.
You know where API keys fit, how to test the public reference, and which secret-handling rules to follow.
Complete steps
Create or locate an API key
Use the account surface intended for API keys. Treat the key as a secret, not as public tutorial content.
Test the public API reference
Use `/api-reference` to understand the public transcription and dictionary request shape before putting it in automation.
Build the automation wrapper
Wrap the request in Shortcuts, a local script, or a server-side workflow that can keep the key private.
Details
Secret handling rules
Docs can teach the request shape, but examples should use placeholders instead of real secrets, reusable passwords, or private URLs.
- Use placeholders in docs and screenshots.
- Keep real keys in local secret stores or server-side config.
- Rotate a key if it appears in a public recording.
Connected feature paths
This tutorial should not dead-end. These are the natural next features and workflows it connects to.
Create a custom dictionary
Protect names, brands, acronyms, and domain terms during transcription.
Troubleshoot common issues
Fix recording, permissions, transcript quality, API, and media capture issues.
Start with Vowise
Pick the right first workflow: record, import, review, or automate.