FTT API

Automated Subscription Cancellation Infrastructure™

The FTT API allows applications, AI agents, banks, fintech platforms, and enterprise systems to initiate, monitor, and manage subscription cancellation attempts through a standardized interface.

Built for reliability, auditability, automation, and AI Callability.

FTT standardizes subscription cancellation execution through a deterministic state machine, structured outcome model, confidence scoring engine, and audit-ready EventLog architecture.

Applications submit requests. FTT manages execution.

BASE URL

https://api.freetrialterminator.com/api/v1

AUTHENTICATION

All requests require:

Authorization: Bearer YOUR_API_KEY

Additional caller identification headers:

X-FTT-Caller-ID: your_application
X-FTT-Caller-Type: AI_AGENT

Supported Caller Types:

AI_AGENT
HUMAN_USER
THIRD_PARTY_APP
INTERNAL_SYSTEM

QUICK START

Initiate a Cancellation Attempt

POST /cancellations/attempt

Example Request

{
  "provider_id": "provider_123",
  "user_identifier": "user@example.com"
}

Example Response

{
  "request_id": "req_123",
  "attempt_id": "attempt_123",
  "status": "IN_PROGRESS",
  "confidence_score": 0.92
}

Check Status

GET /cancellations/{attempt_id}

Example Response

{
  "attempt_id": "attempt_123",
  "status": "CONFIRMED",
  "confidence_score": 0.97
}

CANCELLATION LIFECYCLE

FTT tracks cancellation progress using a structured state model.

Core States	Additional States
`DETECTED` `SCHEDULED` `INITIATED` `IN_PROGRESS` `PENDING_CONFIRMATION` `CONFIRMED`	`ACTION_REQUIRED` `FAILED` `INTERRUPTED` `DLQ`

DETERMINISTIC CONFIDENCE SCORING™

Unlike traditional cancellation systems that provide binary outcomes, FTT evaluates provider history, friction severity, cancellation method, confirmation type, and retry history to generate transparent and repeatable confidence assessments.

Every confidence score is calculated using a deterministic model, ensuring the same inputs produce the same outcome.

Confidence scores are versioned, traceable, and tied directly to cancellation outcomes through FTT's EventLog architecture.

ERROR HANDLING

Example Error Response

{
  "error_code": "PROVIDER_UNAVAILABLE",
  "error_category": "TEMPORARY",
  "retryable": true,
  "next_step": "retry_later"
}

IDEMPOTENCY

FTT supports idempotent request handling via the Idempotency-Key header.

Safe retries return the original result without creating duplicate cancellation attempts, allowing AI systems, applications, and enterprise platforms to retry requests safely.

RATE LIMITS

Current default limits:

100 requests per minute
1,000 requests per hour

Rate limits may vary by integration tier.

EXAMPLE INTEGRATIONS

AI Agents

User	"Cancel my subscription."
Agent	Calls FTT API.
FTT	Returns structured cancellation outcome.

Banks & Credit Unions

Customer	Requests cancellation through banking interface.
Institution	Calls FTT API.
FTT	Executes and returns outcome status.

Fintech Platforms

User	Requests cancellation through dashboard.
Platform	Calls FTT API.
FTT	Returns real-time cancellation progress and confirmation status.

WEBHOOKS

Future Support

cancellation_confirmed
action_required
cancellation_failed