Snapshots
Snapshots allow you to create permanent, shareable copies of webhook requests for documentation, collaboration, and archival purposes.
What is a Snapshot?
A snapshot is an immutable, publicly accessible copy of a webhook request that includes:
- Complete request details (headers, body, query params)
- Timestamp and metadata
- Public URL for sharing
- Permanent url
- Optional comments and notes
Creating a Snapshot
From Request Details
- Open the request you want to snapshot
- Click the "Create Snapshot" button
- Click "Create"
- Copy the public URL to share
Snapshot Button
Snapshot URL Format
https://app.h00k.dev/snapshot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Use Cases
Documentation
Create examples for API documentation
Bug Reports
Share problematic requests with your team or support:
- Create snapshot of failing request
- Add comments describing the issue
- Share URL in bug tracker or chat
Team Collaboration
Discuss webhook behavior with teammates:
- Add comments to snapshots
- Reference in code reviews
- Use in pull request descriptions
Training & Onboarding
Create a library of example webhooks for new team members.
Snapshot Features
Public Access
- No authentication required to view snapshots
- Anyone with the URL can access
- Perfect for sharing with external teams
- Consider data sensitivity before creating
Permanent Storage
- Snapshots never expire automatically
- Remain accessible indefinitely
- Can only be deleted by creator
- Not affected by bin retention periods
Comments System
Add context and notes to snapshots:
- Describe what the request represents
- Explain why it's important
- Document expected vs actual behavior
- Collaborate with team via comments
Managing Snapshots
View Your Snapshots
Authenticated users only:
- Go to your Dashboard
- Click "Snapshots" tab
- See all your created snapshots
- Filter by date or bin
Delete a Snapshot
- Open the snapshot
- Click "Delete" (only visible to creator)
- Confirm deletion
- Snapshot URL becomes invalid
Note: Deletion is permanent and cannot be undone.
Snapshot Limits
| User Type | Limit |
|---|---|
| Anonymous | 10 per session |
| Registered | 100 |
| Pro | 1,000 |
Best Practices
✅ DO
- Include relevant comments and context
- Use for documentation and examples
- Create snapshots of important/interesting requests
- Share with team for collaboration
❌ DON'T
- Snapshot requests with sensitive data (passwords, tokens)
- Create excessive snapshots (they never expire)
- Share snapshot URLs publicly if data is confidential
- Rely on snapshots for long-term data storage beyond examples
Privacy & Security
Data Visibility
- Snapshots are publicly accessible by URL
- No authentication required to view
- Consider data sensitivity before creating
- Remove sensitive data before snapshotting
Recommended Practices
- Review request content before creating snapshot
- Redact sensitive information manually if needed
- Use generic example data for public documentation
- Keep confidential snapshots private (don't share URLs)
Related Topics
- Bins: Learn about webhook endpoints
- Forward Requests: Forward webhooks to your server
- Mock Responses: Create mock API responses
Questions? Contact us at support@h00k.dev