Archive

Posts Tagged ‘technology’

How to Check Polish Vehicle History Using Python and RapidAPI

When buying a used car in Poland, one of the most important steps is verifying the vehicle’s history. Thanks to modern APIs, you can now programmatically access official vehicle registration data from the CEPiK (Central Register of Vehicles and Drivers) system. In this tutorial, we’ll show you how to use Python to check a vehicle’s complete history using the Polish Vehicle History API on RapidAPI.

What Information Can You Get?

The Polish Vehicle History API provides comprehensive data about any registered vehicle in Poland:

Technical Specifications

  • Make, model, year of manufacture
  • Engine capacity and power
  • Fuel type and emission standards
  • Weight specifications and seating capacity

Ownership History

  • Complete ownership timeline
  • Number of previous owners
  • Registration provinces
  • Corporate vs. private ownership

Technical Inspections

  • All periodic technical inspections with dates and results
  • Odometer readings at each inspection
  • Detection of rolled-back odometers

Legal Status

  • Current registration status
  • Valid insurance information
  • Stolen or withdrawn vehicle alerts

Risk Assessment

  • Accident history indicators
  • Damage reports
  • Taxi usage history
  • Odometer tampering detection

Getting Started

Prerequisites

First, install the required Python library:

pip install requests

Basic Implementation

Here’s a simple example to get you started:

import requests

# API configuration
url = "https://historia-pojazdow-polskich.p.rapidapi.com/EL6574U/YS3DD55C622039715/2002-06-04"

headers = {
    "x-rapidapi-host": "historia-pojazdow-polskich.p.rapidapi.com",
    "x-rapidapi-key": "YOUR_API_KEY_HERE"
}

# Make the request
response = requests.get(url, headers=headers)

# Check if request was successful
if response.status_code == 200:
    data = response.json()
    print("Data retrieved successfully!")
    print(data)
else:
    print(f"Error: {response.status_code}")
    print(response.text)

Advanced Implementation with Error Handling

For production use, you’ll want a more robust implementation:

import requests
import json
from typing import Optional, Dict, Any

class PolishVehicleHistoryAPI:
    def __init__(self, api_key: str):
        self.base_url = "https://historia-pojazdow-polskich.p.rapidapi.com"
        self.headers = {
            "x-rapidapi-host": "historia-pojazdow-polskich.p.rapidapi.com",
            "x-rapidapi-key": api_key
        }
    
    def check_vehicle(self, license_plate: str, vin: str, first_registration_date: str) -> Optional[Dict[Any, Any]]:
        """
        Check vehicle history
        
        Args:
            license_plate: License plate number (e.g., "EL6574U")
            vin: Vehicle identification number
            first_registration_date: Date in YYYY-MM-DD format
            
        Returns:
            Dictionary with vehicle data or None on error
        """
        url = f"{self.base_url}/{license_plate}/{vin}/{first_registration_date}"
        
        try:
            response = requests.get(url, headers=self.headers, timeout=10)
            
            if response.status_code == 200:
                return response.json()
            elif response.status_code == 404:
                print("Vehicle not found with provided parameters")
                return None
            elif response.status_code == 429:
                print("API rate limit exceeded")
                return None
            else:
                print(f"API error: {response.status_code} - {response.text}")
                return None
                
        except requests.exceptions.Timeout:
            print("Timeout - API not responding")
            return None
        except requests.exceptions.RequestException as e:
            print(f"Connection error: {e}")
            return None

def main():
    # IMPORTANT: Insert your RapidAPI key here
    API_KEY = "YOUR_API_KEY_HERE"
    
    # Create API instance
    api = PolishVehicleHistoryAPI(API_KEY)
    
    # Vehicle parameters
    license_plate = "EL6574U"
    vin = "YS3DD55C622039715"
    registration_date = "2002-06-04"
    
    print(f"Checking vehicle: {license_plate}")
    
    # Retrieve data
    data = api.check_vehicle(license_plate, vin, registration_date)
    
    if data:
        print("\n=== VEHICLE HISTORY RESULTS ===")
        
        # Display basic information
        if len(data) > 0 and "technicalData" in data[0]:
            basic_data = data[0]["technicalData"]["basicData"]
            print(f"Make: {basic_data.get('make')}")
            print(f"Model: {basic_data.get('model')}")
            print(f"Year: {basic_data.get('yearOfManufacture')}")
            print(f"Registration status: {basic_data.get('registrationStatus')}")
            
            # Odometer reading
            if basic_data.get('odometerReadings'):
                reading = basic_data['odometerReadings'][0]
                rolled_back = " (ODOMETER ROLLED BACK!)" if reading.get('rolledBack') else ""
                print(f"Mileage: {reading.get('value')} {reading.get('unit')}{rolled_back}")
        
        # Risk analysis (if available)
        if len(data) > 2 and "carfaxData" in data[2]:
            risk = data[2]["carfaxData"]["risk"]
            print("\n=== RISK ANALYSIS ===")
            print(f"Stolen: {'YES' if risk.get('stolen') else 'NO'}")
            print(f"Post-accident: {'YES' if risk.get('postAccident') else 'NO'}")
            print(f"Odometer tampering: {'YES' if risk.get('odometerTampering') else 'NO'}")
            print(f"Taxi: {'YES' if risk.get('taxi') else 'NO'}")
        
        # Save complete data to file
        with open(f"vehicle_history_{license_plate}.json", "w", encoding="utf-8") as f:
            json.dump(data, f, ensure_ascii=False, indent=2)
        print(f"\nComplete data saved to: vehicle_history_{license_plate}.json")
    
    else:
        print("Failed to retrieve vehicle data")

if __name__ == "__main__":
    main()

Understanding the API Response

The API returns data in three main sections:

1. Technical Data

Contains all technical specifications and current vehicle status:

technical_data = data[0]["technicalData"]["basicData"]
print(f"Make: {technical_data['make']}")
print(f"Model: {technical_data['model']}")
print(f"Engine capacity: {technical_data['engineCapacity']} cc")

2. Timeline Data

Provides complete ownership and inspection history:

timeline = data[1]["timelineData"]
print(f"Total owners: {timeline['totalOwners']}")
print(f"Current registration province: {timeline['registrationProvince']}")

# Loop through all events
for event in timeline["events"]:
    print(f"{event['eventDate']}: {event['eventName']}")

3. Risk Assessment

Carfax-style risk indicators:

risk_data = data[2]["carfaxData"]["risk"]
if risk_data["odometerTampering"]:
    print("⚠️ Warning: Possible odometer tampering detected!")

Real-World Use Cases

1. Used Car Marketplace Integration

def evaluate_vehicle_for_listing(license_plate, vin, registration_date):
    api = PolishVehicleHistoryAPI("YOUR_API_KEY")
    data = api.check_vehicle(license_plate, vin, registration_date)
    
    if not data:
        return {"status": "error", "message": "Cannot verify vehicle"}
    
    # Extract risk factors
    risk = data[2]["carfaxData"]["risk"] if len(data) > 2 else {}
    
    risk_score = sum([
        risk.get("stolen", False),
        risk.get("postAccident", False), 
        risk.get("odometerTampering", False),
        risk.get("taxi", False)
    ])
    
    return {
        "status": "success",
        "risk_level": "high" if risk_score > 1 else "low",
        "owners_count": data[1]["timelineData"]["totalOwners"],
        "mileage_verified": not data[0]["technicalData"]["basicData"]["odometerReadings"][0]["rolledBack"]
    }

2. Insurance Risk Assessment

def calculate_insurance_risk(vehicle_data):
    if not vehicle_data:
        return "unknown"
    
    timeline = vehicle_data[1]["timelineData"]
    risk_data = vehicle_data[2]["carfaxData"]["risk"]
    
    # High risk indicators
    if (timeline["totalOwners"] > 5 or 
        risk_data.get("postAccident") or 
        risk_data.get("taxi")):
        return "high_risk"
    
    return "standard_risk"

Getting Your API Key

  1. Sign up at RapidAPI.com
  2. Search for “Polish Vehicle History” or “Historia Pojazdów Polskich”
  3. Subscribe to an appropriate plan
  4. Copy your API key from the “Headers” section
  5. Replace "YOUR_API_KEY_HERE" with your actual key

API Parameters Explained

The API endpoint requires three parameters:

  • license_plate: The Polish license plate number (e.g., “EL6574U”)
  • vin: The 17-character Vehicle Identification Number
  • first_registration_date: Date when the vehicle was first registered in Poland (YYYY-MM-DD format)

Best Practices and Security

1. Secure API Key Management

Never hardcode your API key. Use environment variables instead:

import os

API_KEY = os.environ.get('RAPIDAPI_KEY')
if not API_KEY:
    raise ValueError("Please set RAPIDAPI_KEY environment variable")

2. Rate Limiting and Caching

Implement proper rate limiting to avoid exceeding API quotas:

import time
from functools import wraps

def rate_limit(max_calls_per_minute=60):
    min_interval = 60.0 / max_calls_per_minute
    last_called = [0.0]
    
    def decorator(func):
        @wraps(func)
        def wrapper(*args, **kwargs):
            elapsed = time.time() - last_called[0]
            left_to_wait = min_interval - elapsed
            if left_to_wait > 0:
                time.sleep(left_to_wait)
            ret = func(*args, **kwargs)
            last_called[0] = time.time()
            return ret
        return wrapper
    return decorator

@rate_limit(max_calls_per_minute=50)
def check_vehicle_with_rate_limit(api, license_plate, vin, date):
    return api.check_vehicle(license_plate, vin, date)

3. Error Handling and Retries

Implement exponential backoff for transient errors:

