Inkfluence AI Full Tutorial

When you call Inkfluence AI, every request must carry proof that you own the account that created it. This chapter covers how to create API keys, attach them to requests, and keep them safe across environments.

Overview

This section explains Inkfluence AI authentication using API keys (a secret token used to authorize API requests). Use it when building server-to-server calls, browser apps with a backend proxy, or automated workflows that generate or transform content.

Quick Reference

Header format

• `Authorization: Bearer `
• `Content-Type: application/json`

Parameters

Authentication parameters (applies to all endpoints):

Code Example

# 1) Create an API key (run once, then store the secret)
curl -sS -X POST "https://api.inkfluence.ai/v1/api-keys" \
  -H "Authorization: Bearer $INKFLUENCE_ADMIN_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "prod-server",
    "scopes": ["content:generate", "content:analyze"]
  }'

// 2) Use the key for authenticated requests (Node.js example)
import fetch from "node-fetch";

const INKFLUENCE_API_KEY = process.env.INKFLUENCE_API_KEY; // set in server env vars

async function generateText() {
  const res = await fetch("https://api.inkfluence.ai/v1/generate", {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${INKFLUENCE_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      model: "inkfluence-text-v1",
      prompt: "Summarize the key points for a client-ready brief.",
      temperature: 0.3,
      max_tokens: 300,
    }),
  });

  // Handle non-2xx responses with body capture
  const data = await res.json().catch(() => ({}));
  if (!res.ok) {
    throw new Error(`Inkfluence API error (${res.status}): ${JSON.stringify(data)}`);
  }
  return data;
}

generateText().then(console.log).catch(console.error);

Response Format

{
  "id": "req_123456789",
  "created_at": "2026-06-24T12:34:56Z",
  "status": "success",
  "data": {
    "api_key": "inkf_live_••••••••••••", 
    "api_key_id": "key_abc123",
    "name": "prod-server",
    "scopes": ["content:generate", "content:analyze"],
    "expires_at": null
  }
}

Field descriptions

• `id`: Request identifier for tracing.
• `created_at`: Server timestamp.
• `status`: High-level status string.
• `data.api_key`: The secret key value (capture and store immediately).
• `data.api_key_id`: Key identifier for revoke/list.
• `data.scopes`: Granted permissions.
• `data.expires_at`: Expiration time if configured.

Notes & Best Practices

• Key handling (“Key Vault Checklist”): store the raw `api_key` only in server-side secrets (environment variables or a managed secret store); never commit to git or embed in frontend code.
• Rotation: revoke old keys using `POST /v1/api-keys/{api_key_id}/revoke` before replacing them in production to avoid mixed credentials.
• Error handling: treat `401/403` as authentication/authorization issues; log `request id` (`id` field) for support-grade debugging.
• Rate limits: if you receive `429`, back off and retry with jitter; avoid tight retry loops that can increase throttling.

Authentication with API keys is the gate that everything else depends on; once the `Authorization: Bearer ...` header is stable, the rest of your Inkfluence AI calls become deterministic request/response engineering.