Skip to main content

​
Overview

The fallback endpoint provides sample manual time entry data for Zapier trigger testing and configuration. When setting up a “Manual Time Entry” trigger, Zapier uses this endpoint to show users the expected data structure, making it easier to configure workflows before activating live webhook subscriptions.
This endpoint intelligently returns your most recent manual time entry data when available, or consistent sample data for testing when your workspace has no manual time entries yet.

​
Authentication

All requests require a valid API key in the Authorization header: 
Authorization: Bearer YOUR_API_KEY

​
Get Sample Data

curl -X GET 'https://app.timetracker.in/api/integrations/zapier/triggers/time-entries/manual_entry/fallback' \
  -H 'Authorization: Bearer YOUR_API_KEY'

​
Response

​
Success Response

Returns an array containing one manual time entry object - either your most recent manual time entry or sample data: 
[
  {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "description": "Working on user authentication implementation",
    "date": "2024-01-15T00:00:00.000Z",
    "startTime": "2024-01-15T10:00:00.000Z",
    "endTime": "2024-01-15T12:30:00.000Z",
    "duration": 9000,
    "billable": true,
    "action": "manual_entry",
    "workspace": {
      "id": "abc12345-e89b-12d3-a456-426614174003",
      "name": "Development Team"
    },
    "teamMember": {
      "id": "def67890-e89b-12d3-a456-426614174004",
      "name": "John Doe"
    },
    "project": {
      "id": "456e7890-e89b-12d3-a456-426614174001",
      "name": "Mobile App Development"
    },
    "task": {
      "id": "789e0123-e89b-12d3-a456-426614174002",
      "name": "Implement user authentication"
    },
    "tags": [
      {
        "id": "ghi11111-e89b-12d3-a456-426614174005",
        "name": "authentication"
      },
      {
        "id": "jkl22222-e89b-12d3-a456-426614174006",
        "name": "mobile"
      }
    ],
    "createdAt": "2024-01-15T10:00:00.000Z",
    "updatedAt": "2024-01-15T10:00:00.000Z"
  }
]

​
Data Fields

​
id
string
Unique time entry identifier (UUID format)
​
description
string
Time entry description
​
date
string
Date of the time entry in ISO 8601 format
​
startTime
string
Time entry start time in ISO 8601 format
​
endTime
string
Time entry end time in ISO 8601 format
​
duration
integer
Total duration in seconds (e.g., 9000 = 2.5 hours)
​
billable
boolean
Whether the time entry is billable
​
action
string
Action type - always "manual_entry" for this trigger
​
workspace
object
Associated workspace information
​
teamMember
object
Team member who created the manual entry
​
project
object
Associated project information
​
task
object
Associated task information
​
tags
array
Array of tags associated with the time entry
​
createdAt
string
ISO 8601 timestamp when time entry was created
​
updatedAt
string
ISO 8601 timestamp when time entry was last modified

​
Error Responses

{
  "error": "Unauthorized"
}
Cause: Invalid or missing API key
Solution: Verify your API key is correct and properly formatted
{
  "error": "Failed to fetch time entries"
}
Cause: Server-side error during data retrieval
Solution: Retry the request or contact support if the issue persists

​
Sample Data Format

When your workspace has no manual time entries, you’ll receive this consistent sample data: 
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "description": "Working on sample task implementation",
  "date": "2024-01-15T00:00:00.000Z",
  "startTime": "2024-01-15T10:00:00.000Z",
  "endTime": "2024-01-15T12:30:00.000Z",
  "duration": 9000,
  "billable": true,
  "action": "manual_entry",
  "workspace": {
    "id": "abc12345-e89b-12d3-a456-426614174003",
    "name": "Sample Development Team"
  },
  "teamMember": {
    "id": "def67890-e89b-12d3-a456-426614174004",
    "name": "Sample Developer"
  },
  "project": {
    "id": "456e7890-e89b-12d3-a456-426614174001",
    "name": "Sample Project"
  },
  "task": {
    "id": "789e0123-e89b-12d3-a456-426614174002",
    "name": "Sample Task"
  },
  "tags": [
    {
      "id": "ghi11111-e89b-12d3-a456-426614174005",
      "name": "sample"
    },
    {
      "id": "jkl22222-e89b-12d3-a456-426614174006",
      "name": "development"
    }
  ],
  "createdAt": "2024-01-15T10:00:00.000Z",
  "updatedAt": "2024-01-15T10:00:00.000Z"
}

​
Zapier Integration Workflow

​
How Zapier Uses This Endpoint

1

Trigger Configuration

When you set up a “Manual Time Entry” trigger in Zapier, it automatically calls this endpoint to fetch sample data.
2

Data Structure Display

Zapier shows you the returned manual time entry data structure, including all available fields and their formats.
3

Field Mapping Setup

You can map specific time entry fields (like description, duration, project.name, task.name) to actions in your workflow.
4

Testing & Validation

Use the sample data to test your workflow logic before activating live webhook notifications.
5

Production Activation

Once configured, Zapier switches to receiving real-time data via webhook subscriptions.
Pro Tip: The data structure shown during setup matches exactly what you’ll receive in live webhook payloads, so you can confidently design your workflows around the sample data.

​
Use Cases

Primary Use: Zapier automatically calls this endpoint when users configure “Manual Time Entry” triggers to show them what data will be available.
Development Use: Test your integration logic with consistent, predictable data structures before connecting to live manual time entry events.
Reference Use: Use the returned data structure to document what fields are available in your time tracking workflows.
Testing Use: Validate that your automation workflows can handle all the time entry data fields before going live.

​
Important Notes

Data Consistency Guarantee: The structure returned by this endpoint exactly matches the webhook payload format, ensuring seamless transition from testing to production.
Workspace Isolation: Only returns real time entry data from your authenticated workspace. Cross-workspace data access is prevented for security.
Integration Best Practices:
  • Always test your workflows with this sample data first
  • The endpoint returns an array, so access the first element: data[0]
  • All dates use ISO 8601 format for consistent parsing
  • Time entry IDs are always UUIDs for reliable identification
  • Duration is always in seconds for precise calculations
  • Tags arrays may be empty for entries with no tags
  • Action field is always "manual_entry" for this trigger
  • Both start and end times are always present for manual entries

​
Testing Your Integration

To test how your application handles manual time entry data:
  1. Call the endpoint with your API credentials
  2. Parse the response and extract the first time entry object
  3. Validate data types match your expected formats
  4. Test field mapping for your specific use case
  5. Handle edge cases like missing optional fields or empty arrays
This ensures your integration works smoothly when real manual time entry data flows through webhooks.