URL Scheme Overview
Base URL: timelined://
Available Actions
1. Create Event
timelined://create?[parameters]
2. Open Event
timelined://open?uuid=[event-uuid]
Parameters Reference
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
title | String | Yes | Event title | title=Team Meeting |
subtitle | String | No | Event subtitle/tagline | subtitle=Important milestone |
description | String | No | Event description | description=Weekly team sync |
date | String | Yes | Start date (see date formats) | date=2024-01-15T14:30:00Z |
endDate | String | No | End date (see date formats) | endDate=2024-01-15T15:30:00Z |
category | String | No | Category name | category=Work |
type | String | No | Event type name | type=Meeting |
location | String | No | Location address | location=New York, NY |
people | String | No | Comma-separated people names | people=John Doe,Jane Smith |
tags | String | No | Comma-separated tag names | tags=important,urgent |
edit | Boolean | No | Show form for editing | edit=true |
callback | URL | No | Callback URL for results | callback=myapp://result |
Date Format Support
Timelined supports multiple date formats with automatic precision detection:
Supported Formats
| Format | Example | Precision | Display |
|---|---|---|---|
| ISO 8601 | 2024-01-15T14:30:00Z | Full | “January 15, 2024 at 2:30 PM” |
| Date Only | 2024-01-15 | Date only | “January 15, 2024” |
| Month/Year | 2024-01 | Month only | “January 2024” |
| Year Only | 2024 | Year only | “2024” |
Date Format Examples
// Full precision with time
date=2024-01-15T14:30:00Z
date=2024-01-15T14:30:00+00:00
// Date only (no time)
date=2024-01-15
// Month and year only
date=2024-01
// Year only
date=2024
URL Encoding
All parameters must be properly URL-encoded. Special characters should be encoded:
| Character | Encoded |
|---|---|
| Space | %20 or + |
| & | %26 |
| = | %3D |
| ? | %3F |
| # | %23 |
| % | %25 |
URL Encoding Best Practices
Why URL Encoding is Important
URL encoding ensures that special characters, spaces, and non-ASCII characters are properly transmitted in URLs. Without proper encoding, URLs may break or be misinterpreted.
Shortcuts App Encoding
In Shortcuts, use the “URL Encode Input” action to properly encode text:
- Add Action: “Text” action with your content
- Add Action: “URL Encode Input” action
- Connect: Text action to URL Encode Input action
- Use: The encoded output in your URL
Encoded URLs
Before and After Examples
| Original | Encoded |
|---|---|
title=Team Meeting | title=Team%20Meeting |
title=Q&A Session | title=Q%26A%20Session |
description=Meeting (important) | description=Meeting%20%28important%29 |
location=San Francisco, CA | location=San%20Francisco%2C%20CA |
Complete URL Examples
Original (will break):
timelined://create?title=Team Meeting & Discussion&description=Meeting (important)&location=San Francisco, CA
Properly Encoded:
timelined://create?title=Team%20Meeting%20%26%20Discussion&description=Meeting%20%28important%29&location=San%20Francisco%2C%20CA
Basic Examples
Simple Event Creation
timelined://create?title=Team%20Meeting&date=2024-01-15T14:30:00Z&category=Work&type=Meeting
Event with Description
timelined://create?title=Project%20Review&subtitle=Q1%20Review&description=Review%20project%20progress%20and%20plan%20next%20quarter&date=2024-01-15&category=Work&type=Review
Event with Location
timelined://create?title=Client%20Meeting&date=2024-01-15T10:00:00Z&location=San%20Francisco%2C%20CA&category=Work&type=Meeting
Event with People and Tags
timelined://create?title=Birthday%20Party&date=2024-01-15&people=John%20Doe%2CJane%20Smith%2CBob%20Wilson&tags=celebration%2Cpersonal&category=Personal&type=Party
Historical Event (Year Only)
timelined://create?title=Company%20Founded&date=1995&category=Business&type=Foundation&description=Company%20was%20established
Event with End Date
timelined://create?title=Conference&date=2024-01-15&endDate=2024-01-17&category=Professional&type=Conference&location=Austin%2C%20TX
Event with Special Characters
timelined://create?title=Meeting%20%26%20Discussion&subtitle=Q%26A%20Session&description=Team%20meeting%20with%20Q%26A%20session%20%28important%29&date=2024-01-15&category=Work&type=Meeting
Event with Complex Description
timelined://create?title=Product%20Launch&description=Launch%20of%20our%20new%20product%20line.%20Features%20include%3A%0A%0A-%20Advanced%20analytics%0A-%20Real-time%20updates%0A-%20Cloud%20integration&date=2024-01-15&category=Business&type=Launch
Callback Functionality
How Callbacks Work
When you include a callback parameter, Timelined will open the callback URL with result information after the operation completes.
Callback URL Format
[your-callback-url]?success=[true/false]&uuid=[event-uuid]&message=[result-message]
Callback Parameters
| Parameter | Type | Description |
|---|---|---|
success | Boolean | Whether the operation was successful |
uuid | String | UUID of the created/opened event (if successful) |
message | String | Human-readable result message |
Callback Examples
Successful Event Creation
myapp://result?success=true&uuid=123e4567-e89b-12d3-a456-426614174000&message=Event created successfully
Failed Event Creation
myapp://result?success=false&message=Failed to create event: Invalid date format
Event Opened
myapp://result?success=true&uuid=123e4567-e89b-12d3-a456-426614174000&message=Event opened successfully
Shortcuts App Integration
Basic Shortcut: Create Simple Event
- Add Action: “URL” action
- Set URL:
timelined://create?title=Quick%20Event&date=2024-01-15&category=Personal - Add Action: “Open URL” action
- Connect: URL action to Open URL action
