API Documentation (2.1.3)

Financial Analytics API

Overview

The Financial Analytics API provides comprehensive data analysis and insights for ISA investments and trading behavior. This powerful platform enables financial institutions, advisors, and analysts to access detailed metrics, trends, and recommendations through a simple, consistent REST API.

Key Capabilities

ISA Analytics

Access detailed analytics on Individual Savings Accounts (ISAs) including:

  • Provider market share and performance metrics
  • Customer demographic analysis across age groups and income brackets
  • Behavioral patterns and investment preferences
  • Term duration and risk profile analysis
  • Personalized provider recommendations

Trading Analytics

Comprehensive trading data analysis including:

  • Market trends and sentiment indicators
  • Trading pair popularity and directional bias
  • Trader behavior patterns and preferences
  • Broker performance metrics and comparison
  • Predictive signals and anomaly detection

Authentication

All API requests require authentication using an API key which should be passed as a query parameter:

GET /isa/summary?api_key=your_api_key

Contact our team to obtain your API key and access credentials.

Rate Limits

Our API offers different tiers of access:

  • Standard: 60 requests per minute
  • Premium: 300 requests per minute
  • Enterprise: Custom limits available

Response Format

All responses are returned in JSON format and follow a consistent structure:

{
  "timestamp": "2024-03-20T12:00:00Z",
  "data": {
    // Response data specific to the endpoint
  }
}

Error Handling

The API uses standard HTTP status codes to indicate the success or failure of requests:

  • 200: Success
  • 400: Bad request (invalid parameters)
  • 401: Unauthorized (invalid API key)
  • 404: Resource not found
  • 422: Validation error
  • 429: Rate limit exceeded
  • 500: Server error

Error responses include detailed information to help troubleshoot the issue:

{
  "timestamp": "2024-03-20T12:00:00Z",
  "error": "Validation Error",
  "detail": "Invalid parameter: start_date must be in DD-MM-YY format"
}

Versioning

The API uses a semantic versioning system (Major.Minor.Patch). The current version is 2.1.3.

Getting Started

  1. Sign up for an API key at our developer portal
  2. Explore the available endpoints in this documentation
  3. Make your first request to the API
  4. Implement the insights into your application or analysis
Download OpenAPI description
Languages
Servers
Mock server
https://docs.tfe.ai/_mock/openapi/
Production server
https://api.tfe.ai/

Behavioral

Operations

Demographic

Operations

Provider

Operations

Summary

Operations

Market Analysis

Analysis of market trends, instruments, and trading signals

Operations

Trader Analytics

Analysis of trader behavior and demographics

Operations

Broker Insights

Broker analysis, comparison, and performance metrics

Operations

Summary Metrics

Overview statistics and most popular metrics

Operations

FAQ

Error Handling

Error Handling Guide for TFE API

This document provides comprehensive information about handling errors when integrating with the TFE API.

Understanding Error Responses

All API errors follow a consistent format:

{
  "timestamp": "2023-06-20T15:45:32.123Z",
  "error": "error_code",
  "detail": "Human-readable error message"
}

Where:

  • timestamp: When the error occurred (UTC)
  • error: A machine-readable error code
  • detail: A human-readable explanation of what went wrong

For validation errors, additional fields may be included:

{
  "timestamp": "2023-06-20T15:45:32.123Z",
  "error": "validation_error",
  "detail": "One or more validation errors occurred",
  "errors": [
    {
      "field": "name_of_field",
      "message": "Specific validation error message"
    }
  ]
}

HTTP Status Codes

The API uses standard HTTP status codes to indicate the success or failure of a request:

Status CodeDescription
200 OKThe request succeeded
400 Bad RequestThe request was malformed or invalid
401 UnauthorizedAuthentication failed (missing or invalid API key)
404 Not FoundThe requested resource doesn't exist or no data found
422 Unprocessable EntityThe request was well-formed but couldn't be processed (e.g., validation failed)
429 Too Many RequestsRate limit exceeded
500 Internal Server ErrorAn unexpected error occurred on the server
503 Service UnavailableThe service is temporarily unavailable

Common Error Types

Quick Start Guide

Authentication

Security