Reference

Images

Every image URL returned by the API is a sealed, encrypted token served through the Deeline image proxy. You cannot decode it, and it never reveals where the image actually lives. Just prepend your base origin and use it like any other URL.

How it works

The API response gives you /api/img?t=<token>.
The token is a sealed reference — issued server-side. It is opaque to clients.
When you (or the browser) requests it, Deeline serves the image through its proxy and returns the result to you.
Your end-user only ever sees deeline.com.ng in the URL.

Example

Response from GET /api/v1/products:

{
  "image": "/api/img?t=XXXXX…",
  "images": [
    "/api/img?t=YYYYY…",
    "/api/img?t=ZZZZZ…"
  ]
}

To display it on your site, prepend your base origin:

// Browser / JSX
<img src={"https://deeline.com.ng" + product.image} alt={product.name} />

// Or when rendering a list
{product.images.map((src) => (
  <img key={src} src={"https://deeline.com.ng" + src} alt="" loading="lazy" />
))}

Python

import requests

# Read the JSON, then download the image
data = requests.get(
    "https://deeline.com.ng/api/v1/products?page=1&pageSize=1",
    headers={"Authorization": "Bearer dl_live_YOUR_KEY"},
    timeout=30,
).json()

product = data["products"][0]
image_path = product["image"]           # e.g. /api/img?t=…
image_url = "https://deeline.com.ng" + image_path

image_bytes = requests.get(image_url, timeout=30).content
with open("product.jpg", "wb") as f:
    f.write(image_bytes)

Why the token is sealed

Security. The token is not a simple encoding — you cannot reverse it, decode it, or extract the underlying source from it.
Stability. The image source is never exposed to clients, regardless of what appears in the URL.
Revocability. Tokens are issued server-side; if the underlying source changes, tokens are reissued without breaking your integration.
Cache-friendly. The same image always returns the same URL, so standard CDN caching works.

Caching

Image responses are cached for 24 hours. You can cache them yourself — the tokens are deterministic, so the same URL always returns the same image.

Rate limits

The image proxy is on its own rate path and does not count against your API key quota. If you serve many images, cache them at your edge / CDN.

What not to do

Do not attempt to decode the token. It is opaque — treated as a URL, nothing more.
Do not strip /api/img. The path is part of the proxy contract — the origin path is not directly reachable.
Do not cache the underlying image outside the proxy. Use the proxy URL as your cache key.