Session 9: Transmission & API Settings and IS Roadmap Webinar Replay

Oct 8th, 2026

We’re excited to launch the Dayforce Integration Studio Builder Series — a collaborative initiative designed to bring together internal teams and partners to better leverage the full potential of the Dayforce platform.

What this series is about

This series focuses on showcasing real-world capabilities through practical, hands-on examples. Our goal is to help teams:

• Build with confidence using proven patterns
• Drive reuse and scale through shared solutions

• Strengthen the developer community through collaboration and knowledge sharing

Through weekly sessions, deep dives, and interactive discussions, participants will gain actionable insights into how to apply these tools in real implementations—and contribute back to a growing ecosystem of shared expertise.

What we covered in Session 9

Thank you to everyone who joined our latest Integration Studio Builder Series session!

In this session, we focused on Transmission Settings in Integration Studio, exploring how to configure and manage API-based transmissions once data has been retrieved and transformed.

Our Integration Studio experts covered:

• Configuring batch transmissions, including sending one record per API call and managing batch size.
• Using dynamic URI tokens, headers, and integration parameters when transmitting data to external systems.
• Working with different API methods, including POST, PUT, and PATCH, based on the destination system’s requirements.
• Preventing unnecessary transmissions when no data is returned or records have been filtered out.
• Using Batch Logs to review individual API calls, troubleshoot failures, and rerun only failed batches rather than retransmitting the entire dataset.
• Understanding authentication options, including Basic Authentication and OAuth, along with client credentials, tokens, and scopes.
• Important considerations when using third-party webhook/testing tools, particularly around protecting sensitive data.

We also shared a sneak peek at what’s ahead for Integration Studio, including improved log search, bulk editing, expanded JSON Web Token support, HR Events 2.0 support, and conditional POST/PATCH capabilities during transmission.

Key takeaway: Transmission is more than simply sending the final payload. Understanding batching, authentication, API requirements, logging, and error recovery helps create integrations that are easier to operate and troubleshoot.

Have an Integration Studio idea or a challenge you’d like us to know about? Share it in the Dayforce Developer Community — your feedback helps inform future capabilities and priorities.

Follow-Up & Topics We’ll Address

Based on your questions, we’ll continue to incorporate:

• Real-world use cases and scenarios
• Integration patterns and best practices

• End-to-end examples showing how components connect.