API
This documentation provides detailed information about the Vanadum API, including endpoints, parameters, and usage examples to help you integrate Vanadum's powerful TLS capabilities into your applications.
Endpoint
All requests to the Vanadum API are directed to this single, versatile endpoint.
Supported Features
TLS
- Transport Layer Security fingerprinting bypassJA3
- JA3 fingerprint spoofing and evasionJA4
- JA4 fingerprint customizationHTTP2
- HTTP/2 protocol fingerprint management
Headers
The Vanadum API uses custom headers to control request behavior. Configure these headers to customize how your requests are processed.
Response Handling
When you make a request to the Vanadum API, the response is a straight pass-through of the target server's response, including status code, headers, and body content.
Error Responses
If an error occurs during the request processing, Vanadum returns a JSON error object:
Common error scenarios include:
- Invalid URL format
- Connection timeout
- Proxy connection failure
- TLS handshake errors
Implementation Guide
Follow these steps to implement Vanadum in your application:
Start the Vanadum Service
Ensure the Vanadum service is running on your local machine at http://localhost:8000/
.
Create Your Request
Prepare an HTTP request to the Vanadum endpoint with appropriate headers.
Process the Response
Handle the response from Vanadum, which will be the response from the target URL or an error object.
Advanced Usage Examples
Real-World Use Cases
Vanadum is particularly useful for applications that need to make requests to websites with sophisticated bot detection systems, as well as for testing website behavior with different browser fingerprints.
Performance Considerations
- Local Processing: Since Vanadum runs locally, network latency is minimized between your application and the Vanadum service.
- Connection Pooling: Vanadum implements connection pooling for improved performance when making multiple requests to the same host.
- Compression: Use of modern compression algorithms can significantly reduce bandwidth usage and improve response times.
When making high-volume requests, monitor your system resources, especially when using many threads or proxies simultaneously.