import time
import random

def check_vehicle_with_retry(api, license_plate, vin, date, max_retries=3):
    for attempt in range(max_retries):
        try:
            result = api.check_vehicle(license_plate, vin, date)
            if result is not None:
                return result
        except requests.exceptions.RequestException:
            if attempt < max_retries - 1:
                wait_time = (2 ** attempt) + random.random()
                time.sleep(wait_time)
            else:
                raise
    
    return None

Conclusion

The Polish Vehicle History API provides a powerful way to programmatically access comprehensive vehicle data directly from official government sources. Whether you’re building a used car marketplace, developing an insurance application, or creating tools for automotive professionals, this API offers reliable and up-to-date information about any vehicle registered in Poland.

The examples in this guide provide a solid foundation for integrating vehicle history checks into your Python applications. Remember to handle errors gracefully, respect rate limits, and keep your API credentials secure.

With this integration, you can help users make informed decisions when buying used cars, reduce fraud in automotive transactions, and build more trustworthy platforms for the Polish automotive market.
https://www.tablicarejestracyjnaapi.pl/

Romanian Vehicle Registration #API: Complete Guide to Vehicle Data Lookup in #Romania

TLDR: https://www.inmatriculareapi.ro/
Romania, as a member of the European Union since 2007, maintains a modern vehicle registration system that provides comprehensive vehicle information through digital databases. The Romanian Vehicle Registration API offers developers and businesses access to detailed vehicle specifications, ownership documents, and technical data for vehicles registered throughout Romania’s 42 counties.

Overview of Romanian Vehicle Registration System

Romania’s vehicle registration system is centralized under the Romanian National Agency for Fiscal Administration (ANAF) and the Romanian Automobile Registry (RAR). The system covers all Romanian counties from Bucharest (București) to the smallest rural regions, providing standardized vehicle identification and technical specifications.

The Romanian license plate format typically consists of:

  • County Code – 1-2 letters identifying the county of registration
  • Numbers – Sequential numerical identifier
  • Letters – Additional letter combinations

Romanian Vehicle API Features

The Romania endpoint provides comprehensive vehicle information including:

Available Data

When querying Romanian vehicle registrations, you can retrieve:

  • Make and Model – Complete manufacturer and vehicle model information
  • Registration Year – Year when the vehicle was first registered
  • Engine Specifications – Engine size in cubic centimeters and power in kilowatts
  • Fuel Type – Fuel classification (benzina/petrol, motorina/diesel, GPL/LPG, electric)
  • VIN Number – Complete 17-character Vehicle Identification Number
  • CIV Document – Vehicle Identity Document (Cartea de Identitate a Vehiculului)
  • Vehicle Type – Classification (Autoturism/passenger car, Autoutilitară/utility vehicle, etc.)
  • Technical Specifications – Weight, number of seats, variant information
  • Registration Region – County or city where the vehicle is registered
  • Representative Image – Visual identification of the vehicle type

Sample Response Format

{
  "Description": "Renault Clio",
  "RegistrationYear": "1999",
  "CarMake": {
    "CurrentTextValue": "Renault"
  },
  "CarModel": {
    "CurrentTextValue": "Clio"
  },
  "MakeDescription": {
    "CurrentTextValue": "Renault"
  },
  "ModelDescription": {
    "CurrentTextValue": "Clio"
  },
  "Type": "Autoturism",
  "VIN": "VF1CB0A0F20507251",
  "CIV": "J350228",
  "Variant": "",
  "Weight": "955",
  "FuelType": "benzina",
  "NumberOfSeats": "5",
  "Power": "43",
  "EngineSize": "1149",
  "Region": "București",
  "ImageUrl": "http://www.inmatriculareapi.ro/image.aspx/@UmVuYXVsdCBDbGlv"
}

API Implementation

Endpoint Usage

The Romanian Vehicle API uses the /CheckRomania endpoint and requires two parameters:

  1. Registration Number – The complete Romanian license plate number
  2. Username – Your API authentication credentials

Basic Implementation Example

// JavaScript example for Romanian vehicle lookup
async function lookupRomanianVehicle(registrationNumber, username) {
  const apiUrl = `https://www.inmatriculareapi.ro/api/reg.asmx/CheckRomania?RegistrationNumber=${registrationNumber}&username=${username}`;
  
  try {
    const response = await fetch(apiUrl);
    const xmlText = await response.text();
    
    // Parse XML response
    const parser = new DOMParser();
    const xmlDoc = parser.parseFromString(xmlText, "text/xml");
    const jsonData = xmlDoc.getElementsByTagName("vehicleJson")[0].textContent;
    const vehicleInfo = JSON.parse(jsonData);
    
    return {
      make: vehicleInfo.MakeDescription.CurrentTextValue,
      model: vehicleInfo.ModelDescription.CurrentTextValue,
      year: vehicleInfo.RegistrationYear,
      engineSize: vehicleInfo.EngineSize,
      power: vehicleInfo.Power,
      fuel: vehicleInfo.FuelType,
      vin: vehicleInfo.VIN,
      civ: vehicleInfo.CIV,
      region: vehicleInfo.Region,
      weight: vehicleInfo.Weight,
      seats: vehicleInfo.NumberOfSeats,
      type: vehicleInfo.Type
    };
  } catch (error) {
    console.error('Romanian vehicle lookup failed:', error);
    return null;
  }
}

// Usage example
lookupRomanianVehicle("B123ABC", "your_username")
  .then(data => {
    if (data) {
      console.log(`Vehicle: ${data.make} ${data.model} (${data.year})`);
      console.log(`Engine: ${data.engineSize}cc, ${data.power}kW`);
      console.log(`Fuel: ${data.fuel}`);
      console.log(`CIV: ${data.civ}`);
      console.log(`Region: ${data.region}`);
    }
  });

Python Implementation

import requests
import xml.etree.ElementTree as ET
import json

class RomanianVehicleAPI:
    def __init__(self, username):
        self.username = username
        self.base_url = "https://www.inmatriculareapi.ro/api/reg.asmx/CheckRomania"
    
    def validate_registration_format(self, registration):
        """Validate Romanian registration number format"""
        if not registration or len(registration.strip()) < 6:
            return False, "Registration number too short"
        
        # Remove spaces and convert to uppercase
        reg = registration.replace(" ", "").upper()
        
        # Basic format validation (letters + numbers + letters)
        if not any(c.isalpha() for c in reg) or not any(c.isdigit() for c in reg):
            return False, "Invalid format - must contain both letters and numbers"
        
        return True, reg
    
    def lookup(self, registration_number):
        """Lookup Romanian vehicle with comprehensive error handling"""
        # Validate registration format
        is_valid, processed_reg = self.validate_registration_format(registration_number)
        if not is_valid:
            return {"error": processed_reg}
        
        try:
            params = {
                'RegistrationNumber': processed_reg,
                'username': self.username
            }
            
            response = requests.get(self.base_url, params=params, timeout=15)
            response.raise_for_status()
            
            # Parse XML response
            root = ET.fromstring(response.content)
            json_element = root.find('.//vehicleJson')
            
            if json_element is None or not json_element.text:
                return {"error": "No vehicle data found for this registration number"}
            
            vehicle_data = json.loads(json_element.text)
            
            # Process and structure the response
            return {
                'success': True,
                'description': vehicle_data.get('Description'),
                'make': vehicle_data.get('MakeDescription', {}).get('CurrentTextValue'),
                'model': vehicle_data.get('ModelDescription', {}).get('CurrentTextValue'),
                'registration_year': vehicle_data.get('RegistrationYear'),
                'vehicle_type': vehicle_data.get('Type'),
                'vin': vehicle_data.get('VIN'),
                'civ': vehicle_data.get('CIV'),
                'engine_size': vehicle_data.get('EngineSize'),
                'power_kw': vehicle_data.get('Power'),
                'fuel_type': vehicle_data.get('FuelType'),
                'weight_kg': vehicle_data.get('Weight'),
                'number_of_seats': vehicle_data.get('NumberOfSeats'),
                'region': vehicle_data.get('Region'),
                'variant': vehicle_data.get('Variant'),
                'image_url': vehicle_data.get('ImageUrl'),
                'raw_data': vehicle_data
            }
            
        except requests.Timeout:
            return {"error": "Request timed out - please try again"}
        except requests.RequestException as e:
            return {"error": f"Network error: {str(e)}"}
        except ET.ParseError:
            return {"error": "Invalid response format from API"}
        except json.JSONDecodeError:
            return {"error": "Could not parse vehicle data"}
        except Exception as e:
            return {"error": f"Unexpected error: {str(e)}"}

# Usage example
api = RomanianVehicleAPI("your_username")
result = api.lookup("B123ABC")

if result.get('success'):
    print(f"Vehicle: {result['make']} {result['model']}")
    print(f"Year: {result['registration_year']}")
    print(f"Engine: {result['engine_size']}cc, {result['power_kw']}kW")
    print(f"Fuel: {result['fuel_type']}")
    print(f"VIN: {result['vin']}")
    print(f"CIV: {result['civ']}")
    print(f"Region: {result['region']}")
    print(f"Weight: {result['weight_kg']}kg")
    print(f"Seats: {result['number_of_seats']}")
else:
    print(f"Error: {result['error']}")

Romanian Vehicle Registration Format

County Codes

Romanian license plates begin with county codes that identify the registration location:

