WIRESYNDICATEDocumentation

Network Initialization

Before your application can request programmatic bids or render spatial assets, you must initialize the WireSyndicate Core Engine and authenticate your client with the Edge Delivery Node.

Authentication Architecture

Authentication requires your Publisher Network Key. This cryptographically binds the telemetry emitted by the client to your publisher account, ensuring you are compensated for all validated impressions.

The 5-Step Deployment Pipeline

  1. Package Ingestion: Open your Unity Editor. Navigate to Window > Package Manager. Click the + icon, select Add package from git URL, and input our public repository URL (https://github.com/WireSyndicate/wiresyndicate-unity-sdk.git).
  2. Key Retrieval: Log into your Developer Dashboard on the WireSyndicate Web Portal. Copy your Organization ID or the specific Game Network Key.
  3. Scene Preparation: Open your initial loading scene. In the Unity Hierarchy, create an Empty GameObject and rename it to [WireSyndicate_Core].
  4. Component Implementation: In the Unity Inspector, click Add Component, search for WireSyndicateInitializer, and add it to the GameObject. Due to its [DisallowMultipleComponent] architecture, you can only attach one instance per GameObject.
  5. Inspector Binding: In the Unity Inspector, configure the exposed fields on the WireSyndicateInitializer:
    • Network Key: This is your Developer API Key. It cryptographically binds telemetry to your publisher account.
    • Game Id: The unique identifier for your game on the platform, used for telemetry tracking.
    • API Base URL: Tells the SDK where to connect. By default, it points to https://api.wiresyndicate.com for production. If running a local test server, update this to your local host address.

Architecture Note: The WireSyndicateInitializer is a strict DontDestroyOnLoad Singleton. It features built-in auto-bootstrapping, meaning it will automatically handle internal dependencies like the Gaze Verification Engine.

Warning: You must insert a valid Network Key or Organization ID into the Inspector slot. If this key is missing, invalid, or your account is suspended, the SDK will gracefully reject the Zero-Trust Handshake (403/404) and halt Edge telemetry.