--- title: "PSR - Centralized Partner Lead API Platform" description: "Centralized API platform receiving and routing real estate leads from 9+ external partner portals to CRM Hermes via Adobe Campaign - each partner integration supervised end-to-end, from API specification to production monitoring." locale: "en" canonical: "https://portfolio.josedacosta.info/en/achievements/psr-plateforme-api-partenaires" source: "https://portfolio.josedacosta.info/en/achievements/psr-plateforme-api-partenaires.md" html_source: "https://portfolio.josedacosta.info/en/achievements/psr-plateforme-api-partenaires" author: "José DA COSTA" date: "2021" type: "achievement" slug: "psr-plateforme-api-partenaires" tags: ["REST API", "Microsoft API Manager", "Adobe Campaign v7", "Dynamics 365", "AWS EKS", "Kubernetes", "Docker", "GitLab CI", "SOFT Monitor", "Jira"] generated_at: "2026-04-23T15:46:30.508Z" --- # PSR - Centralized Partner Lead API Platform Centralized API platform receiving and routing real estate leads from 9+ external partner portals to CRM Hermes via Adobe Campaign - each partner integration supervised end-to-end, from API specification to production monitoring. **Date:** February 2021 - 2024 **Duration:** ~3 years **Role:** Project Manager / Product Owner - API Platform Owner **Technologies:** REST API, Microsoft API Manager, Adobe Campaign v7, Dynamics 365, AWS EKS, Kubernetes, Docker, GitLab CI, SOFT Monitor, Jira ### Key Metrics - Partner APIs: **-** - Integrated and maintained - Lead Volume: **-** - ~1 lead every 2 seconds peak - Lead Loss Rate: **-** - Zero major loss incidents - Onboarding Time: **-** - Reduced from weeks to days ## Presentation _Project definition and scope_ ### Nature Centralized REST API platform for multi-partner lead reception, normalization, and CRM routing ### Domain Real Estate / PropTech - Lead Management (B2B internal + B2B external partners) ### Key Architecture Decisions - [object Object] - [object Object] - [object Object] ### Scope - Expose standardized REST APIs for each lead generation partner - Normalize lead data (name, email, phone, program, source) regardless of partner format - Route leads to CRM Hermes via Adobe Campaign (Neolane) for commercial follow-up - Detect anomalies: blocked leads, duplicates, format errors - Manage API credentials and access via Microsoft API Manager (APIM) - Monitor lead quality with SOFT Monitor alerts and email notifications **Content:** The **PSR (Pichet Services Repository)** is the **centralized API platform** of the Groupe Pichet for receiving and routing real estate leads from external partner portals. Every real estate portal or marketing partner generating prospects for Pichet connects to the PSR via a dedicated API endpoint, which normalizes data and transmits it to the CRM Hermes (Dynamics 365) through Adobe Campaign (Neolane) and the Microsoft API Manager (APIM). As Lead Developer and API Platform Owner, I supervised the integration of each new partner API and the platform's functional evolutions, coordinating with the marketing teams and external technical service providers. The PSR is a **business-critical system**: every lead lost or incorrectly routed translates directly into a missed sales opportunity in a highly competitive real estate market. **Nature Label:** Nature **Domain Label:** Domain **Scope Label:** Functional Scope ## Objectives, Context, Stakes & Risks _Strategic vision and constraints_ ### Obj - Expose standardized APIs for each lead generation partner with consistent data contracts - Normalize all lead data regardless of partner-specific format or protocol - Route leads reliably to CRM Hermes via Adobe Campaign for commercial pipeline tracking - Supervise lead flow quality: anomaly detection, blocked leads, duplicate filtering - Manage credentials and API access centrally via Microsoft API Manager ### Context The project was initiated within the **SI Marketing team** at Groupe Pichet, where the growing number of external lead sources (real estate portals, advertising partners, marketing platforms) created the need for a **single entry point** to centralize and normalize incoming leads before routing them to the commercial CRM. The existing landscape was fragmented: each partner had its own data format, authentication method, and delivery protocol. Without the PSR, integrating a new partner required custom development on the CRM side - an unsustainable approach as the partner ecosystem grew. The PSR was designed to **absorb this heterogeneity** and provide a clean, standardized interface to the downstream systems. ### Stakes Leads are the **lifeblood of commercial activity** in real estate. Each lead represents a potential buyer, and the market is fiercely competitive: losing a lead to a routing error or a delayed integration means giving that prospect to a competitor. With 9+ partners generating leads simultaneously, the PSR became the **single most critical data pipeline** feeding the commercial teams' daily pipeline. The commercial impact was direct and measurable: a partner API down for a single day could mean **dozens of lost prospects** - each worth potentially hundreds of thousands of euros in property sales. ### Security & RGPD Compliance - Per-partner credential isolation via APIM: each partner receives unique API keys with scoped permissions - no partner can access another partner's data or endpoints - Systematic API key rotation policy enforced through APIM lifecycle management - credentials renewed on schedule to limit exposure window - RGPD compliance for personal data: leads contain name, email, phone - data transmitted over HTTPS only, no persistent storage in intermediate layers, CRM as sole data repository - Security audit conducted in February 2023 covering PSR infrastructure, APIM configuration, and Adobe Campaign integration - resulting in hardened access controls and updated firewall rules - Input validation at gateway level: format checks, payload size limits, and malformed request rejection before data reaches internal systems ### Risk - [object Object] - [object Object] - [object Object] - [object Object] **Objectives:** Objectives **Context:** Context **Stakes:** Stakes **Risks:** Risks ## The Steps - What I Did _Chronological progression of the project_ ## The Actors - Interactions _Teams, stakeholders and collaboration_ ### Technical Leadership & Knowledge Transfer - Authored the complete partner integration playbook on Confluence - a step-by-step guide enabling any team member to onboard a new partner autonomously, from APIM credential setup to production monitoring - Conducted internal technical meetups on API integration patterns, sharing lessons learned from partner onboarding with the broader SI team - Produced and maintained API documentation across 5 versions (v1 to v5), serving as the reference for both internal teams and external partners - Trained external partner technical teams on PSR API specifications, authentication flows, and testing procedures during each onboarding cycle - Defined code quality standards for the PSR codebase: validation patterns, error handling conventions, and logging practices adopted across the SI Marketing team **Content:** The PSR project operated at the intersection of **marketing, IT, and external partners**. Each new partner integration required coordinating between the partner's technical team (for API specifications), the SI Marketing team (for business validation), and the CRM team (for lead routing confirmation). I served as the **single technical point of contact** for all partner integrations. ## The Results _Impact for me and for the company_ ### For Me - Deepened expertise in API integration patterns: authentication, normalization, routing, error handling at enterprise scale - Mastered the Microsoft API Manager platform for credential and access management - Developed strong coordination skills working at the intersection of marketing, IT, and external partners - Gained experience in lead management domain: data quality, deduplication, CRM routing strategies - Built confidence in owning a business-critical platform where every failure had direct commercial impact ### For Company - 9+ partner APIs integrated → diversified lead acquisition channels feeding the commercial pipeline - Centralized lead entry point → eliminated the need for custom CRM-side development per partner - Standardized data format → consistent lead quality regardless of source, improving commercial team efficiency - Real-time monitoring → immediate detection of anomalies, reducing lead loss to near-zero - Scalable architecture → new partner onboarding reduced from weeks to days with the PSR playbook - 2024 refactoring → future-proofed the platform with improved SeLoger and Adobe Campaign integrations ### Monitoring & Observability Strategy - SOFT Monitor dashboard with real-time KPI gauges tracking lead flow health across all 9+ partners simultaneously - Automated email alerts triggered on lead processing anomalies: blocked leads, format validation failures, partner API timeouts, and routing errors - Per-partner flux tracking: each partner API has individual monitoring with transaction logs, success/failure rates, and volume trends - Proactive anomaly detection: format changes from partners (field additions, encoding shifts) caught at validation layer before impacting downstream systems - Production incident response: monitoring enabled sub-minute detection of partner outages, reducing silent lead loss from days to minutes **For Me:** For Me **For Company:** For the Company ## The Aftermath _What happened after delivery_ **Content:** After the initial wave of partner integrations (2021-2023), the PSR entered a **stabilization and optimization phase**. The platform continued to process leads daily from all integrated partners, with monitoring alerts catching occasional anomalies (format changes from partners, API deprecations, credential renewals). The **2024 refactoring** marked a significant architectural evolution: the SeLoger API integration was redesigned, and the Adobe Campaign API layer was modernized. This refactoring demonstrated that the original architectural choices were **sound but needed updating** as both internal requirements and external partner APIs evolved. As of today, the PSR remains **the single entry point for all external lead acquisition** at Groupe Pichet. The partner onboarding playbook I documented enables the team to integrate new partners autonomously, ensuring knowledge continuity beyond my direct involvement. ## My Critical Reflection _Lessons learned and honest assessment_ ### Positive - The incremental partner-by-partner approach allowed us to validate each integration thoroughly before moving to the next - zero major lead loss incidents during onboarding - Using Microsoft APIM as a gateway layer provided clean credential isolation and throttling - partners never had direct access to internal systems - The SOFT Monitor integration gave us real-time visibility into lead flow health, catching issues within minutes instead of days - The normalization layer successfully absorbed the heterogeneity of 9+ partner formats into a single clean CRM-compatible schema ### Improvement - The Adobe Campaign v6 to v7 migration revealed a fragility: URL changes required manual updates across all partner configurations - a configuration management tool would have simplified this - Lead deduplication logic could have been more sophisticated - the basic matching was sufficient but edge cases (phone format variations, accent handling) required manual review - End-to-end integration testing was manual and time-consuming - automated partner simulation would have accelerated the onboarding cycle - Documentation was sometimes written after the fact rather than during development - earlier documentation would have eased knowledge transfer ### Tradeoff - [object Object] - [object Object] - [object Object] - [object Object] ### Lesson - In lead management, speed matters as much as accuracy - a fast but slightly imperfect routing beats a slow but perfect one, because leads go cold quickly - API gateway layers (like APIM) are essential when dealing with multiple external partners - they provide security, monitoring, and credential isolation in a single layer - Partner-by-partner validation with business teams is non-negotiable - even technically identical integrations can have different business expectations - A well-documented onboarding playbook is the best investment for long-term team autonomy - the PSR playbook outlived my direct involvement on the project **Positives:** What Worked Well **Improvements:** What Could Be Improved **Lessons:** Lessons Learned