Major Cities and Counties:

  • B – București (Bucharest) – Capital city
  • AB – Alba – Alba Iulia
  • AG – Argeș – Pitești
  • AR – Arad – Arad
  • BC – Bacău – Bacău
  • BH – Bihor – Oradea
  • BN – Bistrița-Năsăud – Bistrița
  • BR – Brăila – Brăila
  • BT – Botoșani – Botoșani
  • BV – Brașov – Brașov
  • BZ – Buzău – Buzău
  • CJ – Cluj – Cluj-Napoca
  • CL – Călărași – Călărași
  • CS – Caraș-Severin – Reșița
  • CT – Constanța – Constanța
  • CV – Covasna – Sfântu Gheorghe
  • DB – Dâmbovița – Târgoviște
  • DJ – Dolj – Craiova
  • GJ – Gorj – Târgu Jiu
  • GL – Galați – Galați
  • GR – Giurgiu – Giurgiu
  • HD – Hunedoara – Deva
  • HR – Harghita – Miercurea Ciuc
  • IF – Ilfov – Buftea
  • IL – Ialomița – Slobozia
  • IS – Iași – Iași
  • MH – Mehedinți – Drobeta-Turnu Severin
  • MM – Maramureș – Baia Mare
  • MS – Mureș – Târgu Mureș
  • NT – Neamț – Piatra Neamț
  • OT – Olt – Slatina
  • PH – Prahova – Ploiești
  • SB – Sibiu – Sibiu
  • SJ – Sălaj – Zalău
  • SM – Satu Mare – Satu Mare
  • SV – Suceava – Suceava
  • TL – Tulcea – Tulcea
  • TM – Timiș – Timișoara
  • TR – Teleorman – Alexandria
  • VL – Vâlcea – Râmnicu Vâlcea
  • VN – Vrancea – Focșani
  • VS – Vaslui – Vaslui

Understanding Romanian Vehicle Data

Vehicle Types (Tip Vehicul)

  • Autoturism – Passenger car
  • Autoutilitară – Utility vehicle/van
  • Autocamion – Truck
  • Autobus/Autobuz – Bus
  • Motocicletă – Motorcycle
  • Moped – Moped
  • Remorcă – Trailer

Fuel Types (Tip Combustibil)

  • Benzină – Petrol/Gasoline
  • Motorină – Diesel
  • GPL – Liquefied Petroleum Gas
  • Electric – Electric vehicle
  • Hibrid – Hybrid (petrol/electric or diesel/electric)

CIV Document

The CIV (Cartea de Identitate a Vehiculului) is Romania’s vehicle identity document, similar to a vehicle registration certificate. It contains:

  • Vehicle technical specifications
  • Ownership history
  • Registration details
  • Environmental compliance information

Use Cases for Romanian Vehicle API

Insurance Industry

  • Policy Underwriting – Access technical specifications for risk assessment
  • Claims Processing – Verify vehicle details during accident claims
  • Fraud Prevention – Cross-reference VIN and CIV data for authenticity
  • Premium Calculation – Engine power and weight for insurance categories

Automotive Dealers

  • Vehicle History – Verify registration and technical details
  • Import/Export – VIN verification for cross-border transactions
  • Inventory Management – Automated vehicle data population
  • Trade Valuations – Technical specifications for pricing

Fleet Management

  • Asset Tracking – Maintain detailed vehicle records
  • Compliance Monitoring – Ensure registration validity across fleet
  • Maintenance Planning – Engine specifications for service schedules
  • Environmental Reporting – Fuel type and emissions data

Government and Law Enforcement

  • Vehicle Identification – Quick lookups during traffic enforcement
  • Registration Verification – Confirm vehicle legitimacy
  • Import Control – VIN verification for customs procedures
  • Investigation Support – Vehicle tracking and identification

Mobile Applications

  • Car Shopping Apps – Instant vehicle specification lookup
  • Insurance Apps – Quick vehicle verification for quotes
  • Service Apps – Technical specifications for maintenance booking
  • Parking Apps – Vehicle identification and validation

Error Handling Best Practices

function handleRomanianVehicleLookup(registration, username) {
  // Validate input format
  if (!registration || registration.length < 6) {
    return Promise.reject(new Error("Invalid registration number format"));
  }
  
  // Clean registration number
  const cleanReg = registration.replace(/\s+/g, '').toUpperCase();
  
  return lookupRomanianVehicle(cleanReg, username)
    .then(data => {
      if (!data) {
        throw new Error("No vehicle data returned");
      }
      
      // Validate essential fields
      if (!data.make || !data.model) {
        throw new Error("Incomplete vehicle data received");
      }
      
      return data;
    })
    .catch(error => {
      console.error('Romanian vehicle lookup error:', error);
      
      // Return structured error response
      return {
        error: true,
        message: error.message,
        registration: registration,
        timestamp: new Date().toISOString()
      };
    });
}

Data Privacy and Compliance

GDPR Compliance

As an EU member state, Romania follows strict data protection regulations:

  • The API returns technical vehicle specifications, not personal owner data
  • VIN and CIV numbers are vehicle identifiers, not personal information
  • Consider data retention policies when caching API responses
  • Implement proper access controls for vehicle data systems

Usage Limitations

  • API is intended for legitimate business purposes
  • Vehicle data should not be used for unauthorized tracking
  • Respect rate limits and terms of service
  • Implement proper error handling to avoid excessive requests

Getting Started

Account Setup

  1. Register for API access at the Romanian vehicle API portal
  2. Verify your email address and business credentials
  3. Test with sample registration numbers like “B123ABC”
  4. Purchase credits for production usage

Integration Testing

Test with various Romanian registration formats:

  • Bucharest format: B123ABC, B456DEF
  • County formats: CJ12ABC, TM34DEF, CT56GHI
  • Different vehicle types to understand data variations

Production Considerations

  • Implement robust error handling for network issues
  • Cache responses appropriately to reduce API calls
  • Monitor API usage and credit consumption
  • Plan for data updates and system maintenance windows

Conclusion

The Romanian Vehicle Registration API provides comprehensive access to vehicle data across all Romanian counties and cities. With detailed technical specifications, official document references (CIV), and standardized data formats, the API supports diverse applications from insurance processing to fleet management.

Romania’s centralized registration system ensures consistent data quality while the API’s detailed response format provides all necessary vehicle information for professional applications. Understanding Romanian vehicle types, fuel classifications, and regional codes enhances the effectiveness of API integration.

The system’s compliance with EU data protection standards and focus on technical specifications rather than personal data makes it suitable for business applications requiring vehicle verification and specification lookup.

Start integrating Romanian vehicle data today by registering for API access and exploring the comprehensive database of Romanian vehicle registrations.

Please visit https://www.inmatriculareapi.ro/ to get started.

How to Open .pkpasses Files on Your iPhone: The Hidden Multi-Pass Secret #PKPASSES

If you’ve ever booked multiple tickets with airlines like EasyJet, you might have encountered a mysterious file type: .pkpasses. Unlike the familiar .pkpass files that open seamlessly in Apple Wallet, these multi-pass bundles can leave you scratching your head when they won’t open directly on your iPhone.

Don’t worry – there’s a simple workaround that airlines don’t always explain clearly. Here’s everything you need to know about .pkpasses files and how to get your boarding passes into Apple Wallet where they belong.

What Are .pkpasses Files?

A .pkpasses file is essentially a container that holds multiple .pkpass files bundled together. When you book multiple flights or tickets in a single transaction, airlines like EasyJet use this format to deliver all your passes at once, rather than sending separate emails for each boarding pass.

Think of it as a digital envelope containing multiple boarding passes – convenient for the airline’s system, but not immediately compatible with your iPhone’s Wallet app, which expects individual .pkpass files.

The Problem: Why Won’t My .pkpasses File Open?

When you try to open a .pkpasses file directly on your iPhone, you’ll likely encounter one of these frustrating scenarios:

  • The file downloads but nothing happens when you tap it
  • You get an error message saying the file can’t be opened
  • The Wallet app doesn’t recognize or import the passes

This happens because Apple Wallet is designed to handle individual .pkpass files, not the bundled .pkpasses format.

The Solution: Extract Individual Passes

Here’s the step-by-step process to extract your individual boarding passes from a .pkpasses file:

Step 1: Rename the File Extension

The key insight is that .pkpasses files are actually ZIP archives in disguise. To access the individual passes inside:

  1. Save the .pkpasses file to your device (usually through email or download)
  2. Rename the file extension from .pkpasses to .zip
  3. You can do this using the Files app on iOS, or more easily on a computer

Step 2: Unzip the Archive

Once renamed to .zip, you can extract the contents:

  • On iPhone/iPad: Use the Files app to tap the ZIP file and it will automatically extract
  • On Mac/PC: Double-click the ZIP file or use your preferred extraction tool

Step 3: Find Your Individual .pkpass Files

Inside the extracted folder, you’ll discover multiple .pkpass files – one for each boarding pass or ticket in your booking. These files will typically be named with flight numbers, dates, or passenger names.

Step 4: Email the Passes to Yourself

This is where the magic happens:

  1. Select each .pkpass file individually
  2. Email them to yourself (or use AirDrop if working on a Mac)
  3. Open the email on your iPhone
  4. Tap each .pkpass attachment
  5. Each pass will now open properly in Apple Wallet

Why This Method Works

By extracting and emailing the individual .pkpass files, you’re essentially doing what the airline’s system should have done in the first place – delivering each pass in a format that Apple Wallet can recognize and import.

The email step is crucial because it triggers iOS to properly recognize the MIME type and offer to open the file in Wallet. Simply copying the extracted .pkpass files to your phone via other methods might not work as reliably.

Pro Tips for Managing Multiple Passes

  • Organize by trip: Create separate emails for outbound and return flights
  • Check all details: Verify that each extracted pass contains the correct passenger and flight information
  • Keep the original: Save the original .pkpasses file as a backup
  • Test early: Don’t wait until you’re at the airport to discover pass issues

