Quickstart

Send your first API request.

Use one scoped API key, the public API base URL, and a supported model id. Keep the first request small so usage and credits are easy to verify.

Create API key API reference

Setup

Before you start

No server session is needed for the API call itself. The request uses a bearer key.

Base URL: https://api.1api.club/v1
Authorization: Authorization: Bearer $API_KEY
First endpoint: POST /v1/chat/completions
First verification: Open Usage and Credits after the request completes.

Minimum setup

Keep API keys in server-side environment variables. Do not ship them in browser bundles or mobile apps.

Steps

Keep the first integration path narrow.

If you need model ids first, open Models. If you need rates first, open Pricing.

01Create a keyOpen the console and create an API key for the workspace.
02Set the base URLPoint your SDK or HTTP client at the public API base URL.
03Send one small requestUse a public model id and a short prompt before real traffic.
04Check usageConfirm status, latency, tokens, and credits before scaling up.

curl

Start with a direct HTTP request.

This request uses the common Chat Completions shape many SDKs, agents, and workflow tools already know.

Chat Completions request

curl https://api.1api.club/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.5",
    "messages": [
      { "role": "user", "content": "Write a one sentence deployment note." }
    ]
  }'

SDK shape

Use the same SDK pattern with a different base URL.

OpenAI-compatible SDK clients usually need only apiKey and baseURL changed. Keep API keys in server-side environment variables.

Node.js SDK shape

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.API_KEY,
  baseURL: "https://api.1api.club/v1",
});

const response = await client.chat.completions.create({
  model: "gpt-5.5",
  messages: [
    { role: "user", content: "Write a one sentence deployment note." },
  ],
});

console.log(response.choices[0]?.message?.content);

Verify

Confirm the request shows up in usage.

A successful HTTP response is not the whole integration check. Verify usage and credits before sustained automation.

Open usage Open credits

Request record: Status, latency, model, and tokens.
Spend record: Credits Used and remaining credits.
Support context: Public trust context and support details.

Troubleshooting

Check the small things first.

Most first-run failures come from key, URL, model id, credits, or endpoint availability assumptions.

Base URL: Use the exact API base URL, not the public site URL.
Bearer key: Send the key in the Authorization bearer header.
Model id: Use a public model id from Models.
Credits: Check available credits before repeated requests.
Endpoint scope: Use documented endpoints; unavailable resource APIs return documented errors.
Secret handling: Keep API keys out of browser bundles and mobile apps.

Continue through the docs.

Use the overview for integration context or the reference for endpoint scope.

OverviewConnection facts, public scope, and the first verification path.Open QuickstartCreate a key, set the base URL, and send the first request.Current API referenceSupported endpoints, request shape, and unavailable resources.Open