Documentation
A quick guide to connecting your site and receiving editorial articles. Have a question this does not answer? Email support@taploon.com.
1. Create your workspace
Sign up, then create your organization. Every account starts on the Editorial Pack with 200 monthly credits, roughly 20 articles.
2. Connect a destination
A destination is a site that receives your articles. Run the setup prompt and it scaffolds a secure ingest endpoint in your app (Next.js and Supabase first). You get two things:
- An ingest URL behind a high-entropy, unguessable path. Treat the full URL as a secret.
- An API key. Add it to your environment as TAPLOON_INGEST_KEY and deploy.
3. How delivery works
When an article is approved, Taploon sends it to your endpoint as a signed JSON payload with an Authorization Bearer header. Your endpoint verifies the key, validates the payload, writes the post to your database, and publishes it. Deliveries are idempotent, so a repeated push never double-publishes.
Example payload:
POST /api/taploon/ingest/<unguessable-slug>
Authorization: Bearer <TAPLOON_INGEST_KEY>
Content-Type: application/json
{
"id": "a1b2c3",
"title": "How to reduce SaaS churn",
"slug": "reduce-saas-churn",
"excerpt": "A practical guide ...",
"body_md": "## Intro ...",
"keywords": ["reduce saas churn"],
"published_at": "2026-06-27T10:00:00Z"
}4. Securing the endpoint
The endpoint that receives content should always:
- Verify the Authorization Bearer key with a constant-time comparison.
- Reject unauthenticated requests with 401 and malformed payloads with 400.
- Deduplicate by the article id so replays cannot create duplicates.
- Store no personal data. Payloads contain article content and metadata only.
See the security page for the full reference implementation.
5. Credits and cadence
- Each article costs about 10 credits.
- Set how many posts per day a destination should receive, within your plan.
- Running low? Buy a top-up pack anytime. Top-up credits never expire.