Alternative Solutions

If the manual extraction method seems too technical, consider these alternatives:

  • Contact the airline: Many airlines can resend individual .pkpass files if you explain the issue
  • Use airline apps: Download the airline’s official app, which often provides wallet-compatible passes
  • Third-party tools: Some online services can convert .pkpasses to individual passes, though be cautious about uploading sensitive travel documents

When You Might Encounter .pkpasses Files

This file format is most commonly used by:

  • Budget airlines like EasyJet for multi-leg bookings
  • Travel booking platforms managing multiple tickets
  • Event organizers selling group or family ticket bundles
  • Transit authorities for multi-ride passes

Conclusion

While .pkpasses files might seem like an unnecessary complication, understanding how to handle them ensures you’re never stuck without access to your boarding passes. The rename-to-ZIP trick is a simple but powerful solution that turns a frustrating file format issue into a minor inconvenience.

Next time you receive a .pkpasses file, you’ll know exactly what to do: rename it to .zip, extract the individual passes, and email them to yourself. Your future self at the airport will thank you for taking these few extra minutes to ensure your passes are properly loaded in Apple Wallet.

Remember, technology should make travel easier, not harder – and now you have the knowledge to make sure it does.

USA Vehicle Registration API: Complete Guide to American VIN and License Plate Lookups

The United States represents one of the largest automotive markets in the world, with over 270 million registered vehicles across all 50 states. For developers and businesses working with American vehicle data, the USA Vehicle Registration API provides instant access to comprehensive vehicle information using license plate numbers and state codes. See here: https://www.vehicleregistrationapi.com/

Overview of USA Vehicle Registration System

Unlike many countries that have centralized vehicle registration systems, the United States operates on a state-by-state basis. Each of the 50 states, plus Washington D.C., Puerto Rico, Guam, and the Virgin Islands, maintains its own vehicle registration database. This decentralized approach means that vehicle lookups require both the license plate number and the state where the vehicle is registered.

USA Vehicle API Features

The USA endpoint provides access to vehicle information across all American jurisdictions, including:

Supported Jurisdictions

  • All 50 States – From Alabama to Wyoming
  • Federal District – Washington D.C. (DC)
  • Territories – Puerto Rico (PR), Guam (GU), Virgin Islands (VI)

Data Available

When querying American vehicle registrations, you can retrieve:

  • Vehicle Description – Complete make, model, and year information
  • Body Style – Vehicle type classification (sedan, SUV, pickup truck, etc.)
  • VIN Number – Complete 17-character Vehicle Identification Number
  • Engine Specifications – Engine size and configuration details
  • Country of Assembly – Where the vehicle was manufactured
  • Registration Year – Year the vehicle was first registered

API Implementation

Endpoint Usage

The USA Vehicle Registration API uses the /CheckUSA endpoint and requires two parameters:

  1. License Plate Number – The registration number (without spaces or special characters)
  2. State Code – Two-letter abbreviation for the state of registration

State Codes Reference

The API accepts standard two-letter state abbreviations:

States A-M:

  • AL (Alabama), AK (Alaska), AZ (Arizona), AR (Arkansas)
  • CA (California), CO (Colorado), CT (Connecticut), DE (Delaware)
  • FL (Florida), GA (Georgia), HI (Hawaii), ID (Idaho)
  • IL (Illinois), IN (Indiana), IA (Iowa), KS (Kansas)
  • KY (Kentucky), LA (Louisiana), ME (Maine), MD (Maryland)
  • MA (Massachusetts), MI (Michigan), MN (Minnesota), MS (Mississippi), MO (Missouri), MT (Montana)

States N-W:

  • NE (Nebraska), NV (Nevada), NH (New Hampshire), NJ (New Jersey)
  • NM (New Mexico), NY (New York), NC (North Carolina), ND (North Dakota)
  • OH (Ohio), OK (Oklahoma), OR (Oregon), PA (Pennsylvania)
  • RI (Rhode Island), SC (South Carolina), SD (South Dakota), TN (Tennessee)
  • TX (Texas), UT (Utah), VT (Vermont), VA (Virginia)
  • WA (Washington), WV (West Virginia), WI (Wisconsin), WY (Wyoming)

Federal & Territories:

  • DC (District of Columbia), GU (Guam), PR (Puerto Rico), VI (Virgin Islands)

Sample Implementation

Basic API Call Example

// JavaScript example for USA vehicle lookup
const username = 'your_api_username';
const plateNumber = 'ABC1234';
const state = 'CA'; // California

const apiUrl = `https://www.regcheck.org.uk/api/reg.asmx/CheckUSA?RegistrationNumber=${plateNumber}&State=${state}&username=${username}`;

fetch(apiUrl)
  .then(response => response.text())
  .then(data => {
    // Parse XML response
    const parser = new DOMParser();
    const xmlDoc = parser.parseFromString(data, "text/xml");
    const jsonData = xmlDoc.getElementsByTagName("vehicleJson")[0].textContent;
    const vehicleInfo = JSON.parse(jsonData);
    
    console.log("Vehicle:", vehicleInfo.Description);
    console.log("VIN:", vehicleInfo.VechileIdentificationNumber);
    console.log("Body Style:", vehicleInfo.BodyStyle.CurrentTextValue);
  })
  .catch(error => console.error('Error:', error));

Response Format

The API returns data in both XML and JSON formats. Here’s a sample response for a 2004 Dodge Durango:

{
  "Description": "2004 Dodge Durango Limited",
  "BodyStyle": {
    "CurrentTextValue": "SUV 4D"
  },
  "VechileIdentificationNumber": "1D8HB58D04F177301",
  "Assembly": "United States",
  "EngineSize": {
    "CurrentTextValue": "5.7L V8 MPI"
  },
  "RegistrationYear": "2004",
  "CarMake": {
    "CurrentTextValue": "Dodge"
  },
  "CarModel": {
    "CurrentTextValue": "Durango Limited"
  },
  "MakeDescription": {
    "CurrentTextValue": "Dodge"
  },
  "ModelDescription": {
    "CurrentTextValue": "Durango Limited"
  }
}

State-Specific Considerations

California (CA)

California has one of the most comprehensive vehicle databases in the US, with detailed information available for most vehicles. The state’s emissions requirements mean additional environmental data may be available.

Texas (TX)

As the second-largest state by population and vehicle registrations, Texas maintains extensive records. The state’s diverse automotive market includes everything from pickup trucks to luxury vehicles.

Florida (FL)

Florida’s high volume of vehicle imports and exports, combined with its large retiree population, creates a unique mix of vehicle types and registration patterns.

New York (NY)

New York’s database includes both upstate rural vehicles and New York City urban registrations, providing a diverse dataset for vehicle information.

Use Cases for USA Vehicle API

Insurance Industry Applications

  • Policy Underwriting – Verify vehicle specifications for accurate premium calculations
  • Claims Processing – Validate vehicle information during accident claims
  • Fraud Prevention – Cross-reference vehicle details to detect inconsistencies

Automotive Dealers

  • Inventory Management – Automatically populate vehicle listings with accurate specifications
  • Trade-In Valuations – Verify vehicle details for pricing assessments
  • Sales Documentation – Ensure accurate vehicle information on sales contracts

Fleet Management

  • Asset Tracking – Maintain detailed records of company vehicle fleets
  • Compliance Monitoring – Verify vehicle specifications for regulatory compliance
  • Maintenance Scheduling – Access manufacturer specifications for service intervals

Law Enforcement

  • Vehicle Identification – Quick lookup for traffic stops and investigations
  • Asset Recovery – Verify vehicle ownership and specifications
  • Investigation Support – Cross-reference vehicle data in criminal cases

Mobile Applications

  • Car Shopping Apps – Instant vehicle specification lookup for used car buyers
  • Maintenance Apps – Access vehicle specs for service reminders and parts ordering
  • Insurance Apps – Quick vehicle verification for policy quotes

Integration Best Practices

Error Handling

Always implement robust error handling when working with the USA API:

import requests
import xml.etree.ElementTree as ET
import json

def lookup_usa_vehicle(plate_number, state, username):
    try:
        url = f"https://www.regcheck.org.uk/api/reg.asmx/CheckUSA"
        params = {
            'RegistrationNumber': plate_number,
            'State': state,
            'username': username
        }
        
        response = requests.get(url, params=params)
        response.raise_for_status()
        
        # Parse XML response
        root = ET.fromstring(response.content)
        json_data = root.find('.//vehicleJson').text
        
        if json_data:
            vehicle_data = json.loads(json_data)
            return vehicle_data
        else:
            return {"error": "No vehicle data found"}
            
    except requests.RequestException as e:
        return {"error": f"API request failed: {str(e)}"}
    except ET.ParseError as e:
        return {"error": f"XML parsing failed: {str(e)}"}
    except json.JSONDecodeError as e:
        return {"error": f"JSON parsing failed: {str(e)}"}

# Usage example
result = lookup_usa_vehicle("ABC1234", "CA", "your_username")
print(result)

Rate Limiting and Credits

The USA Vehicle API operates on a credit-based system:

  • Each successful lookup consumes one credit
  • Failed lookups (no data found) typically don’t consume credits
  • Monitor your credit balance to avoid service interruptions
  • Consider implementing local caching for frequently accessed data

Data Validation

Before making API calls, validate input parameters:

