The Protocol for
Verified Communication
TrustSignal provides an open-standard protocol for verifying communication integrity. Integrate our API into your telco stack, PBX, or application in minutes.
Documentation
SDKs & Tools
Getting Started
The TrustSignal API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
Base URL
https://api.trustsignal.io/v1Authentication
Bearer Token (JWT)Session Management
To start verifying calls, you first need to initiate a session. This generates a cryptographic signal that we use to track and verify the integrity of the communication channel.
curl -X POST https://api.trustsignal.io/v1/sessions \
-H "Authorization: Bearer ${YOUR_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"caller_id": "+233201234567",
"recipient": "+233559876543",
"protocol": "veriwave-v1",
"metadata": {
"purpose": "security_verification"
}
}'The Veriwave Standard
Asymmetric Verification
Our protocol uses dual-channel verification. We combine in-band audio watermarking with out-of-band cryptographic validation.
- AES-256 Content Encryption
- Millisecond Latency Sync
Trusted Infrastructure
Every node in the TrustSignal network is verified. We maintain a decentralized registry of authorized issuers and gateways.
- Mutual TLS Auth (mTLS)
- Signed JWT Endpoints
Core Endpoints
| Endpoint | Method | Description |
|---|---|---|
| /sessions | POST | Create a new trusted session |
| /sessions/:id | GET | Retrieve session status |
| /verify/:token | POST | Validate a protocol token |
| /metrics | GET | Access real-time protocol health |
Need a custom implementation?
Our engineering team is ready to help you with complex SIP/RTP integrations.