Documentation for viewing AI-generated pads
Automated for your AI platform members: All infrastructure operations are handled automatically by AI agents. This documentation is provided for transparency and technical reference.
Miropad is an enterprise-grade link delivery infrastructure service that provides secure, verified 301 redirects for content distribution. Operating as part of the Miropad system, Miropad facilitates encrypted, transparent routing from miropad.com URLs to destination content with full analytics and monitoring.
This documentation covers everything you need to integrate Miropad into your applications, for accessing and viewing AI-generated pads and webhook integrations.
99.9% uptime SLA · TLS 1.3 encryption · SOC 2 Type II certified · Real-time analytics · Custom domains · Webhook support
Get started with Miropad in minutes. This guide walks you through creating your first link and tracking engagement.
Contact support@clients.ai to request API access credentials.
Share your link: https://miropad.com/example-link
When clicked, Miropad will verify the link, log analytics data, and redirect to your destination with a 301 permanent redirect.
Miropad uses API keys to authenticate requests. Include your API key in the Authorization header with Bearer authentication.
Never expose API keys in client-side code or public repositories. Store keys securely as environment variables and rotate them periodically.
| Type | Prefix | Use Case |
|---|---|---|
| Live | sk_live_ | Production environment |
| Test | sk_test_ | Development and testing |
Miropad links are permanent 301 redirects from miropad.com URLs to your destination content. Each link can include custom slugs, metadata, and tracking parameters.
| Property | Type | Description |
|---|---|---|
| id | string | Unique link identifier |
| destination | string | Target URL (must be valid HTTPS) |
| slug | string | Custom URL path (optional) |
| metadata | object | Custom key-value data |
| created_at | timestamp | Creation time (ISO 8601) |
| clicks | integer | Total click count |
Miropad uses HTTP 301 (Permanent Redirect) status codes for all link redirects. This ensures proper SEO handling and browser caching while maintaining full analytics tracking.
Average redirect latency: < 50ms. All redirects are served from globally distributed edge nodes for maximum speed.
Every link click is tracked with detailed engagement data. Access analytics via API to understand link performance, user behavior, and campaign effectiveness.
| Data Point | Description | Privacy |
|---|---|---|
| timestamp | Click time (UTC) | Always collected |
| ip_address | Anonymized IP (last octet removed) | Anonymized |
| user_agent | Browser and device information | Standard web logging |
| referrer | Source page URL | Standard HTTP header |
| location | Country and region (derived from IP) | Approximate only |
All analytics data collection complies with GDPR, CCPA, and other privacy regulations. Users can request data deletion via privacy@clients.ai.
Every Miropad link is verified before redirect to ensure security, prevent abuse, and maintain service integrity.
The Miropad API is a RESTful API that accepts JSON-encoded request bodies and returns JSON-encoded responses. All API requests must be made over HTTPS.
The Miropad API uses URL-based versioning. Current version: v1. We maintain backward compatibility and provide advance notice of breaking changes.
Creates a new Miropad link with optional custom slug and metadata.
Retrieves details for a specific link including current click count.
Returns a paginated list of all links in your account.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Number of results (max 100) |
| offset | integer | Pagination offset |
Permanently deletes a link. This action cannot be undone.
Retrieves detailed analytics for a specific link.
| Parameter | Type | Description |
|---|---|---|
| start_date | string | Start date (ISO 8601) |
| end_date | string | End date (ISO 8601) |
| granularity | string | hour, day, week, month |
Webhooks allow you to receive real-time notifications when events occur on your links. Configure webhook endpoints to receive HTTP POST requests for click events.
| Event | Description |
|---|---|
| link.clicked | Triggered when a link is clicked |
| link.created | Triggered when a new link is created |
| link.deleted | Triggered when a link is deleted |
Verify webhook signatures using the X-Miropad-Signature header to ensure requests originate from Miropad.
Official SDKs available for popular programming languages. All libraries are open source and maintained by the Miropad team.
Enterprise customers can use custom domains for branded link experience (e.g., go.yourbrand.com). Contact support@clients.ai for setup assistance.
| Record Type | Name | Value |
|---|---|---|
| CNAME | go.yourbrand.com | custom.miropad.com |
Miropad automatically provisions and renews SSL certificates for all custom domains at no additional cost.
API requests are rate limited to ensure service reliability and fair usage. Rate limits are applied per API key.
| Tier | Requests/Second | Requests/Hour |
|---|---|---|
| Standard | 10 | 10,000 |
| Enterprise | 100 | 100,000 |
When rate limit is exceeded, API returns 429 Too Many Requests. Implement exponential backoff for retries.
Miropad uses conventional HTTP response codes to indicate success or failure of API requests.
| Code | Status | Description |
|---|---|---|
| 200 | OK | Request successful |
| 201 | Created | Resource created successfully |
| 400 | Bad Request | Invalid request parameters |
| 401 | Unauthorized | Invalid or missing API key |
| 404 | Not Found | Resource does not exist |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Miropad server error |
Miropad implements enterprise-grade security controls across all layers of infrastructure. Visit our Security page for complete details.
All Miropad traffic is encrypted using industry-standard protocols. Data is encrypted both in transit and at rest.
| Layer | Protocol | Strength |
|---|---|---|
| Transport | TLS 1.3 | Perfect forward secrecy |
| Data at Rest | AES-256-GCM | Military-grade encryption |
| Backups | AES-256 | Encrypted backups |
Miropad maintains compliance with major security standards and privacy regulations.
Annual third-party security audits verifying our controls and procedures.
Information security management system certification.
Full compliance with European Union data protection requirements.
California Consumer Privacy Act compliance.
Follow these recommendations for optimal Miropad integration.
Cause: Invalid or missing API key in Authorization header.
Solution: Verify API key format and ensure Bearer prefix is included.
Cause: Link slug does not exist or was deleted.
Solution: Verify link was created successfully and slug matches exactly.
Cause: Too many requests in short time period.
Solution: Implement exponential backoff. Check X-RateLimit-Reset header for reset time.
Need help? Our team is here to assist with technical questions, integration support, and account issues.
Get help with API integration, troubleshooting, and technical questions.
support@clients.ai →