API Reference

Content Injection API

Generate optimized content blocks that can be injected into your pages.

Endpoints

Generate, preview, and fetch injection payloads.

POST /injection

Generate injection-ready content for a URL or HTML payload.

curl https://api.cleversearch.ai/v1/injection \
  -H "Authorization: Bearer YOUR_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "mode": "auto"}'

GET /injection/{id}

Retrieve injection content previously generated.

GET https://api.cleversearch.ai/v1/injection/inj_123

POST /injection/preview

Preview generated content without saving changes.

POST https://api.cleversearch.ai/v1/injection/preview

Preview Request Example

Use preview mode to inspect generated content before deployment.

{
  "url": "https://example.com/pricing",
  "mode": "manual",
  "content_types": ["faq", "supporting_paragraphs"],
  "brand_voice": "clear, technical, direct"
}

Supported Content Types

Select which blocks to generate for your site.

●title

●meta_description

●faq

●headings

●supporting_paragraphs

Injection Safety Controls

Protect UX quality with strict placement and approval rules.

●Whitelist containers and prevent conflicting DOM updates.

●Use preview mode for high-traffic templates.

●Track rollback capability for every deployment.

●Run quality checks for tone, claims, and formatting.

Execution Phases

Phase 1: Integration

Implement auth, request validation, and core endpoint flow.

Output: Stable API client with retries and typed payloads.

Phase 2: Automation

Add async handling and webhook-driven workflows.

Output: Background jobs connected to reliable event processing.

Phase 3: Hardening

Improve observability, rate-limit handling, and security.

Output: Production-ready monitoring and incident runbooks.

Common Mistakes

●Calling endpoints from client-side code with secret credentials.

●Ignoring 202/async patterns and assuming immediate completion.

●Missing idempotency in webhook consumers, causing duplicate actions.

●Retrying aggressively without backoff during rate limiting.

Success Metrics

Successful Request Rate

>= 99% for non-4xx requests

Indicates resilient client logic and error handling.

Webhook Processing Delay

< 60 seconds median end-to-end

Keeps downstream automation timely and useful.

Auth Error Frequency

< 1% of total calls

Confirms credential management is stable.