GET STARTED

Make your first API request

A familiar interface and a clear path to integration.

Before you start: you need an account, a valid API key and available account credits. Online top-ups are not available yet.

01 · Create an account and key

Sign up or sign in, then create an application key in API Keys. Use a separate key for each app, with an expiry, quota and model restrictions.

Create account Manage API keys

02 · Store your key on the server

Store your key in APILUMA_API_KEY and send it in the Authorization: Bearer header. Keep it out of browser code, URLs and public repositories.

export APILUMA_API_KEY='YOUR_API_KEY'

To rotate a key, create a new key, update your application, then disable the old key.

03 · Choose a model and send a request

Choose a model from the current public catalog. The Python example uses the OpenAI SDK; install it with pip install openai.

Request model

POST /v1/chat/completions

Keep your key in an environment variable

Examples copy code; this page does not collect keys or send paid requests.

Endpoints

GET/v1/models

List models available to your key

POST/v1/chat/completions

Text chat; streaming is verified per model

Use https://api.apiluma.com/v1 as the base URL. SDKs normally append /chat/completions; do not add /v1 twice.

04 · Review credits and usage

Account credits and key quotas are separate limits. Creating a key does not add account credits. Online top-ups are not available; the administrator assigns credits. Existing redemption codes can be used in the credits area.

The public catalog shows reference prices for the selected group. Actual usage depends on your account group and request records. Refresh logs after a request; processing can delay reporting.

View credits View request logs

Troubleshooting

401Check that the key is valid, complete and not expired.

403Check key permissions, model restrictions and account group.

429Rate or quota limits may apply. Read the error message before retrying with backoff.

5xxAn upstream or gateway error occurred. Keep the request ID and avoid rapid retries.

Data & privacy

Request content is forwarded to the selected model’s upstream service and is subject to that service’s handling practices. The platform retains account, credit and request records for authentication, metering and troubleshooting. A fixed retention period has not yet been published.

When you sign in with Google, we receive your Google account identifier, name and email to create or identify your account, sign you in and support account linking. We request only openid, profile and email, with no access to Gmail, Drive or contacts. You can revoke access in your Google account. To request deletion of your Apiluma account or ask about data handling, contact [email protected].

Only submit data you are authorized to share, and protect your keys. Public pages do not collect API keys or run live inference demos. This release does not promise zero retention or continuous availability.