API Developer Hub

Authentication

Production calls should include a private API key. Public no-key calls should remain rejected.

Authorization: Bearer YOUR_TSWG_API_KEY
X-TSWG-API-Key: YOUR_TSWG_API_KEY

Proof review actions

Admins can approve, reject, or return API proof submissions to pending review. Approval publishes proof; rejection keeps it private. These actions do not call AI providers or payment systems.

Submit API product proof

API users, teams, and product builders can submit proof screenshots, demos, metrics, before/after examples, and workflow automation evidence for admin review.

API request queue and lifecycle

Admins can review queued API requests, provider status, proof requirements, and request event timelines from the API Request Queue. This admin surface does not trigger provider generation.

API usage analytics and privacy

Admins can review API usage rows, client usage summaries, endpoint activity, and hash-prefix privacy from the API Usage Analytics center. Raw IPs, raw user agents, and full hashes are not displayed.

API client activation and key privacy

After manual verification and activation, admins can review activated clients, monthly limits, usage rows, and key-hash prefixes from the API Client Directory. Raw API keys are not displayed.

Manual activation path

After a request is submitted and payment is verified manually, an admin can activate the API client from the API Access Requests queue. Activation creates a protected API client record and updates the request status without charging or calling external providers.

Request paid API access

Submit a paid API access request for AI Avatar Creation, Text to Image, Text/Image to Video, Text to Audio, SVG API, or protected AI API workflows. Requests are manually reviewed before activation.

Paid access and local payment workflow

• API users need a paid TSWG API access plan before production usage.
• Every paid API product should show the problem it solves, who it is for, use cases, proof, screenshots/results, workflow, and automation value.
• API access should be reviewed through Premium Access or a verified manual payment path before activation.
• API keys must be kept private. Public requests without valid keys should remain rejected.
• Local payment collection should capture buyer country, preferred payment method, payment reference, status, and manual verification notes before activation.

What API products must prove

• Problem: What manual or expensive workflow does this API remove?
• Solution: What output does the user receive?
• Who it is for: Creators, brands, educators, agencies, developers, marketplace sellers, and teams.
• Use cases: Avatars, product images, explainer videos, voiceovers, documentation assets, proof screenshots, and automated content workflows.
• Proof: Results screenshots, before/after output, demo endpoint, docs, sample payload, and expected response.
• Nuance: Prompt quality, review flow, queue status, usage limits, privacy, and key protection.

Admin API Product Registry

Admins can review API products, proof requirements, billing plans, payment review paths, request events, SVG clients, and API usage from the API Product Registry.

Example request

curl -X POST "https://thesurestwayguides.com/tswg-ai-api.php?action=create&type=image" \
  -H "Authorization: Bearer YOUR_TSWG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"premium creator dashboard product image","use_case":"marketplace proof screenshot"}'

Approved API Proof Gallery

Published API proof appears in the public gallery after admin review. Pending, rejected, and private proofs are not shown.

API Product Catalog

Explore TSWG API products, proof routing, outcomes, workflows, endpoints, and access paths from the public API Product Catalog.

Product-specific API pages

Each API product now has a detail route for product-specific access requests, proof submissions, approved proof routing, and endpoint context.