Custom HTTP
When imports fail, craft routes by hand
Some backends need bespoke headers, multi-step proxies, or mixed body modes. Custom HTTP lets you describe each route explicitly while still selling through the marketplace.
How it works
Three moves from raw source to a buyer-ready listing-no all-nighter on StackOverflow required.
Your edge cases
Collect the paths, methods, and auth headers that make your integration unique.
Your configuration
Add routes in the dashboard: public vs private fields, raw JSON vs form-style bodies, playground paths.
Your buyers
They see only what you mark public—everything else stays in the secure proxy configuration.
Ditch the slow path.
Do it the ApiClay way.
The spaghetti NGINX way
Rewrite rules nobody remembers writing.
The ApiClay way
Declarative routes with attached billing and analytics.
The shared secret way
Partners embed the same HMAC key everywhere.
The ApiClay way
Per-buyer marketplace credentials with request logs.
The undocumented curl way
“Run this example from 2019.”
The ApiClay way
Structured docs for the fields you choose to expose.
The serverless sprawl way
Twenty Lambda functions, zero discoverability.
The ApiClay way
One listing that explains how they fit together.
Works with the tools you already use
Buyers and publishers integrate ApiClay APIs the same way they integrate any REST product: HTTP, keys, and OpenAPI-style docs.
Postman & Insomnia
Exercise endpoints from your workspace with the same base URL and headers we document.
curl & scripts
Automate pulls in CI, cron, or ETL without a proprietary SDK.
OpenAPI clients
Generate typed clients when your listing is backed by Swagger or custom HTTP routes.
Retool & internal apps
Point low-code tools at stable JSON endpoints instead of raw database access.
AI coding assistants
Paste OpenAPI-style docs into your AI-assisted IDE or coding chat and wire UIs or agents to live data fast—no bespoke SDK required.
Serverless & containers
Call the marketplace gateway from Lambda, Cloud Run, or your API mesh.
Endless possibilities
Do not just expose rows-ship a business buyers can subscribe to.
The webhook verifier
Document inbound verification headers while keeping signing secrets private.
The SOAP shim
Proxy XML upstream but expose JSON routes to modern clients.
The device command API
Route signed device payloads through controlled paths with tight rate limits.
The signed URL mint
Expose a route that returns short-lived URLs without leaking storage credentials.
The ticketed escalation
Pair custom routes with ApiClay support tickets so buyers can report issues per route.
The tool boundary
Give agents exactly three POST routes—nothing more, nothing less.
Simple economics: publish, subscribe, scale
You set trials, subscription plans, and pay-as-you-go credits. Buyers only pay for what they use—no surprise infra line items on your side for the gateway.
Free to list: create a company, connect your source, and go through approval like any marketplace vendor.
Trials and caps: give first-time integrators a taste without exposing unlimited rows or requests.
Credits & plans: mix recurring plans with metered overage so power users can grow into paid usage.
Burning questions
Straight answers-no lawyer-speak.
How is this different from Swagger mode?
Can I mix public and private headers?
Is raw JSON supported?
What about aggregators?
Stop overthinking the API layer
Pick your datasource, wire it once in the dashboard, and ship a documented product your buyers can trust tonight.