function validateUSALookup(plateNumber, state) {
  // Valid US state codes
  const validStates = [
    'AL', 'AK', 'AZ', 'AR', 'CA', 'CO', 'CT', 'DE', 'FL', 'GA',
    'HI', 'ID', 'IL', 'IN', 'IA', 'KS', 'KY', 'LA', 'ME', 'MD',
    'MA', 'MI', 'MN', 'MS', 'MO', 'MT', 'NE', 'NV', 'NH', 'NJ',
    'NM', 'NY', 'NC', 'ND', 'OH', 'OK', 'OR', 'PA', 'RI', 'SC',
    'SD', 'TN', 'TX', 'UT', 'VT', 'VA', 'WA', 'WV', 'WI', 'WY',
    'DC', 'GU', 'PR', 'VI'
  ];
  
  if (!plateNumber || plateNumber.length < 2 || plateNumber.length > 8) {
    return { valid: false, error: "Invalid plate number length" };
  }
  
  if (!validStates.includes(state.toUpperCase())) {
    return { valid: false, error: "Invalid state code" };
  }
  
  return { valid: true };
}

Limitations and Coverage

Data Availability

  • Coverage varies by state based on data sharing agreements
  • Some states may have limited historical data
  • Newer registrations typically have more complete information
  • Commercial vehicles may have different data availability

Privacy Considerations

  • The API provides vehicle specifications, not personal owner information
  • All data returned is from publicly available vehicle registration records
  • Comply with local privacy laws when storing or processing vehicle data
  • Consider data retention policies for cached information

Getting Started

Account Setup

  1. Create Account – Register at regcheck.org.uk for API access
  2. Email Verification – Confirm your email to receive free test credits
  3. Test the Service – Use provided sample license plates for testing
  4. Purchase Credits – Buy additional credits for production use

Testing with Sample Data

Use this sample license plate for testing: ZZZ9999 with state NC (North Carolina)

This will return information about a 2004 Dodge Durango Limited without consuming your credits.

Pricing and Support

Credit Costs

  • Standard rate: 1 credit per successful vehicle lookup
  • Volume discounts available for high-usage applications
  • Failed lookups typically don’t consume credits

Technical Support

  • API documentation available at regcheck.org.uk
  • Email support for technical integration questions
  • WSDL definition available for SOAP implementations

Conclusion

The USA Vehicle Registration API provides comprehensive access to American vehicle data across all 50 states and territories. With proper implementation and error handling, developers can integrate reliable vehicle lookup functionality into their applications, supporting use cases from insurance processing to mobile app development.

The decentralized nature of American vehicle registration creates unique challenges, but the API abstracts this complexity, providing a single endpoint for nationwide vehicle data access. Whether you’re building consumer applications or enterprise solutions, the USA Vehicle Registration API offers the reliability and coverage needed for professional vehicle data integration.

Ready to start integrating American vehicle data into your application? Sign up for your free API account today and begin exploring the extensive database of US vehicle registrations.

Categories: Uncategorized Tags: , ,

Complete Guide to the UK Vehicle Registration #API: Access #DVLA Data, #MOT History, and More

Are you developing an application that needs instant access to UK vehicle information? The UK Vehicle Registration API provides comprehensive access to DVLA data, MOT history, tax information, and vehicle specifications through a simple integration. This powerful tool allows developers to retrieve detailed vehicle information using just a Vehicle Registration Mark (VRM). Here: https://regcheck.org.uk/

What is the UK Vehicle Registration API?

The UK Vehicle Registration API is a SOAP-based web service that provides instant access to official UK vehicle data. By simply entering a vehicle registration number (VRM), you can retrieve comprehensive information about cars, motorcycles, and commercial vehicles registered with the DVLA.

Key Features:

  • Instant VRM lookups for all UK-registered vehicles
  • Complete MOT history with test results and failure reasons
  • Tax status information including expiry dates
  • Comprehensive vehicle specifications including make, model, engine details
  • Support for special territories including Isle of Man and Jersey
  • Both XML and JSON response formats

UK Vehicle Data Available

Standard Vehicle Information

When you query the UK endpoint using a vehicle registration number, you’ll receive:

  • Make and Model – Manufacturer and specific vehicle model
  • Year of Registration – When the vehicle was first registered
  • VIN Number – Complete Vehicle Identification Number
  • ABI Code – Association of British Insurers classification code
  • Body Style – Vehicle type (saloon, hatchback, SUV, etc.)
  • Engine Size – Displacement in cubic centimeters
  • Number of Doors – Vehicle door configuration
  • Transmission Type – Manual or automatic
  • Fuel Type – Petrol, diesel, electric, hybrid
  • Immobiliser Status – Security system information
  • Number of Seats – Seating capacity
  • Driver Side – Left or right-hand drive
  • Vehicle Color – Primary exterior color

Example Response for UK Vehicle Data

{
  "ABICode": "32130768",
  "Description": "MERCEDES-BENZ E220 SE CDI",
  "RegistrationYear": "2013",
  "CarMake": {
    "CurrentTextValue": "MERCEDES-BENZ"
  },
  "CarModel": {
    "CurrentTextValue": "E220 SE CDI"
  },
  "EngineSize": {
    "CurrentTextValue": "2143"
  },
  "FuelType": {
    "CurrentTextValue": "Diesel"
  },
  "Transmission": {
    "CurrentTextValue": "Automatic"
  },
  "NumberOfDoors": {
    "CurrentTextValue": "4DR"
  },
  "BodyStyle": {
    "CurrentTextValue": "Saloon"
  },
  "Colour": "WHITE",
  "VehicleIdentificationNumber": "WDD2120022A899877"
}

MOT History API – Complete Test Records

One of the most valuable features of the UK Vehicle API is access to complete MOT history data. This service covers all UK cars (excluding Northern Ireland) and provides detailed test information including:

MOT Data Includes:

  • Test Date – When each MOT was conducted
  • Test Result – Pass or Fail status
  • Odometer Reading – Mileage at time of test
  • Test Number – Official MOT test reference
  • Failure Reasons – Detailed list of any failures
  • Advisory Notes – Items that need attention
  • Expiry Date – When the MOT certificate expires

MOT History Response Example

[
  {
    "TestDate": "8 November 2016",
    "ExpiryDate": "16 November 2017",
    "Result": "Pass",
    "Odometer": "61,706 miles",
    "TestNumber": "2754 6884 4000",
    "FailureReasons": [],
    "Advisories": []
  },
  {
    "TestDate": "8 November 2016",
    "Result": "Fail",
    "Odometer": "61,703 miles",
    "TestNumber": "5901 3690 4542",
    "FailureReasons": [
      "Nearside Rear Brake pipe excessively corroded (3.6.B.2c)",
      "Offside Rear Brake pipe excessively corroded (3.6.B.2c)"
    ],
    "Advisories": []
  }
]

Extended Vehicle Information with Tax Data

The API also provides enhanced vehicle information including tax and emissions data:

  • Make and Registration Date
  • Year of Manufacture
  • CO2 Emissions – Environmental impact rating
  • Tax Status – Current road tax status
  • Tax Due Date – When road tax expires
  • Vehicle Type Approval – EU approval classification
  • Wheelplan – Axle configuration
  • Weight Information – Gross vehicle weight

UK Motorcycle Support

For motorcycles registered in the UK, use the dedicated CheckMotorBikeUK endpoint. This returns motorcycle-specific information:

  • Make and Model – Manufacturer and bike model
  • Year of Registration
  • Engine Size – Engine displacement
  • Variant – Specific model variant
  • Colour – Primary color
  • VIN – Complete chassis number
  • Engine Number – Engine identification

Motorcycle Response Example

{
  "Description": "HONDA ST1300 A",
  "RegistrationYear": "2005",
  "CarMake": {
    "CurrentTextValue": "HONDA"
  },
  "CarModel": {
    "CurrentTextValue": "ST1300 A"
  },
  "EngineSize": {
    "CurrentTextValue": "1261"
  },
  "BodyStyle": {
    "CurrentTextValue": "Motorbike"
  },
  "FuelType": {
    "CurrentTextValue": "PETROL"
  },
  "Colour": "YELLOW",
  "VehicleIdentificationNumber": "JH2SC51A92M007472"
}

Isle of Man Vehicle Support

Vehicles registered in the Isle of Man (identified by “MN”, “MAN”, or “MANX” in the registration) return enhanced data including:

  • Standard vehicle information (make, model, engine size)
  • Version details – Specific trim level
  • CO2 emissions – Environmental data
  • Tax status – “Active” or expired
  • Tax expiry date – When road tax is due
  • Wheelplan – Vehicle configuration

Isle of Man Response Example

{
  "Description": "HONDA JAZZ",
  "RegistrationYear": 2012,
  "CarMake": {
    "CurrentTextValue": "HONDA"
  },
  "Version": "I-VTEC ES",
  "Colour": "SILVER",
  "Co2": "126",
  "RegistrationDate": "06/07/2012",
  "WheelPlan": "2-AXLE Rigid",
  "Taxed": "Active",
  "TaxExpiry": "31/07/2018"
}

Integration and Implementation

API Endpoint

The service is available at: https://www.regcheck.org.uk/api/reg.asmx

WSDL Definition

Access the service definition at: https://www.regcheck.org.uk/api/reg.asmx?wsdl

Authentication

All API calls require a valid username. You can obtain a test account with 10 free credits after email verification.

Sample Implementation (PHP)

<?php
$username = 'Your_Username_Here';
$regNumber = 'AB12CDE';

$xmlData = file_get_contents("https://www.regcheck.org.uk/api/reg.asmx/Check?RegistrationNumber=" . $regNumber . "&username=" . $username);

$xml = simplexml_load_string($xmlData);
$strJson = $xml->vehicleJson;
$json = json_decode($strJson);

