Connecting partner services to AeThex
AeThex Integrations wrap third-party analytics, identity, payments, and live-ops tooling behind a consistent runtime, security model, and visual system. Use this guide to register new connectors, surface partner UI in product flows, and automate data exchange without hand-rolled plumbing.
Game Engines
Integrate AeThex into your game engine of choice with native SDKs and code examples.
Godot Engine
GameMaker
Powerful 2D engine with GML scripting for rapid game development
Distribution Platforms
Publish your games on indie storefronts with AeThex backend integration for cloud saves and cross-platform features.
GameJolt
Community gaming platform with 10M+ players and trophy sync
Itch.io
Indie marketplace with 500K+ games and flexible pay-what-you-want pricing
Social VR & Metaverse Platforms
Deploy your games and apps across social VR and metaverse platforms using AeThex's unified API.
VRChat
Build immersive VR worlds with Udon scripting and cross-platform authentication
RecRoom
Create social games using Circuits visual scripting for VR and mobile
Spatial
Build browser-based 3D experiences for VR, desktop, and mobile devices
Decentraland
The Sandbox
Runtime flow
Integration manifests are stored in the AeThex Integrations service and synced across the dashboard and runtime. Client components resolve connector metadata through the shared API helpers, ensuring credentials and capability flags stay consistent with server state.
During hydration the runtime mounts partner SDKs behind AeThex loaders, applying sandboxed execution where required. Use lifecycle hooks to emit analytics, hydrate widgets with scoped credentials, and gate access through the same role-based policies used elsewhere in the platform.
Theming hook
Use the integration theming utilities to adapt partner widgets to AeThex gradients, typography, and focus states. Tokens flow through CSS variables defined in global.css, so embeds stay visually aligned with dashboards and consumer apps.
Extend styling with scoped class names or CSS variables exported by the partner SDK. When shipping multiple widgets, prefer design tokens over hard-coded overrides to keep dark-mode and accessibility tweaks in sync.
Configuration options
| Property | Purpose | Default |
|---|---|---|
| key | Unique identifier referenced across dashboards, APIs, and audit logs. | "analytics-segment" |
| category | Integration taxonomy aligned with AeThex surfaces (analytics, identity, commerce, ops). | "analytics" |
| capabilities | Feature flags that unlock widgets, automation hooks, and data pipelines. | ['metrics', 'webhooks'] |
| connectionMode | Determines how credentials are managed (oauth, apiKey, managedVault). | "oauth" |
| webhookEndpoint | Optional callback URL for outbound events delivered by AeThex. | "https://app.example.com/aethex/webhooks" |
| uiEmbeds | Declarative config describing dashboard cards, modals, or launchers this integration renders. | [{ surface: 'dashboard', placement: 'sidebar' }] |
Best practices
- Store credentials in AeThex-managed vaults and rotate them from the dashboard rather than hard-coding.
- Limit embed rendering to audiences that have access to the underlying data to avoid leaking partner UI.
- Log integration events through the shared telemetry helpers so support can trace partner-side failures.
Lifecycle management
Promote integration changes through staging first. AeThex snapshots connector manifests per environment so you can test credentials, capability flags, and UI placements without impacting production users.
When partners publish SDK updates, pin versions in your manifest, document the change log, and coordinate rollout windows with stakeholders subscribing to the integration.
Troubleshooting
OAuth handshake fails
Confirm the integration's redirect URI matches the value registered in the partner console. AeThex surfaces expose the required callback under Settings → Integrations.
Webhook retries exhausted
Inspect delivery attempts in the Integrations dashboard. Update retry policies or verify your endpoint responds with a 2xx status within 10 seconds.
Embedded widget styling
Override component tokens through the integration theme utilities or wrap the widget in a container that inherits AeThex gradient variables.
Further reading
Manage integration documentation centrally in Builder CMS or export static guides for partner teams. Keep manifests, onboarding playbooks, and support runbooks together so each connector has a clear owner.