Authentication

Every request to the Deeline API must include a Bearer key. Keys are issued from the admin panel — the plaintext is shown once and never again.

The Authorization header

Authorization: Bearer dl_live_YOUR_KEY

The header is required on every request. Missing or invalid keys return 401 Unauthorized.

Where to get a key

1. Contact Deeline support to request a reseller account.
2. We issue the key from the admin panel and share it once.
3. You store it server-side and never expose it to the browser.

Key format

All keys start with dl_live_. Treat the whole key as opaque — do not parse or slice it.

dl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Storing keys safely

• Environment variables — store the key in .env, never hardcode it.
• Server-side only — never send the key to the browser, mobile client, or public repo.
• One key per integration — so you can revoke one without affecting others.
• Rotate on compromise — if a key leaks, revoke it immediately from the admin panel.

Example: Node.js (server-side)

// .env
API_KEY=dl_live_xxxxxxxxxxx

// server.js
const API_KEY = process.env.API_KEY;

const res = await fetch("https://deeline.com.ng/api/v1/products", {
  headers: { Authorization: `Bearer ${API_KEY}` },
});

Example: Python (server-side)

import os, requests

API_KEY = os.environ["API_KEY"]

r = requests.get(
    "https://deeline.com.ng/api/v1/products",
    headers={"Authorization": f"Bearer {API_KEY}"},
    timeout=30,
)

Revoking a key

If a key is compromised, revoke it from the admin panel. Revocation is immediate — the next request returns 401.

Rate limiting

Every key is rate limited per minute and per hour. See Rate limits.