echo "Vehicle: " . $json->Description;
echo "Year: " . $json->RegistrationYear;
echo "Fuel: " . $json->FuelType->CurrentTextValue;
?>

Use Cases for UK Vehicle API

For Businesses:

  • Insurance Companies – Instant vehicle verification and risk assessment
  • Car Dealers – Vehicle history checks and specifications
  • Fleet Management – MOT tracking and compliance monitoring
  • Automotive Marketplaces – Automated vehicle data population
  • Garage Services – Customer vehicle information lookup

For Developers:

  • Mobile Apps – Vehicle checking applications
  • Web Platforms – Integrated vehicle lookup features
  • Compliance Tools – MOT and tax reminder systems
  • Data Validation – Verify vehicle registration details

Benefits of Using the UK Vehicle Registration API

  1. Official DVLA Data – Access to authoritative government vehicle records
  2. Real-time Information – Instant access to current vehicle status
  3. Comprehensive Coverage – Supports cars, motorcycles, and commercial vehicles
  4. Historical Data – Complete MOT history with detailed records
  5. Multiple Formats – Both XML and JSON response options
  6. Reliable Service – High uptime and consistent performance
  7. Cost Effective – Credit-based pricing with free test options

Getting Started

To begin using the UK Vehicle Registration API:

  1. Sign up for a free test account at regcheck.org.uk
  2. Verify your email address to receive 10 free credits
  3. Test the API with sample vehicle registration numbers
  4. Purchase additional credits as needed for production use
  5. Implement the API in your application using provided documentation

Security and Compliance

The API includes several security features:

  • IP Address Restrictions – Lock access to specific IP addresses
  • Credit Monitoring – Balance alerts and daily usage limits
  • Secure Connections – HTTPS encryption for all API calls
  • Data Protection – Compliance with UK data protection regulations

Conclusion

The UK Vehicle Registration API provides developers and businesses with comprehensive access to official DVLA data, MOT records, and vehicle specifications. Whether you’re building a consumer app for vehicle checks or integrating vehicle data into business systems, this API offers the reliability and data coverage needed for professional applications.

With support for standard UK vehicles, motorcycles, and special territories like the Isle of Man, plus detailed MOT history and tax information, the UK Vehicle Registration API is the most complete solution for accessing UK vehicle data programmatically.

Ready to get started? Visit the RegCheck website to create your free account and begin exploring UK vehicle data today.

Porting a PHP OAuth Spotler Client to C#: Lessons Learned

Recently I had to integrate with Spotler’s REST API from a .NET application. Spotler provides a powerful marketing automation platform, and their API uses OAuth 1.0 HMAC-SHA1 signatures for authentication.

They provided a working PHP client, but I needed to port this to C#. Here’s what I learned (and how you can avoid some common pitfalls).


🚀 The Goal

We started with a PHP class that:

✅ Initializes with:

  • consumerKey
  • consumerSecret
  • optional SSL certificate verification

✅ Creates properly signed OAuth 1.0 requests

✅ Makes HTTP requests with cURL and parses the JSON responses.

I needed to replicate this in C# so we could use it inside a modern .NET microservice.


🛠 The Port to C#

🔑 The tricky part: OAuth 1.0 signatures

Spotler’s API requires a specific signature format. It’s critical to:

  1. Build the signature base string by concatenating:
    • The uppercase HTTP method (e.g., GET),
    • The URL-encoded endpoint,
    • And the URL-encoded, sorted OAuth parameters.
  2. Sign it using HMAC-SHA1 with the consumerSecret followed by &.
  3. Base64 encode the HMAC hash.

This looks simple on paper, but tiny differences in escaping or parameter order will cause 401 Unauthorized.

💻 The final C# solution

We used HttpClient for HTTP requests, and HMACSHA1 from System.Security.Cryptography for signatures. Here’s what our C# SpotlerClient does:

✅ Generates the OAuth parameters (consumer_key, nonce, timestamp, etc).
✅ Creates the exact signature base string, matching the PHP implementation character-for-character.
✅ Computes the HMAC-SHA1 signature and Base64 encodes it.
✅ Builds the Authorization header.
✅ Sends the HTTP request, with JSON bodies if needed.

We also added better exception handling: if the API returns an error (like 401), we throw an exception that includes the full response body. This made debugging much faster.


🐛 Debugging tips for OAuth 1.0

  1. Print the signature base string.
    It needs to match exactly what Spotler expects. Any stray spaces or wrong escaping will fail.
  2. Double-check timestamp and nonce generation.
    OAuth requires these to prevent replay attacks.
  3. Compare with the PHP implementation.
    We literally copied the signature generation line-by-line from PHP into C#, carefully mapping rawurlencode to Uri.EscapeDataString.
  4. Turn off SSL validation carefully.
    During development, you might disable certificate checks (ServerCertificateCustomValidationCallback), but never do this in production.

using System.Security.Cryptography;
using System.Text;

namespace SpotlerClient
{
 
    public class SpotlerClient
    {
        private readonly string _consumerKey;
        private readonly string _consumerSecret;
        private readonly string _baseUrl = "https://restapi.mailplus.nl";
        private readonly HttpClient _httpClient;

        public SpotlerClient(string consumerKey, string consumerSecret, bool verifyCertificate = true)
        {
            _consumerKey = consumerKey;
            _consumerSecret = consumerSecret;

            var handler = new HttpClientHandler();
            if (!verifyCertificate)
            {
                handler.ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => true;
            }

            _httpClient = new HttpClient(handler);
        }

        public async Task<string> ExecuteAsync(string endpoint, HttpMethod method, string jsonData = null)
        {
            var request = new HttpRequestMessage(method, $"{_baseUrl}/{endpoint}");
            var authHeader = CreateAuthorizationHeader(method.Method, endpoint);
            request.Headers.Add("Accept", "application/json");
            request.Headers.Add("Authorization", authHeader);

            if (jsonData != null)
            {
                request.Content = new StringContent(jsonData, Encoding.UTF8, "application/json");
            }

            var response = await _httpClient.SendAsync(request);

            if (!response.IsSuccessStatusCode)
            {
                var body = await response.Content.ReadAsStringAsync();
                return body;
            }

            return await response.Content.ReadAsStringAsync();
        }

        private string CreateAuthorizationHeader(string httpMethod, string endpoint)
        {
            var timestamp = DateTimeOffset.UtcNow.ToUnixTimeSeconds().ToString();
            var nonce = Guid.NewGuid().ToString("N");

            var paramString = "oauth_consumer_key=" + Uri.EscapeDataString(_consumerKey) +
                              "&oauth_nonce=" + Uri.EscapeDataString(nonce) +
                              "&oauth_signature_method=" + Uri.EscapeDataString("HMAC-SHA1") +
                              "&oauth_timestamp=" + Uri.EscapeDataString(timestamp) +
                              "&oauth_version=" + Uri.EscapeDataString("1.0");

            var sigBase = httpMethod.ToUpper() + "&" +
                          Uri.EscapeDataString(_baseUrl + "/" + endpoint) + "&" +
                          Uri.EscapeDataString(paramString);

            var sigKey = _consumerSecret + "&";

            var signature = ComputeHmacSha1Signature(sigBase, sigKey);

            var authHeader = $"OAuth oauth_consumer_key=\"{_consumerKey}\", " +
                             $"oauth_nonce=\"{nonce}\", " +
                             $"oauth_signature_method=\"HMAC-SHA1\", " +
                             $"oauth_timestamp=\"{timestamp}\", " +
                             $"oauth_version=\"1.0\", " +
                             $"oauth_signature=\"{Uri.EscapeDataString(signature)}\"";

            return authHeader;
        }

        private string ComputeHmacSha1Signature(string data, string key)
        {
            using var hmac = new HMACSHA1(Encoding.UTF8.GetBytes(key));
            var hash = hmac.ComputeHash(Encoding.UTF8.GetBytes(data));
            return Convert.ToBase64String(hash);
        }
    }
}

✅ The payoff

Once the signature was constructed precisely, authentication errors disappeared. We could now use the Spotler REST API seamlessly from C#, including:

  • importing contact lists,
  • starting campaigns,
  • and fetching campaign metrics.

📚 Sample usage

var client = new SpotlerClient(_consumerKey, _consumerSecret, false);
var endpoint = "integrationservice/contact/email@gmail.com";
var json = client.ExecuteAsync(endpoint, HttpMethod.Get).GetAwaiter().GetResult();

🎉 Conclusion

Porting from PHP to C# isn’t always as direct as it looks — especially when it comes to cryptographic signatures. But with careful attention to detail and lots of testing, we managed to build a robust, reusable client.

If you’re facing a similar integration, feel free to reach out or clone this approach. Happy coding!

Categories: Uncategorized Tags: , , , ,

🚫 Why AWS SDK for S3 No Longer Works Smoothly with .NET Framework 4.8 — and How to Fix It

In 2024, more .NET developers are finding themselves in a strange situation: suddenly, tried-and-tested .NET Framework 4.8 applications that interact with Amazon S3 start throwing cryptic build errors or runtime exceptions. The culprit? The AWS SDK for .NET has increasingly shifted toward support for .NET Core / .NET 6+, and full compatibility with .NET Framework is eroding.

In this post, we’ll explain:

  • Why this happens
  • What errors you might see
  • And how to remove the AWS SDK altogether and replace it with pure .NET 4.8-compatible code for downloading (and uploading) files from S3 using Signature Version 4.

🧨 The Problem: AWS SDK & .NET Framework 4.8

