Skip to main content
Community Admin
jcooleyCommunity Admin
Community Admin
Jan 30, 2026 2:00 PM UTC

Tech Talks After Hours: REST and SOAP API

API: REST or SOAP?  Extending the Data Integration series, SMEs David Stroud and Andrew Talecki join Tom Linton as they discuss the differences, prerequisites, authentication types, and optimization techniques while utilizing SOAP or REST API calls.

Key Topics Covered

  • Four categories of OneStream connections: file-based integrations, external integrations, database integrations, and API integrations — this session focuses on the API category
  • REST vs. SOAP API: an introduction to both protocols, their differences, and the scenarios in which each is used for connecting OneStream to external systems
  • Prerequisites for each API type: what needs to be in place before building a REST or SOAP integration, including endpoint access, credentials, and documentation from the source system
  • Token-based authentication: how REST APIs typically require calling an authentication endpoint first to obtain a randomly generated token, which is then used to call the target endpoint — no credentials are passed directly
  • Token security and revocation: tokens act as a secure go-between so credentials are never exposed; tokens can be revoked at any time to immediately cut off access
  • Variation in token generation: some systems require a separate call to obtain a token while others embed the token generation logic inside the request body — the approach depends on what the endpoint provider requires
  • Industry-specific authentication considerations: organizations in highly audited industries (government contractors, finance) may require stronger authentication protocols, and the implementation must match the security posture of the endpoint
  • Volume and partitioning considerations: how to think about data volume and partitioning strategy when designing an API integration, particularly for large datasets returned across multiple API calls
  • Response format differences: REST and SOAP return data in different formats (JSON/XML), and the integration must be designed to parse and map the response correctly into OneStream
  • Working with a customer's ERP system: the integration developer must collaborate with the customer's technical team to understand the specific authentication and endpoint requirements of their source system
  • Smart Integration Connector (SIC): a VPN-like capability that creates a secure tunnel from OneStream into a customer's private network, enabling connections to internal APIs that are not publicly accessible from the internet
  • Breadth of REST connectivity: as Andrew and David note, if a REST API endpoint exists and the system can be accessed, OneStream can connect to it — the platform's API integration capabilities are broad and flexible

 

 

 

To receive OnePoints for watching this Tech Talk video, please visit the link below:
https://onestream.thoughtindustries.com/courses/tech-talks-after-hours-rest-and-soap-api?sessionFields=%5B%5B%22series%22%2C%22Tech%20Talks%22%5D%5D

    Terms & ConditionsAccessibility statement