The MyTCRPlus REST API at api.mytcrplus.com exposes all 16 compliance tools as programmable endpoints. Whether you are building a compliance dashboard, integrating with a CPaaS platform, or adding pre-flight validation to an internal tool, the API lets you call any MyTCRPlus tool directly from your code.
This guide covers authentication, billing, core endpoints, error handling, and integration patterns with working code examples.
Authentication
The API uses JWT-based authentication. Obtain a token by sending your API credentials to the auth endpoint, then include the token in the Authorization header of all subsequent requests.
POST /v1/auth
Content-Type: application/json
{
"api_key": "your_api_key",
"api_secret": "your_api_secret"
}
Response:
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"expires_in": 3600
}
Include the token in all API calls:
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
Token-Based Billing
Each API call consumes one token from your account balance. Token costs vary by tool:
- Message validation: $0.50 per call
- Rejection decoding: $0.60 per call
- Trust score simulation: $0.70 per call
- Compliance document generation: $0.90 per call
Tokens never expire. Every account receives one free daily token and two free trial tokens at signup. Check your balance:
GET /v1/balance
Response: {
"balance": 42,
"free_tokens_today": 0,
"next_free_token_in": "14 hours"
}
Core Endpoints
All 16 tools are available under /v1/tools. The following endpoints cover the most common compliance operations.
POST /v1/tools/rejection-decode
Submit a TCR error code and receive a plain-English explanation with remediation steps.
Request:
{
"error_code": "BRAND-0042"
}
Response:
{
"tool": "rejection-decode",
"error_code": "BRAND-0042",
"explanation": "The brand name on your registration does not match the legal name on file with your vetting provider.",
"severity": "high",
"remediation_steps": [
"Verify the legal name on your EIN or VAT registration matches your brand registration.",
"Update the brand name in the TCR portal to match the vetted legal name.",
"Re-submit the brand for vetting if the name change requires re-vetting."
],
"estimated_fix_time": "30 minutes"
}
POST /v1/tools/message-validate
Submit a message template for compliance scanning.
Request:
{
"message": "Hi {{first_name}}, your appointment is confirmed for {{date}}. Reply STOP to opt out.",
"use_case": "account_notification"
}
Response:
{
"tool": "message-validate",
"overall_score": 94,
"status": "pass",
"flags": [],
"recommendations": [
"Consider adding 'Msg and data rates may apply' for full TCPA compliance."
]
}
POST /v1/tools/trust-score-simulate
Estimate your TCR trust score before registration.
Request:
{
"brand_vetting_status": "verified",
"campaign_age_months": 6,
"message_type": "mixed_marketing_and_service",
"industry": "healthcare",
"monthly_volume": 50000
}
Response:
{
"tool": "trust-score-simulate",
"estimated_score": 82,
"passing_threshold": 75,
"status": "pass",
"improvement_tips": [
"Separate marketing and service messages into different campaigns to avoid mixed-type scoring penalties.",
"Increase brand vetting to Stamped level for a 5-8 point score boost."
]
}
POST /v1/tools/use-case-wizard
Get the correct TCR use case code for your messaging scenario.
Request:
{
"industry": "healthcare",
"audience_type": "existing_patients",
"message_purpose": "appointment_reminders",
"opt_in_method": "web_form"
}
Response:
{
"tool": "use-case-wizard",
"recommended_use_case": "Customer Care",
"use_case_code": "C0201",
"alternatives": [
"Account Notification - C0101"
],
"notes": "Appointment reminders for existing patients qualify under Customer Care. Use separate campaigns for marketing."
}
POST /v1/tools/compliance-document
Generate carrier-ready compliance documents.
Request:
{
"document_type": "privacy_policy",
"brand_name": "Acme Health",
"website": "https://acmehealth.com",
"industry": "healthcare",
"data_collected": ["name", "email", "phone", "appointment_history"]
}
Response:
{
"tool": "compliance-document",
"document_type": "privacy_policy",
"content": "Privacy Policy for Acme Health...",
"tcr_compliant": true,
"generated_at": "2026-07-01T12:00:00Z"
}
Error Handling
The API returns standard HTTP status codes:
- 200: Success
- 400: Validation error – check your request parameters
- 401: Authentication failure – your token is missing or expired
- 402: Insufficient tokens – purchase more tokens in the dashboard
- 429: Rate limit exceeded – slow down your request rate
Error response format:
{
"error": {
"code": "INSUFFICIENT_TOKENS",
"message": "Your token balance is zero. Purchase more tokens in the dashboard.",
"reference": "ERR-TOK-001"
}
}
Rate Limits
Standard tier: 60 requests per minute. Pro tier: 300 requests per minute. Enterprise tier: custom limits. Rate limit headers are returned with every response and include your current limit, remaining requests, and reset time.
Integration Example: Automated Compliance Pipeline
Here is a typical flow for checking a campaign before TCR submission:
1. POST /v1/tools/use-case-wizard -> Get correct use case code 2. POST /v1/tools/message-validate -> Validate message content 3. POST /v1/tools/trust-score-simulate -> Estimate approval score 4. Submit to TCR with validated data
All four calls complete in under two seconds. For CPaaS platforms, the integration pattern is: intercept outbound messages, call the message validator, block non-compliant messages, and log compliance data to your audit trail.
Getting Started
- Sign up at tools.mytcrplus.com to receive your API credentials
- You get two free trial tokens immediately
- Read the full API reference at api.mytcrplus.com/docs
- The reference includes an OpenAPI specification and code samples in Python, JavaScript, PHP, and cURL
Building your own compliance system requires 6-12 months of development and significant engineering investment. The MyTCRPlus API delivers production-ready compliance in one integration. Every compliance tool you need is one HTTP call away.