The AWS SDK for .NET (like AWSSDK.S3) now depends on modern libraries like:

  • System.Text.Json
  • System.Buffers
  • System.Runtime.CompilerServices.Unsafe
  • Microsoft.Bcl.AsyncInterfaces

These dependencies were designed for .NET Core and later versions — not .NET Framework. While it was once possible to work around this with binding redirects and careful version pinning, the situation has become unstable and error-prone.


❗ Common Symptoms

You may see errors like:

Could not load file or assembly ‘System.Text.Json, Version=6.0.0.11’

Or:

Could not load file or assembly ‘System.Buffers, Version=4.0.5.0’

Or during build:

Warning: Unable to update auto-refresh reference ‘system.text.json.dll’

Even if you install the correct packages, you may end up needing to fight bindingRedirect hell, and still not get a working application.


✅ The Solution: Remove the AWS SDK

Fortunately, you don’t need the SDK to use S3. All AWS S3 requires is a properly signed HTTP request using AWS Signature Version 4, and you can create that yourself using standard .NET 4.8 libraries.


🔐 Downloading from S3 Without the AWS SDK

Here’s how you can download a file from S3 using HttpWebRequest and Signature Version 4.

✔️ The Key Points:

  • You must include the x-amz-content-sha256 header (even for GETs!)
  • You sign the request using your AWS secret key
  • No external packages required — works on plain .NET 4.8

🧩 Code Snippet


public static byte[] DownloadFromS3(string bucketName, string objectKey, string region, string accessKey, string secretKey)
{
var method = "GET";
var service = "s3";
var host = $"{bucketName}.s3.{region}.amazonaws.com";
var uri = $"https://{host}/{objectKey}";
var requestDate = DateTime.UtcNow;
var amzDate = requestDate.ToString("yyyyMMddTHHmmssZ");
var dateStamp = requestDate.ToString("yyyyMMdd");
var canonicalUri = "/" + objectKey;
var signedHeaders = "host;x-amz-content-sha256;x-amz-date";
var payloadHash = HashSHA256(string.Empty); // Required even for GET

var canonicalRequest = $"{method}\n{canonicalUri}\n\nhost:{host}\nx-amz-content-sha256:{payloadHash}\nx-amz-date:{amzDate}\n\n{signedHeaders}\n{payloadHash}";
var credentialScope = $"{dateStamp}/{region}/{service}/aws4_request";
var stringToSign = $"AWS4-HMAC-SHA256\n{amzDate}\n{credentialScope}\n{HashSHA256(canonicalRequest)}";

var signingKey = GetSignatureKey(secretKey, dateStamp, region, service);
var signature = ToHexString(HmacSHA256(signingKey, stringToSign));

var authorizationHeader = $"AWS4-HMAC-SHA256 Credential={accessKey}/{credentialScope}, SignedHeaders={signedHeaders}, Signature={signature}";

var request = (HttpWebRequest)WebRequest.Create(uri);
request.Method = method;
request.Headers["Authorization"] = authorizationHeader;
request.Headers["x-amz-date"] = amzDate;
request.Headers["x-amz-content-sha256"] = payloadHash;

try
{
    using (var response = (HttpWebResponse)request.GetResponse())
    using (var responseStream = response.GetResponseStream())
    using (var memoryStream = new MemoryStream())
    {
        responseStream.CopyTo(memoryStream);
        return memoryStream.ToArray();
    }
}
catch (WebException ex)
{
    using (var errorResponse = (HttpWebResponse)ex.Response)
    using (var reader = new StreamReader(errorResponse.GetResponseStream()))
    {
        var errorText = reader.ReadToEnd();
        throw new Exception($"S3 request failed: {errorText}", ex);
    }
}

}
🔧 Supporting Methods


private static string HashSHA256(string text)
{
using (var sha256 = SHA256.Create())
{
return ToHexString(sha256.ComputeHash(Encoding.UTF8.GetBytes(text)));
}
}
private static byte[] HmacSHA256(byte[] key, string data)
{
using (var hmac = new HMACSHA256(key))
{
return hmac.ComputeHash(Encoding.UTF8.GetBytes(data));
}
}
private static byte[] GetSignatureKey(string secretKey, string dateStamp, string region, string service)
{
var kSecret = Encoding.UTF8.GetBytes("AWS4" + secretKey);
var kDate = HmacSHA256(kSecret, dateStamp);
var kRegion = HmacSHA256(kDate, region);
var kService = HmacSHA256(kRegion, service);
return HmacSHA256(kService, "aws4_request");
}
private static string ToHexString(byte[] bytes)
{
return BitConverter.ToString(bytes).Replace("-", "").ToLowerInvariant();
}


📝 Uploading to S3 Without the AWS SDK
You can extend the same technique for PUT requests. The only differences are:

You calculate the SHA-256 hash of the file content

You include a Content-Type and Content-Length header

You use PUT instead of GET

Let me know in the comments if you’d like the full upload version — it follows the same Signature V4 pattern.

✅ Summary
Feature AWS SDK for .NET Manual Signature V4
.NET Framework 4.8 support ❌ Increasingly broken ✅ Fully supported
Heavy NuGet dependencies ✅ ❌ Minimal
Simple download/upload ✅ ✅ (with more code)
Presigned URLs ✅ 🟡 Manual support

Final Thoughts
If you’re stuck on .NET Framework 4.8 and running into weird AWS SDK issues — you’re not alone. But you’re not stuck either. Dropping the SDK and using HTTP + Signature V4 is entirely viable, especially for simple tasks like uploading/downloading S3 files.

Let me know if you’d like a full upload example, presigned URL generator, or if you’re considering migrating to .NET 6+.

How to Query #LinkedIn from an #Email Address Using AvatarAPI.com

Introduction

When working with professional networking data, LinkedIn is often the go-to platform for retrieving user information based on an email address. Using AvatarAPI.com, developers can easily query LinkedIn and other data providers through a simple API request. In this guide, we’ll explore how to use the API to retrieve LinkedIn profile details from an email address.

API Endpoint

To query LinkedIn using AvatarAPI.com, send a request to:

https://avatarapi.com/v2/api.aspx

JSON Payload

A sample JSON request to query LinkedIn using an email address looks like this:

{
    "username": "demo",
    "password": "demo___",
    "provider": "LinkedIn",
    "email": "jason.smith@gmail.com"
}

Explanation of Parameters:

  • username: Your AvatarAPI.com username.
  • password: Your AvatarAPI.com password.
  • provider: The data source to query. In this case, “LinkedIn” is specified. If omitted, the API will search a default set of providers.
  • email: The email address for which LinkedIn profile data is being requested.

API Response

A successful response from the API may look like this:

{
    "Name": "Jason Smith",
    "Image": "https://media.licdn.com/dms/image/D4E12AQEud3Ll5MI7cQ/article-inline_image-shrink_1500_2232/0/1660833954461?e=1716422400&v=beta&t=r-9LmmNBpvS4bUiL6k-egJ8wUIpEeEMl9NJuAt7pTsc",
    "Valid": true,
    "City": "Los Angeles, California, United States",
    "Country": "US",
    "IsDefault": false,
    "Success": true,
    "RawData": "{\"resultTemplate\":\"ExactMatch\",\"bound\":false,\"persons\":[{\"id\":\"urn:li:person:DgEdy8DNfhxlX15HDuxWp7k6hYP5jIlL8fqtFRN7YR4\",\"displayName\":\"Jason Smith\",\"headline\":\"Creative Co-founder at Mega Ventures\",\"summary\":\"Jason Smith Head of Design at Mega Ventures.\",\"companyName\":\"Mega Ventures\",\"location\":\"Los Angeles, California, United States\",\"linkedInUrl\":\"https://linkedin.com/in/jason-smith\",\"connectionCount\":395,\"skills\":[\"Figma (Software)\",\"Facebook\",\"Customer Service\",\"Event Planning\",\"Social Media\",\"Sales\",\"Healthcare\",\"Management\",\"Web Design\",\"JavaScript\",\"Software Development\",\"Project Management\",\"APIs\"]}]}",
    "Source": {
        "Name": "LinkedIn"
    }
}

Explanation of Response Fields:

  • Name: The full name of the LinkedIn user.
  • Image: The profile image URL.
  • Valid: Indicates whether the returned data is valid.
  • City: The city where the user is located.
  • Country: The country of residence.
  • IsDefault: Indicates whether the data is a fallback/default.
  • Success: Confirms if the request was successful.
  • RawData: Contains additional structured data about the LinkedIn profile, including:
    • LinkedIn ID: A unique identifier for the user’s LinkedIn profile.
    • Display Name: The name displayed on the user’s profile.
    • Headline: The professional headline, typically the current job title or a short description of expertise.
    • Summary: A brief bio or description of the user’s professional background.
    • Company Name: The company where the user currently works.
    • Location: The geographical location of the user.
    • LinkedIn Profile URL: A direct link to the user’s LinkedIn profile.
    • Connection Count: The number of LinkedIn connections the user has.
    • Skills: A list of skills associated with the user’s profile, such as programming languages, software expertise, or industry-specific abilities.
    • Education History: Details about the user’s academic background, including universities attended, degrees earned, and fields of study.
    • Employment History: Information about past and present positions, including company names, job titles, and employment dates.
    • Projects and Accomplishments: Notable work the user has contributed to, certifications, publications, and other professional achievements.
    • Endorsements: Skill endorsements from other LinkedIn users, showcasing credibility in specific domains.
  • Source.Name: The data provider (LinkedIn in this case).

LinkedIn Rate Limiting

By default, LinkedIn queries are subject to rate limits. To bypass these limits, additional parameters can be included in the JSON request:

