This article is part of the Replicon Gen2 knowledge base. If you’re looking for information on Replicon Gen3, which is the latest version of Replicon, please visit:

This topic deals with using Replicon report web services from the legacy (Gen2) Replicon product.

If you’re looking for full API documentation for the legacy version of Replicon (Gen2), you’ll find the RepliConnect documentation here.

If you need API documentation for the latest version of Replicon (Gen3), go to


The Web TimeSheet Web Services uses SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) for its message format, and usually relies on other Application Layer protocols, most notably Remote Procedure Call (RPC) and Hypertext Transfer Protocol (HTTP), for message negotiation and transmission.

SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built. This XML based protocol consists of three parts: an envelope, which defines what is in the message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing procedure calls and responses.

The site would then return an XML-formatted document with the resulting data. Because the data is returned in a standardized machine-parseable format, it could then be integrated directly into a third-party web site or application.