Skip to main content

​
Overview

The fallback endpoint provides sample project data for Zapier trigger testing and configuration. When setting up a “New Project” 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 project data when available, or consistent sample data for testing when your workspace has no projects 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/projects/fallback' \
  -H 'Authorization: Bearer YOUR_API_KEY'

​
Response

​
Success Response

Returns an array containing one project object - either your most recent project or sample data: 
[
  {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "name": "New Mobile App Project",
    "description": "Development of a new mobile application",
    "status": "active",
    "workspace": {
      "id": "345e6789-e89b-12d3-a456-426614174004",
      "name": "Development Team"
    },
    "client": {
      "id": "456e7890-e89b-12d3-a456-426614174001",
      "name": "Tech Startup Inc.",
      "email": "[email protected]",
      "phone": "+1-555-0123",
      "status": "active",
      "type": "company"
    },
    "defaultBillable": true,
    "defaultBillableRate": 75.0,
    "estimatedHours": 200.0,
    "estimatedBudget": 15000.0,
    "isPrivate": false,
    "createdAt": "2024-01-15T10:00:00.000Z",
    "updatedAt": "2024-01-15T10:00:00.000Z"
  }
]

​
Data Fields

​
id
string
Unique project identifier (UUID format)
​
name
string
Project name
​
description
string
Project description
​
status
string
Current project status
  • active - Project is currently active
  • inactive - Project is temporarily inactive
  • completed - Project has been completed
  • cancelled - Project has been cancelled
​
workspace
object
Associated workspace information
​
client
object
Associated client information
​
defaultBillable
boolean
Whether time entries are billable by default for this project
​
defaultBillableRate
number
Default hourly rate for billable time entries
​
estimatedHours
number
Estimated total hours for the project
​
estimatedBudget
number
Estimated total budget for the project
​
isPrivate
boolean
Whether the project is private (restricted access)
​
createdAt
string
ISO 8601 timestamp when project was created
​
updatedAt
string
ISO 8601 timestamp when project 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 projects"
}
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 projects, you’ll receive this consistent sample data: 
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "name": "Sample Mobile App Project",
  "description": "Development of a sample mobile application",
  "status": "active",
  "workspace": {
    "id": "345e6789-e89b-12d3-a456-426614174004",
    "name": "Sample Development Team"
  },
  "client": {
    "id": "456e7890-e89b-12d3-a456-426614174001",
    "name": "Sample Tech Startup Inc.",
    "email": "[email protected]",
    "phone": "+1-555-0123",
    "status": "active",
    "type": "company"
  },
  "defaultBillable": true,
  "defaultBillableRate": 75.0,
  "estimatedHours": 200.0,
  "estimatedBudget": 15000.0,
  "isPrivate": false,
  "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 “New Project” trigger in Zapier, it automatically calls this endpoint to fetch sample data.
2

Data Structure Display

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

Field Mapping Setup

You can map specific project fields (like name, description, client.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 “New Project” triggers to show them what data will be available.
Development Use: Test your integration logic with consistent, predictable data structures before connecting to live project creation events.
Reference Use: Use the returned data structure to document what fields are available in your project management workflows.
Testing Use: Validate that your automation workflows can handle all the project 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 project 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
  • Project IDs are always UUIDs for reliable identification
  • Client information is included when available
  • Budget and rate fields use decimal numbers for precision

​
Testing Your Integration

To test how your application handles project data:
  1. Call the endpoint with your API credentials
  2. Parse the response and extract the first project 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
This ensures your integration works smoothly when real project data starts flowing through webhooks.