{
    "overrideAccount": "your_override_username",
    "overridePassword": "your_override_password"
}

Using these credentials allows queries to be processed without rate limiting. However, to enable this feature, you should contact AvatarAPI.com to discuss setup and access.

Conclusion

AvatarAPI.com provides a powerful way to retrieve LinkedIn profile data using just an email address. While LinkedIn is one of the available providers, the API also supports other data sources if the provider field is omitted. With proper setup, including rate-limit bypassing credentials, you can ensure seamless access to professional networking data.

For more details, visit AvatarAPI.com.

Get #GAIA ID from #Gmail using #AvatarAPI

In this blog post, we will explore how to retrieve a user’s name, profile picture, and GAIA ID from an email address using the AvatarAPI.

Introduction to AvatarAPI

AvatarAPI is a powerful tool that allows developers to fetch user information from various providers. In this example, we will focus on retrieving data from Google, but it’s important to note that AvatarAPI supports multiple providers.

Making a Request to AvatarAPI

To get started, you need to make a POST request to the AvatarAPI endpoint with the necessary parameters. Here’s a step-by-step guide:

Step 1: Endpoint and Parameters

  • Endpoint: https://avatarapi.com/v2/api.aspx
  • Parameters:
    • username: Your AvatarAPI username (e.g., demo)
    • password: Your AvatarAPI password (e.g., demo___)
    • provider: The provider from which to fetch data (e.g., Google)
    • email: The email address of the user (e.g., jenny.jones@gmail.com)

Step 2: Example Request

Here’s an example of how you can structure your request:

Copy{
    "username": "demo",
    "password": "demo___",
    "provider": "Google",
    "email": "jenny.jones@gmail.com"
}

Step 3: Sending the Request

You can use tools like Postman or write a simple script in your preferred programming language to send the POST request. Below is an example using Python with the requests library:

Copyimport requests

url = "https://avatarapi.com/v2/api.aspx"
data = {
    "username": "demo",
    "password": "demo___",
    "provider": "Google",
    "email": "jenny.jones@gmail.com"
}

response = requests.post(url, json=data)
print(response.json())

Step 4: Handling the Response

If the request is successful, you will receive a JSON response containing the user’s information. Here’s an example response:

Copy{
    "Name": "Jenny Jones",
    "Image": "https://lh3.googleusercontent.com/a-/ALV-UjVPreEBCPw4TstEZLnavq22uceFSCS3-KjAdHgnmyUfSA9hMKk",
    "Valid": true,
    "City": "",
    "Country": "",
    "IsDefault": true,
    "Success": true,
    "RawData": "108545052157874609391",
    "Source": {
        "Name": "Google"
    }
}

Understanding the Response

  • Name: The full name of the user.
  • Image: The URL of the user’s profile picture.
  • Valid: Indicates whether the email address is valid.
  • City and Country: Location information (if available).
  • IsDefault: Indicates if the returned data is the default for the provider.
  • Success: Indicates whether the request was successful.
  • RawData: The GAIA ID, which is a unique identifier for the user.
  • Source: The provider from which the data was fetched.

Other Providers

While this example focuses on Google, AvatarAPI supports other providers as well. You can explore the AvatarAPI documentation to learn more about the available providers and their specific requirements.

Conclusion

Using AvatarAPI to retrieve user information from an email address is a straightforward process. By sending a POST request with the necessary parameters, you can easily access valuable user data such as name, profile picture, and GAIA ID. This information can be instrumental in enhancing user experiences and integrating with various applications.

Stay tuned for more insights on leveraging APIs for efficient data retrieval!

Categories: Uncategorized Tags: , , , ,

Farewell #Skype. Here’s how their #API worked.

So, with the shutdown of Skype in May 2025, only two months away, there is not much need to hold on tight to our source code for the Skype API. It worked well for us for years on AvatarAPI.com
but with the imminent shutdown, their API will undoubtedly stop working as soon as Skype is shut down, and will no longer be relevant, even if the API stays active for a little while later.

In this post, we’ll take a deep dive into a C# implementation of a Skype user search feature using HTTP requests. This code interacts with Skype’s search API to fetch user profiles based on a given search parameter. We’ll break down the core functionality, security considerations, and potential improvements.

Overview of the SkypeSearch Class

The SkypeSearch class provides a static method, Search, which sends a request to Skype’s search API to retrieve user profiles. It uses an authentication token (SkypeToken) and manages retries in case of failures. Let’s explore its components in detail.

Key Features of the Implementation

  1. Handles API Requests Securely: The method sets various security protocols (Ssl3, Tls, Tls11, Tls12) to ensure compatibility with Skype’s API.
  2. Custom Headers for Authentication: It constructs an HTTP request with necessary headers, including x-skypetoken, x-skype-client, and others.
  3. Manages Rate Limits & Token Refresh: If the API responds with an empty result (potentially due to a 429 Too Many Requests error), the token is refreshed, and the search is retried up to five times.
  4. Enhances API Response: The method modifies the API response to include an additional avatarImageUrl field for each result.

Breaking Down the Search Method

Constructing the API Request

var requestNumber = new Random().Next(100000, 999999);
var url = string.Format(
    "https://search.skype.com/v2.0/search?searchString={0}&requestId={1}&locale=en-GB&sessionId={2}",
    searchParameter, requestNumber, Guid.NewGuid());

This snippet constructs the API request URL with dynamic query parameters, including:

  • searchString: The user input for searching Skype profiles.
  • requestId: A randomly generated request ID for uniqueness.
  • sessionId: A newly generated GUID for session tracking.

Setting HTTP Headers

HTTPHeaderHandler wicket = nvc =>
{
    var nvcSArgs = new NameValueCollection
    {
        {"x-skypetoken", token.Value},
        {"x-skype-client", "1418/8.134.0.202"},
        {"Origin", "https://web.skype.com"}
    };
    return nvcSArgs;
};

Here, we define essential request headers for authentication and compatibility. The x-skypetoken is a crucial element, as it ensures access to Skype’s search API.

Handling API Responses & Retrying on Failure

if (jsonResponse == "")
{
    token = new SkypeToken();
    return Search(searchParameter, token, ++maxRecursion);
}

If an empty response is received (potentially due to an API rate limit), the method refreshes the authentication token and retries the request up to five times to prevent excessive loops.

Enhancing API Response with Profile Avatars

foreach (var node in jResponse["results"])
{
    var skypeId = node["nodeProfileData"]["skypeId"] + "";
    var avatarImageUrl = string.Format(
        "https://avatar.skype.com/v1/avatars/{0}/public?size=l",
        skypeId);
    node["nodeProfileData"]["avatarImageUrl"] = avatarImageUrl;
}

After receiving the API response, the code iterates through the user results and appends an avatarImageUrl field using Skype’s avatar service.

using System;
using System.Collections.Specialized;
using System.Net;
using System.Text;
using Newtonsoft.Json.Linq;

namespace SkypeGraph
{
    public class SkypeSearch
    {
        public static JObject Search(string searchParameter, SkypeToken token, int maxRecursion = 0)
        {
            if (maxRecursion == 5) throw new Exception("Preventing excessive retries");
            ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 |
                                                   SecurityProtocolType.Tls |
                                                   SecurityProtocolType.Tls11 |
                                                   SecurityProtocolType.Tls12;
            var requestNumber = new Random().Next(100000, 999999);
            var url = string.Format("https://search.skype.com/v2.0/search?searchString={0}&requestId={1}&locale=en-GB&sessionId={2}", searchParameter, requestNumber, Guid.NewGuid());
            var http = new HTTPRequest {Encoder = Encoding.UTF8};
            HTTPHeaderHandler wicket = nvc =>
            {
                var nvcSArgs = new NameValueCollection
                {
                    {"x-skypetoken", token.Value},
                    {"x-skypegraphservicesettings", ""},
                    {"x-skype-client","1418/8.134.0.202"},
                    {"x-ecs-etag", "GAx0SLim69RWpjmJ9Dpc4QBHAou0pY//fX4AZ9JVKU4="},
                    {"Origin", "https://web.skype.com"}
                };
                return nvcSArgs;
            };
            http.OverrideUserAgent =
                "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36";
            http.OverrideAccept = "application/json";
            http.TimeOut = TimeSpan.FromSeconds(5);
            http.HeaderHandler = wicket;
            http.ContentType = "application/json";
            http.Referer = "https://web.skype.com/";
            var jsonResponse = http.Request(url);
            if (jsonResponse == "")
            {
                // In case of a 429 (Too many requests), then refresh the token.
                token = new SkypeToken();
                return Search(searchParameter, token, ++maxRecursion);
            }
            var jResponse = JObject.Parse(jsonResponse);
            #region sample
            /*
             {
                   "requestId":"240120",
                   "results":[
                      {
                         "nodeProfileData":{
                            "skypeId":"live:octavioaparicio_jr",
                            "skypeHandle":"live:octavioaparicio_jr",
                            "name":"octavio aparicio",
                            "avatarUrl":"https://api.skype.com/users/live:octavioaparicio_jr/profile/avatar",
                            "country":"Mexico",
                            "countryCode":"mx",
                            "contactType":"Skype4Consumer"
                         }
                      }
                   ]
                }
             */
            #endregion
            foreach (var node in jResponse["results"])
            {
                var skypeId = node["nodeProfileData"]["skypeId"] + "";
                var avatarImageUrl = string.Format("https://avatar.skype.com/v1/avatars/{0}/public?size=l", skypeId);
                node["nodeProfileData"]["avatarImageUrl"] = avatarImageUrl;
            }
            return jResponse;
        }
    }
}
Categories: Uncategorized Tags: , , , ,