Skip to main content

​
Overview

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

​
Response

​
Success Response

Returns an array containing one client object - either your most recent client or sample data: 
[
  {
    "id": "c1a2b3c4-d5e6-7890-abcd-ef1234567890",
    "name": "Acme Corporation",
    "email": "[email protected]",
    "phone": "+1-800-555-0199",
    "address": "456 Innovation Drive, Silicon Valley, CA 94043",
    "status": "active",
    "type": "company",
    "workspace": {
      "id": "w1b2c3d4-e5f6-7890-abcd-ef0987654321",
      "name": "Acme Main Workspace"
    },
    "createdAt": "2024-01-15T10:30:00Z",
    "updatedAt": "2024-01-15T10:30:00Z"
  }
]

​
Data Fields

​
id
string
Unique client identifier (UUID format)
​
name
string
Client or company name
​
email
string
Primary contact email address
​
phone
string
Contact phone number with country code
​
address
string
Complete business or mailing address
​
status
string
Current client status
  • active - Client is currently active
  • inactive - Client is temporarily inactive
​
type
string
Client classification
  • company - Business or organization
  • individual - Individual person
​
workspace
object
Associated workspace information
​
createdAt
string
ISO 8601 timestamp when client was created
​
updatedAt
string
ISO 8601 timestamp when client 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 clients"
}
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 clients, you’ll receive this consistent sample data: 
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "name": "Sample Tech Startup Inc.",
  "email": "[email protected]",
  "phone": "+1-555-0123",
  "address": "123 Sample Street, Sample City, SC 12345",
  "status": "active",
  "type": "company",
  "workspace": {
    "id": "456e7890-e89b-12d3-a456-426614174001",
    "name": "Sample Workspace"
  },
  "createdAt": "2024-01-15T10:30:00Z",
  "updatedAt": "2024-01-15T10:30:00Z"
}

​
Zapier Integration Workflow

​
How Zapier Uses This Endpoint

1

Trigger Configuration

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

Data Structure Display

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

Field Mapping Setup

You can map specific client fields (like name, email, phone) 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 Client” triggers to show them what data will be available.
Development Use: Test your integration logic with consistent, predictable data structures before connecting to live client creation events.
Reference Use: Use the returned data structure to document what fields are available in your client management workflows.
Testing Use: Validate that your automation workflows can handle all the client 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 client 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
  • Client IDs are always UUIDs for reliable identification
  • Phone numbers include country codes when available

​
Testing Your Integration

To test how your application handles client data:
  1. Call the endpoint with your API credentials
  2. Parse the response and extract the first client 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 client data starts flowing through webhooks.