Partner Integration Guide

This document outlines the technical standards for Business-to-Business (B2B) integrations with the JusPredict Backend. These standards ensure high-performance, institutional-grade security, and predictable system behavior for our partners.

Security Architecture

All B2B integrations must adhere to the following infrastructure-level security controls enforced at our partner gateway.

Mutual TLS (mTLS)

Establishing unbreakable trust. Both our servers and your backend verify each other’s certificates for every request.

IP Whitelisting

Enforced at our network perimeter. Only authorized backend IPs can reach our API via a dedicated secure tunnel.

B2B Pattern

Requests MUST originate from your backend. Direct device-to-B2B calls are strictly prohibited for security.

Traffic & Performance

Rate Management

To ensure platform stability and guaranteed performance for institutional partners:

Dedicated Limit: 5 Requests Per Second (RPS).
Isolation Key: Applied per User-Business pair (partner_id + user_id).
Overload Protection: Exceeding limits results in a standard 429 Too Many Requests.

Strategic Onboarding Options

Choose the integration path that best fits your user experience and security requirements.

Silent Shadow Sync

Seamless background synchronization ideal for white-label experiences. No user friction required.

User App

Partner

JusPredict

1. User Interaction

2. GET /v1/market-data

3. 404 User Not Found

4. POST /v1/user/provision

5. 201 Created

Key Benefit: Users are onboarded automatically the first time they interact with a prediction feature.

Technical Endpoint Reference

Direct endpoints optimized for high-performance partner integration.

Purpose	Method	Path	Required Headers
Fetch Market Data	`GET`	`/v1/market-data`	`X-Partner-ID`
Shadow Provisioning	`POST`	`/v1/user/provision`	`mTLS Cert`
Identity Linking	`POST`	`/v1/user/link`	`Linking-Token`