Get started with TrustWeaver
Set up your integration with Sovos TrustWeaver, including authentication, endpoint configuration, and connection verification.
TrustWeaver exposes its services through Simple Object Access Protocol (SOAP) 1.1 over HTTPS. Your application communicates with TrustWeaver using standard Web Services tooling, so you don't need a proprietary SDK. Familiarity with public key cryptography, SSL/TLS, XML, and SOAP is expected before you begin.
TrustWeaver Compliant e-Invoicing is divided into technical services:
- Signing service
- Handles digital signature creation and validation.
- Storage service
-
Handles invoice storage, retrieval, and processing operations including corroboration, format transformation, tax identifier validation, and download token generation. Paired with the Admin Service, which manages storage sections.
Note:
The Storage Service
StorageServicePortuses SOAP MTOM (Message Transmission Optimization Mechanism) for efficient transmission of binary document data. If your Web Services stack doesn't support MTOM, useStorageServiceLegacyPortinstead. All other service ports (Admin Service, Notification Service, Signing Service) use text encoding without MTOM. - Admin Service
- Paired with the Storage Service. Manages storage sections, cryptographic keys, and branches. All Admin Service operations are configuration prerequisites for Storage Service operations.
- Notification Service
- Provides operations for getting notifications and events andquerying events that occur asynchronously, such as invoice receipt events.
Prerequisites
Before you begin, confirm the following:
-
You have a valid client certificate and its corresponding private key, which Sovosissued for your environment (UAT or production).
-
Your application can establish an SSL/TLS connection to the TrustWeaver host.
-
Your development platform supports a Web Services stack capable of generating client stubs from a WSDL. Most modern platforms include this capability.
-
TrustWeaver uses wrapped parameter style. All input and output messages are wrapped in an element: the input wrapper has the same name as the operation, and the output wrapper has the same name with the suffix
Responseappended. For example,StoreInvoiceusesStoreInvoiceas the input wrapper andStoreInvoiceResponseas the output wrapper.Tip:Don't construct HTTP requests and SOAP envelopes manually. Use the WSDL to generate client stubs through your Web Services stack instead.
Environments
TrustWeaver provides separate environments for testing and production. Certificates issued for one environment can't be used in the other.
| Environment | Description |
|---|---|
| UAT | Used for integration testing and development. Request a UAT certificate before connecting. |
| DEV | Used for early-stage development and pre‑production validation. Request a DEV certificate before starting your tests. |
| Production | Used for live document processing. Requires a separate production certificate issued by Sovos. |
