AuraOne / Developers
Loading the developer hub.
Preparing SDKs, integrations, code examples, infrastructure guidance, and documentation.
AuraOne / Developers
Preparing SDKs, integrations, code examples, infrastructure guidance, and documentation.
AuraOne / Developers / Integrations
Use available connectors and signed webhooks for release automation, archives, incidents, team channels, and observability.
Each catalog entry states its current availability. Customer-specific authentication, network, permissions, and provider enablement are confirmed during implementation.
At a glance
Operating trace
Native connectors and raw webhooks use the same operating trace.
01
02
03
04
Connector catalog
Select a connector to inspect its readiness, requirements, and quickstart.
Gate releases with evaluation results before code or model changes ship.
await client.integrations.github.dispatchWorkflow({ owner: 'aura', repo: 'evals', workflowId: 'ci.yml', ref: 'main' });Raw webhook
The handler rejects an unverified payload, then routes the event only after origin and message integrity are established.
import { createHmac, timingSafeEqual } from "crypto";
app.post("/webhooks/auraone", (req, res) => {
const signature = req.headers["x-auraone-signature"];
const expected = createHmac("sha256", process.env.AURAONE_WEBHOOK_SECRET!)
.update(JSON.stringify(req.body))
.digest("hex");
if (!signature || !timingSafeEqual(
Buffer.from(signature),
Buffer.from(expected)
)) return res.status(401).end();
routeVerifiedEvent(req.body);
res.status(200).json({ received: true });
});import { createHmac, timingSafeEqual } from "crypto";
app.post("/webhooks/auraone", (req, res) => {
const signature = req.headers["x-auraone-signature"];
const expected = createHmac("sha256", process.env.AURAONE_WEBHOOK_SECRET!)
.update(JSON.stringify(req.body))
.digest("hex");
if (!signature || !timingSafeEqual(
Buffer.from(signature),
Buffer.from(expected)
)) return res.status(401).end();
routeVerifiedEvent(req.body);
res.status(200).json({ received: true });
});Keep configuration, delivery, retries, failures, and downstream handling connected.
01
Name the events and payload fields the destination requires.
Subscription scope
02
Confirm credentials, permissions, network, and owner.
Connector configuration
03
Exercise signatures, retries, duplicate handling, and failure alerts.
Integration test receipt
04
Record retention, support, rollback, and the next review date.
Operating handoff