Developers

Stop rebuilding the same business backend for every custom website.

Client projects look different on the surface. Behind them, teams rebuild content, products, media, enquiries, customer records, permissions, analytics and another admin. Webtools ships those foundations as a backend contract.

Read the API docs Create a project

Project-scoped API

Resolve the Project. Fetch what the frontend needs.

Storefront routes sit under a project slug. Projects require a publishable key and allowed browser origin where configured. Trusted server integrations use a secret key.

Products, categories and collections
Posts, authors, taxonomy and search
Carts, shipping choices and checkout
Customer registration and order history
Subscriptions, enquiries and events

storefront.ts

const response = await fetch(
  "https://api.webtools.ng/api/v1/storefront/" +
  "projects/sable-row/products",
  {
    headers: {
      "X-Project-Key": "wt_pk_..."
    }
  }
)

const catalogue = await response.json()

Agent integration

Give AI agents a docs URL, not a Swagger dump.

Issue a secret project key with storefront scopes in the dashboard. Agents call agent-docs for only the modules your project has enabled, then seed or write incrementally on storefront paths.

storefront.docs — feature-filtered integration pack
storefront.seed — batch bootstrap with dry-run support
storefront.write.* — products, content, media, CRM, and more
Publishable keys stay on public reads, carts, and checkout

Read the AI agent integration guide

agent onboarding

curl "https://api.webtools.ng/api/v1/storefront/" +
  "projects/acme/agent-docs?format=json" \
  -H "Authorization: Bearer wt_sk_..."

// Returns only enabled modules with
// handoff content and request samples

await fetch(
  "https://api.webtools.ng/api/v1/storefront/" +
  "projects/acme/seed",
  {
    method: "POST",
    headers: {
      Authorization: "Bearer wt_sk_...",
      "Content-Type": "application/json",
      "Idempotency-Key": "onboarding-v1"
    },
    body: JSON.stringify({
      dry_run: true,
      catalogue: { products: [{ name: "Demo", slug: "demo" }] }
    })
  }
)

Frontends teams ship

Different frontends. The same operational foundation.

Enable the capability areas each business needs, then shape the storefront around its brand and workflow.

Ecommerce storefront

A custom storefront on managed catalogue, carts, customers and orders.

Service company website

Services, Past Works, enquiries, forms and content on one Project backend.

Media publication

An editorial frontend backed by authors, taxonomy, media and subscribers.

Church website

Articles, media, programmes and contact paths that change often.

Agency portfolio

Past Works that generate enquiries your team follows in CRM.

Customer portal or app

A web or mobile client on the same project-scoped contract.

API building blocks

Storefront API for public resources. Dashboard API for operations.

The Storefront API exposes published, customer-facing resources through a publishable project key. The authenticated Dashboard API handles business records, private CRM work, project settings and team access.

Commerce

Products · Categories · Collections · Carts · Customers · Orders · Shipping

Content

Posts · Authors · Categories · Tags · Media · Subscribers

Service websites

Services · Past Works · Enquiries · Forms

Operations

Projects · Features · Members · Permissions · API keys · Agent docs · CRM

Frontend freedom

Bring the framework your product needs.

Use Next.js, React, Astro, Vite, React Native, a server-rendered application or any client that consumes HTTP APIs. Webtools leaves the frontend as your choice.

Next.jsReactAstroViteReact NativeMobile appsServer-rendered appsAny HTTP client

Integration primitives

The important boundaries are explicit.

Webtools separates dashboard accounts, storefront customers and project credentials so each frontend gets the access model it needs.

Project routes

Every public resource resolves inside one project slug.

Publishable keys

Built for browser storefronts, with origin checks where configured.

Secret keys

For trusted server-side work; never ship them to a browser.

Agent integration

Secret keys can fetch feature-filtered docs and seed or write project content without dashboard login.

Feature gates

Disabled project areas fail closed instead of leaking partial behavior.

Commerce behavior

Follow the API contract. Keep payment assumptions out of the frontend.

Checkout validates the cart and creates order and payment records with an idempotency key. The current checkout flow defaults to manual payment confirmation.

From Project to production

A short path from setup to a frontend your client operates.

01
Create the Project
02
Enable the right features
03
Issue a secret key for agents
04
Fetch agent-docs into context
05
Seed or write starter content
06
Create a publishable key
07
Connect the public frontend

The full API reference is pages you can read.

Every storefront endpoint — paths, parameters, request and response fields, authentication and errors — is documented at webtools.ng/docs/api. The machine-readable OpenAPI document stays available for code generation. Do not infer fields from this marketing page.

Open the API reference OpenAPI JSON (for codegen)

Start with one project

Build the frontend you want on a backend your team operates.

Bring catalogue, content, customer activity and project controls together behind it.

Create an account Explore the API