Tallyfy’s “API-first” architecture enables developers to understand exactly how the platform communicates with its backend. By inspecting these API calls, you can more effectively implement your own integrations.
Requirements
Before starting:
Chrome browser (latest version recommended)
A Tallyfy account with appropriate permissions
Basic understanding of HTTP requests and JSON
Familiarity with the Tallyfy feature you want to analyze
Important API Header Requirement
When making direct API calls to Tallyfy endpoints, you must include this header:
X-Tallyfy-Client: APIClient
Capturing API Calls with Chrome DevTools
Setup Process
Open Chrome DevTools
Navigate to the Tallyfy web application and sign in
Right-click anywhere and select Inspect (or press F12)
Alternatively, use keyboard shortcuts:
Windows/Linux: Ctrl+Shift+I or F12
macOS: Cmd+Option+I
The DevTools panel will appear docked to the side or bottom
Access Network Tab
Click the Network tab in the DevTools panel
Ensure recording is enabled (red record button should be active)
Check the Preserve log checkbox to maintain requests between page loads
Select Disable cache to ensure fresh responses
Clear Existing Requests
Click the 🚫 icon to clear all current network requests
This provides a clean slate for capturing only the specific API calls
Perform the Target Action
With Network tab open, perform the action you want to analyze
For example: load a list of processes, launch a new process, or complete a task
The Network tab will populate with requests as they occur
Filter for API Requests
Click the Fetch/XHR filter button at the top of the Network panel
Type /api/ in the filter box to show only Tallyfy API calls
The request list will now display only relevant API calls
Select an API Call
Click any Tallyfy /api/ request in the filtered list
This opens the details pane showing headers, payload, and response
Analyzing Request Details
Request Headers Section
In the Headers tab, examine:
General information:
Request URL: The full endpoint path
Request method: GET, POST, PUT, DELETE, etc.
Status code: 200 (success), 400 (client error), etc.
Request Headers:
Authorization: Bearer <token> for authentication
X-Tallyfy-Client: APIClient required for direct API calls
Content-Type: application/json for data formatting
Response Headers:
Server response metadata
Rate limiting information
Caching directives
Request Payload Section
For POST, PUT, or PATCH requests:
Click the Payload tab to view the request body
Review the following views:
Form Data: URL-encoded parameters
Request Payload: JSON structure
View Source: Raw data exactly as sent
Copy method:
Select the view source tab
Click anywhere in the payload area
Press Ctrl+A (or Cmd+A on Mac) to select all
Press Ctrl+C (or Cmd+C on Mac) to copy
This exact format can be used in your own API implementations
Response Data Section
Examine the server’s response:
Click the Response tab to view raw data returned from the server
Click the Preview tab to see formatted JSON structure
Analyze:
Data objects and their structure
Success/error messages
Pagination information for list responses
Timestamps and formatting patterns
Authentication Analysis
When examining authentication in Tallyfy API calls:
Bearer Token Format: Note the structure and length of the JWT token
Token Lifespan: Tokens typically expire after a set period
Scope Information: What permissions the token includes
User Context: Which user the token represents
Required Headers for API Replication
Header
Value
Purpose
Authorization
Bearer YOUR_TOKEN
Authentication
X-Tallyfy-Client
APIClient
Required identifier
Content-Type
application/json
Format specification
Accept
application/json
Response format
Testing Your API Understanding
To verify you’ve correctly understood an API call:
Copy the endpoint URL, headers, and payload
Use a tool like Postman, Insomnia, or cURL to recreate the request
Compare your response with what you observed in DevTools
Troubleshoot any differences in the responses
Example cURL Command
For a typical API call, your cURL might look like:
To test how your API implementation performs under different conditions:
Click the Network Conditions tab in DevTools (or use the dropdown next to “Online”)
Select a preset throttling profile or create a custom one
Observe how the API behaves with slower connections
Exporting Request Data
To save a request for later reference:
Right-click on the API request
Select Copy > Copy as cURL
Paste into a text file for future reference
Using Integuru for Automated API Integration
For developers looking to automate API interactions with Tallyfy or other platforms, Integuru ↗ provides an advanced solution. Integuru is an open-source AI agent that can generate integration code by reverse-engineering platforms’ internal API
Key features:
Automatically generates a dependency graph of API requests
Creates runnable Python code that reproduces your actions
Identifies relationships between different API calls
Handles authentication and session management
To use Integuru with Tallyfy:
Install Integuru following the instructions on their GitHub repository
Run python create_har.py to start a browser session
Log into Tallyfy and perform the workflow action you want to automate
Use the generated HAR file with Integuru to create Python code that reproduces the API calls
This approach can significantly accelerate API integration development by automatically analyzing the full sequence of API calls needed for complex operations.
Troubleshooting Common Issues
No Requests Appearing
If no API calls appear in DevTools:
Ensure DevTools is open before performing the action
Try enabling Preserve log option in the Network tab
Disable cache and perform a hard refresh (Ctrl+Shift+R or Cmd+Shift+R)
Verify you’re looking at the correct browser tab
Check if content blockers are interfering with network requests
Filtering Problems
If filtering doesn’t show expected results:
Verify the filter string exactly matches part of the API URL
Try the built-in Fetch/XHR filter instead of text filtering
Clear all filters to check if requests appear at all
Ensure your browser isn’t blocking certain requests
Authentication Errors
If calls return HTTP 401 or similar errors:
Verify your Tallyfy session is active
Check that your API token is valid and properly formatted
Ensure all required headers are included in your requests
Confirm your user account has permission for the requested action
Cors or Preflight Issues
For cross-origin implementation challenges:
Note any CORS preflight (OPTIONS) requests
Check response headers for CORS permissions
Understand allowed origins and methods
Security Considerations
When working with API calls:
Never share authentication tokens publicly
Mask sensitive data in screenshots or shared requests
Be aware of data access implications when replicating calls
Remember that all actions through the API are tracked in audit logs
A comprehensive guide detailing the process of launching Tallyfy workflows through REST API including authentication requirements payload structures and task assignment behaviors with proper error handling mechanisms.
The Tallyfy REST API enables secure workflow integration through user-based or application authentication methods requiring specific headers organization context management and proper token handling for successful API requests.
The REST API enables programmatic completion of Tallyfy task form fields through structured requests with field-specific payload formats and authentication headers for both updating fields and marking tasks as complete.
The Tallyfy REST API enables programmatic access to platform functionality through user-based or application authentication with features for process management task operations user administration template management data access and file operations.
