Ship against api.ftpropaganda.com with confidence

Stable REST endpoints, predictable error shapes, and authentication patterns for production and sandbox integrations. This portal is optimized for backend teams that need quick implementation details, not marketing copy.

REST + JSON Bearer auth Cursor pagination Webhook signatures

Start Quickstart Open Full Reference

Quickstart

Verify credentials and make your first authenticated call in under one minute.

Step 1. Export your API key.
Step 2. Call /v1/me.
Step 3. Continue with collection endpoints in the reference section.

cURL

export BASE_URL="https://api.ftpropaganda.com"
export API_KEY="YOUR_API_KEY"

curl -sS "$BASE_URL/v1/me" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Accept: application/json" | jq .

Authentication

All private endpoints require a bearer token and JSON headers.

Use test keys in local development, production keys only in server-side secret stores.

Required headers

Authorization: Bearer YOUR_API_KEY
Accept: application/json
Content-Type: application/json

API Reference

Host:

Filter by method, path, or description. Press / to focus search.

Method	Path	Description	Auth
GET	/health	Read-only service and dependency health summary.	No
GET	/v1/me	Returns actor ID, role, and granted token scopes.	Yes
GET	/v1/stories	Lists stories with cursor pagination and publish state filters.	Yes
GET	/v1/stories/:id	Retrieves a story document by canonical object ID.	Yes
POST	/v1/campaigns	Creates a campaign and schedules optional start window.	Yes
POST	/v1/webhooks	Registers a callback URL and event subscriptions.	Yes
DELETE	/v1/webhooks/:id	Deletes a webhook subscription and revokes signing secret.	Yes

List Stories Example

Pagination defaults to 25 results and caps at 100.

cURL

curl -sS "https://api.ftpropaganda.com/v1/stories?limit=25&status=published" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Accept: application/json" | jq .

Create Campaign Example

POST routes should include idempotency keys to avoid duplicate writes.

cURL

curl -sS "https://api.ftpropaganda.com/v1/campaigns" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 0f49b26f-0ed4-42f9-92d8-d758ad4d4e42" \
  -d '{
    "name": "North America Rollout",
    "storyIds": ["st_1002", "st_1008"],
    "startsAt": "2026-03-01T09:00:00Z"
  }' | jq .

System Status

All systems operational

Live operational view for public API services on .

Component	State	Notes
API Gateway	Operational	Median response time 98ms.
Auth Service	Operational	Token introspection healthy.
Stories API	Operational	Replication lag below 2 seconds.
Webhooks	Degraded	Retry queue slightly above baseline.

Recent Incidents

Incident summaries for the last 30 days.

2026-02-10 09:14 UTC
Webhook deliveries delayed due to queue worker restart. Full recovery in 11 minutes.
2026-01-29 18:02 UTC
Elevated 502 responses on /v1/stories during database failover.
2026-01-12 07:43 UTC
No incident: planned maintenance window completed without customer impact.

Changelog

Release history for . Newest entries appear first.

v1.7.0 · 2026-02-18

Added campaign scheduling controls and webhook destination validation.

Added startsAt and endsAt fields to POST /v1/campaigns.
Added delivery event campaign.published for webhook consumers.
Improved pagination stability on GET /v1/stories under concurrent writes.

v1.6.2 · 2026-01-30

Reliability release after regional failover test.

Reduced gateway timeout variance for read-heavy workloads.
Improved idempotency key replay handling for write retries.

v1.6.0 · 2026-01-10

Webhook management endpoints promoted to general availability.

Added POST /v1/webhooks and DELETE /v1/webhooks/:id.
Added HMAC signature documentation and sample verification payloads.
Deprecated legacy event field payloadType; removal planned for 2026-04-15.