Documentation

Build your integration with confidence.

Start with an SDK example, keep your credentials server-side, and verify the API contract against your Outhly backend.

Quick start

Server-side user registration examples

JavaScript / TypeScript

TypeScript

import { Outhly } from "@outhly/sdk";

const auth = new Outhly({
  applicationId: process.env.OUTHLY_APPLICATION_ID!,
  secretKey: process.env.OUTHLY_SECRET_KEY!,
});

const user = await auth.users.create({
  email: "user@example.com",
  password: "a-strong-password",
});

Go

auth, err := outhly.New(outhly.Config{
  ApplicationID: os.Getenv("OUTHLY_APPLICATION_ID"),
  SecretKey: os.Getenv("OUTHLY_SECRET_KEY"),
})
if err != nil {
  log.Fatal(err)
}

user, err := auth.Users.Create(ctx, outhly.CreateUserInput{
  Email: "user@example.com",
  Password: "a-strong-password",
})

Python

import os
from outhly import Outhly

auth = Outhly(
    application_id=os.environ["OUTHLY_APPLICATION_ID"],
    secret_key=os.environ["OUTHLY_SECRET_KEY"],
)

user = auth.users.create(
    email="user@example.com",
    password="a-strong-password",
)

Before using in production

These are starter examples. Confirm the SDK package version, endpoint, headers, and request/response format against your deployed Outhly API. Never expose `OUTHLY_SECRET_KEY` to a browser or mobile client.

Common integration questions

Where should I use the secret key?+

Only in trusted server-side code or a secure backend environment. Do not expose it in client-side bundles or public environment variables.

Which languages are covered?+

The current starter SDK examples cover JavaScript/TypeScript, Go, and Python.

Are these examples production-certified?+

No. They illustrate the intended SDK shape. Validate them against the currently deployed API and add production security controls before launch.