API Call Consumption and Document Generation in Titan
Overview
Titan interacts with Salesforce to retrieve, create, and update data in real time. These interactions are measured using two separate consumption models:
API Calls for data operations between Titan and Salesforce
Document Generation (Doc Gen) for creating and processing documents
Understanding how each is consumed is essential for designing efficient workflows and estimating usage.
API Calls
What Is an API Call?
An API call is any interaction where Titan connects to Salesforce to retrieve or send data.
Each connection to Salesforce consumes 1 API call, regardless of the amount of data processed within that request.
How API Calls Are Counted
Action
API Calls Consumed
Retrieve data from a Salesforce object
1 API call
Create a record in Salesforce
1 API call
Update a record (single or multiple fields)
1 API call
Validate data against Salesforce before submission
1 API call
Key Behavior
API calls are counted in real time
Updating multiple fields on the same record counts as 1 API call
Each separate interaction with Salesforce counts independently
API usage depends on project configuration and logic design
Example
A form includes:
A validation step to check if an email exists
A submission step to create a new record
Consumption:
1 API call for validation
1 API call for record creation
Total: 2 API calls
Bulk API
Overview
Bulk API allows multiple records to be processed in batches within a single API request.
How It Works
Records are grouped into batches
Each batch counts as 1 API call
The default batch size is 200 records
Example
Records Processed
Batch Size
API Calls
500 records
200
3 API calls
200 records
50
4 API calls
Notes
Batch size can be configured
Changing batch size directly impacts API consumption
Bulk API follows Salesforce-specific processing rules
Data Retrieval (GET Operations)
Overview
Retrieving data from Salesforce consumes API calls.
Behavior
Each object retrieval consumes 1 API call
Large datasets retrieved in a single request still count as 1 API call
Example
Retrieving all accounts from a filtered query:
1 API call, regardless of the number of records returned
Document Generation (Doc Gen)
Overview
Document generation is measured separately from API calls.
Each time a document is created, previewed, or processed, Doc Gen usage is consumed.
Consumption
Action
Doc Gen Consumption
Preview document
1 Doc Gen
Generate document
1 Doc Gen
Convert to PDF
1 Doc Gen
Merge multiple files
1 Doc Gen
Edit document
1 Doc Gen
Interactive document
1 Doc Gen
Key Behavior
Previewing a document counts as usage because the document is generated in real time
Preview + final generation results in 2 Doc Gens consumed
Doc Gen usage is independent of API calls unless combined with additional actions
Post-Generation Actions
Overview
Actions performed after document generation may consume API calls.
Consumption
Action
Consumption
Push document to Salesforce
1 API call
Send email via Salesforce
1 API call
Send email via Titan or external server
0 API calls
Titan Sign Consumption
Overview
Document signing introduces both Doc Gen and API call usage.
Consumption Rules
Action
Consumption
Start the signing process
1 Doc Gen
Each signer
1 Doc Gen per signer
Track signing activity
1 API call per interaction
Generate signing log PDF
1 Doc Gen
Notes
Viewing a document without signing does not consume Doc Gen
Each signer increases total Doc Gen usage
Tracking updates consumes API calls due to Salesforce interaction
Feature-Based API Consumption
Overview
Certain advanced features consume additional API calls due to processing complexity.
Consumption
Feature
API Calls
SmartV login
1 API call
SmartV with 2FA
2 API calls
Virus scan
10 API calls
Barcode scanning
40 API calls
Sentiment recognition
10 API calls
Video recognition
10 API calls
OCR (Optical Character Recognition)
20 API calls
Address validation
20 API calls
Notes
These features involve external processing or advanced validation
API consumption occurs when results are verified or synced with Salesforce
Email Handling
Overview
Email behavior impacts API consumption depending on how the email is sent.
Consumption
Method
API Calls
Send email via Salesforce
1 API call
Send email via Titan or external server
0 API calls
Key Behavior
API calls are only consumed when Salesforce is involved
Direct sending methods bypass Salesforce and do not consume API calls
Monitoring API Usage
Live Trace
Live Trace allows real-time tracking of API usage in production.
Use Cases
Identify which actions consume API calls
Analyze user behavior in web portals
Debug workflows and integrations
API Estimation and Scaling
Estimation
API consumption depends on:
Number of users
Workflow complexity
Validation logic
Data interactions
Unmetered Option
The unmetered option allows continued operation beyond allocated limits.
Behavior
Usage is tracked beyond quota
Additional consumption is billed based on actual usage
Prevents workflow interruption due to limits
Key Takeaways
API calls measure data interactions with Salesforce
Doc Gen measures document-related actions
Multiple operations can be optimized into a single API call
Workflow design directly impacts total consumption
Monitoring tools help track and optimize usage in real time
