Welcome to the Bet Softnets developer documentation. Our platform provides comprehensive APIs, SDKs, and tools for integrating software development, network solutions, and healthcare technology into your applications. Whether you're building custom software, managing network infrastructure, or developing HIPAA-compliant healthcare applications, our documentation will guide you through every step.

Get started with Bet Softnets in 5 minutes. Follow these steps to make your first API call.

BS-LIVE-abc123def456ghi789jkl

composer require betsoftnets/sdk

pip install betsoftnets

npm install @betsoftnets/sdk

<dependency>
    <groupId>com.betsoftnets</groupId>
    <artifactId>sdk</artifactId>
    <version>2.1.0</version>
</dependency>

<?php
require 'vendor/autoload.php';

use BetSoftnets\Client;

$client = new Client([
    'api_key' => 'your-api-key-here',
    'environment' => 'sandbox' // Use 'production' for live
]);

// Test the connection
try {
    $response = $client->health->ping();
    echo "Connected successfully!";
} catch (Exception $e) {
    echo "Error: " . $e->getMessage();
}

All API requests require authentication using your API key. We support multiple authentication methods.

API Key Authentication

Include your API key in the request header:

Authorization: Bearer BS-LIVE-abc123def456ghi789jkl

Environment Types

API requests are subject to rate limiting to ensure fair usage and system stability.

Rate limit information is included in response headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1615305600

The API uses conventional HTTP response codes to indicate success or failure.

Error Response Format

{
  "success": false,
  "error": {
    "code": "invalid_parameters",
    "message": "The request parameters are invalid",
    "details": [
      {
        "field": "email",
        "issue": "must be a valid email address"
      }
    ]
  },
  "request_id": "req_xyz789"
}

Receive real-time notifications about events in your account.

Supported Events

• project.created - New project created
• project.updated - Project details updated
• deployment.completed - Deployment finished
• monitoring.alert - Network monitoring alert
• patient.updated - Patient record updated

Webhook Payload Example

{
  "event": "deployment.completed",
  "timestamp": "2026-03-09T15:30:00Z",
  "data": {
    "project_id": "proj_123456",
    "deployment_id": "dep_789012",
    "status": "success",
    "environment": "production",
    "url": "https://app.example.com"
  },
  "signature": "sha256=..."
}

Verifying Webhook Signatures

All webhooks include a signature header that you should verify to ensure the request is from Bet Softnets.

// PHP Example
$signature = $_SERVER['HTTP_X_BETSOFTNETS_SIGNATURE'];
$payload = file_get_contents('php://input');
$secret = 'your-webhook-secret';

$expected = hash_hmac('sha256', $payload, $secret);

if (hash_equals($expected, $signature)) {
    // Valid webhook
    processWebhook($payload);
} else {
    // Invalid signature
    http_response_code(401);
}