Skip to main content
Request SDK access and understand your credentials

​
Overview

Sanas SDK uses secure credential-based authentication to protect access to SDK resources. Before you can use the SDK, you need to request access and receive your unique credentials.
What you’ll receive:
  • SDK Connector (native libraries and dependencies)
  • Endpoint URL (for Sanas Cloud connection)
  • Account ID (unique identifier)
  • Account Secret (secure password)

​
Request SDK Access

Fill out the access request form to get started:

Request SDK Access

What to expect:
  1. Fill out the form with your use case details
  2. Our team will review your request (typically within 1-2 business days)
  3. Receive SDK connector and credentials via email
  4. Start building!
Fill out the request form →

​
Information Needed

When requesting access, be prepared to provide:
  • Company name and use case description
  • Expected usage volume (concurrent streams, daily minutes)
  • Deployment preference (Sanas Cloud or self-hosted)
  • Technical contact information
  • Preferred region (if available)

​
Understanding Your Credentials

Once approved, you’ll receive the following via email:

​
1. SDK Connector

File: sanas_remote_sdk_<platform-arch>_<version>.tar.gz File includes:
  • Native Python libraries
  • Required dependencies

​
2. Endpoint URL

Example: sip.sanas.ai What it is:
  • Network address to connect to the Sanas Cloud
  • Region-specific endpoint for low latency
Self-hosted users: You’ll connect to your own infrastructure that hosts the AI models.

​
3. Account ID

What it is:
  • Unique identifier for your Sanas account
  • Used to authenticate SDK requests.

​
4. Account Secret

What it is:
  • Secure password for SDK authentication
  • Sensitive credential (keep confidential)
  • Used to verify your identity
Security Warning:
  • Never commit the Account Secret to version control
  • Never share in public forums or documentation
  • Rotate immediately if compromised
  • Use environment variables in production

​
Complete Authentication Example

Here’s how to use your credentials to initialize the SDK: 
import sanas_remote_sdk
import os

# Create SDK instance
sdk = sanas_remote_sdk.CreateRemoteSDK()

# Configure initialization parameters
init_params = sanas_remote_sdk.InitParams()

# Set credentials (use environment variables in production)
init_params.remoteEndpoint = os.getenv("SANAS_ENDPOINT", "your_endpoint_url")
init_params.accountId = os.getenv("SANAS_ACCOUNT_ID", "your_account_id")
init_params.accountSecret = os.getenv("SANAS_ACCOUNT_SECRET", "your_account_secret")

# Enable secure media transmission
init_params.secureMedia = True

# Initialize connection
result = sdk.Initialize(init_params)

if result == sanas_remote_sdk.InitResult.SUCCESS:
    print("SDK initialized successfully")
else:
    print(f"Initialization failed: {result}")

​
Self-Hosted Authentication

If you’re deploying Sanas SDK on your own infrastructure:
Self-hosted differences:
  • Setup requires consultation with the Sanas support team
  • No external endpoint exposure.
To get started with self-hosting:

Contact Support for Self-Hosting

Self-hosted deployment requires:
  • Infrastructure requirements assessment
  • Custom deployment package
  • Architecture guidance
  • Setup assistance
Reach out to our team →

​
Next Steps

Received credentials? Great! You’re ready to install the SDK.

Quickstart Guide


Instructions for installing libraries and dependencies to run your first audio stream.

​
Support

Need help with authentication or credentials?

Email Support

support@sanas.aiResponse time: 1 business day

Support Portal

Raise a support ticketFor urgent issues