TECHNICAL INTEGRATION

Integration guide for AutoScout24 API import on WordPress

Connect ADP Car Market Hub with WordPress, AutoScout24 API access, scheduled imports, webhooks, templates, page builders, translations and frontend presentation workflows.

Open Integration Guide Open AutoScout24 API Setup

Integration readiness overview

A reliable integration starts with the correct API access, server configuration, background processing and frontend compatibility.

API access

Configure the API base URL, credentials, seller access and connection checks required for importing vehicle inventory.

View related docs

Scheduled processing

Use reliable cron processing for recurring imports, image handling, cleanup jobs and background tasks.

View related docs

Theme compatibility

Validate archive pages, detail pages, shortcodes and template output with the active WordPress theme.

View related docs

Customization workflow

Use template overrides, custom CSS and page builder integration without modifying plugin core files.

View related docs

Staging and go live

Test the integration in a controlled environment before moving configuration and templates to production.

View related docs

Integration architecture

ADP Car Market Hub connects external vehicle data with WordPress, scheduled processing and frontend presentation layers.

Layer Component Role in integration
External External data source Provides vehicle inventory data through configured API access.
Connection API credentials Authorize the plugin to request vehicle data for the configured account.
Configuration Plugin settings Store connection values, import settings, layout choices and operational preferences.
Processing Import engine Processes vehicle data, updates inventory and coordinates recurring synchronization.
Storage WordPress database Stores vehicle records, metadata, settings, logs, leads and analytics data.
Media Media library Stores imported vehicle images and related media assets.
Frontend Templates Render archive pages, detail pages and other frontend modules.
Embedding Shortcodes Allow controlled frontend embedding in pages, builders and custom layouts.
Presentation Frontend pages Present imported inventory to website visitors using the active theme.
Conversion Leads and notifications Capture enquiries and support customer contact workflows.
Intelligence Analytics and Market Insights Provide operational visibility and market intelligence where configured.

Setup and connection flow

The integration process should be completed in a controlled order so that connection issues are identified before production imports begin.

  1. Prepare API access Collect API base URL, token URL, seller identifiers and required credentials before configuring the plugin.
  2. Configure plugin settings Enter connection values in the WordPress admin and keep credentials out of public documentation and public repositories.
  3. Run the connection test Validate that the server can reach the configured API endpoints and receive valid responses.
  4. Run a controlled import Start with a limited import to confirm vehicle data, media handling and update behavior.
  5. Validate frontend output Review archive pages, detail pages, shortcodes, compare views, favorites and template output.
  6. Prepare go live Confirm cron, backups, staging to live migration, SEO relevant pages and support checks before production use.

API access and external credentials

API configuration defines how the plugin connects to external vehicle data and authenticates requests.

Required configuration values

  • API Base URL
  • Token URL
  • Client ID
  • Client Secret
  • Seller ID or account identifier
  • Connection test endpoint if configured
  • API environment (staging or production)

Credential handling

  • Never publish credentials in documentation
  • Store credentials only in the plugin settings
  • Restrict access to authorized administrators
  • Validate API URLs before importing
  • Confirm account permissions before go live
  • Rotate credentials when access changes
Open AutoScout24 API Setup Open External API Credentials

Cron, automation and webhooks

Recurring imports, cleanup routines and integration events require reliable background processing.

Cron

Server cron setup

Server side cron is recommended for reliable production imports, cleanup processes and scheduled background tasks.

Server Cron Setup
Webhooks

Webhook integration

Webhook documentation explains how external integration events or signals can be handled where supported.

Webhook Integration
Background

Background reliability

Import jobs should be monitored so failed API calls, image queues or delayed processes can be identified early.

Cron and Background Processing

Theme, template and page builder integration

The plugin should be integrated with the active WordPress theme without editing plugin core files.

Theme and template integration Theme output

Use theme integration and template overrides to control how archive pages, vehicle detail pages and frontend modules are rendered.

  • Archive templates
  • Detail templates
  • Template overrides
  • Theme compatibility checks
  • Custom CSS
  • Staging validation
Page builder integration Builder workflows

Use page builder compatible workflows where supported while keeping plugin controlled inventory output intact.

  • Shortcode placement
  • Builder sections
  • Layout containers
  • Reusable content blocks
  • Responsive checks
  • Frontend validation

Frontend output and shortcode integration

Frontend output should be tested with real vehicle data, configured filters and the active theme before go live.

Component Purpose Documentation
Vehicle archive Displays imported inventory with filters, sorting and vehicle cards. Vehicle Archive
Vehicle detail pages Displays gallery, pricing, specifications, contact actions and related vehicle information. Vehicle Detail Pages
Compare Allows visitors to compare selected vehicles. Compare
Favorites Allows visitors to save vehicles for later review. Favorites
Search alerts Supports saved search or alert workflows where configured. Search Alerts
Shortcodes Allows controlled embedding of plugin output in WordPress pages and builder layouts. Shortcodes Reference

Translation and localization

The plugin and documentation are prepared for multilingual workflows. English remains the source language, while translated folders use localized folder names and file names.

i18n

Multilingual documentation structure

  • Source language English
  • Prepared translation folders German · French · Italian · Spanish · Dutch
  • Folder naming Localized folder and file names per language
  • Translation map translation-map.md connects localized files to English source
  • Plugin strings Poedit compatible translation workflows
Open Translation and Poedit Guide Open Documentation Language Folder

Staging to live workflow

A controlled staging to live workflow reduces risk when moving API configuration, templates and frontend output into production.

  • Staging environment prepared
  • API credentials verified
  • Connection test passed
  • Limited import tested
  • Vehicle images checked
  • Archive page reviewed
  • Detail pages reviewed
  • Shortcodes reviewed
  • Template overrides tested
  • Cron strategy confirmed
  • Backup available
  • Go live checklist completed
Open Staging to Live Migration Open Go Live Checklist

Integration documentation

Open the relevant integration documents directly in the public documentation repository.

Document Link
Integration Guide section Integration Guide section
AutoScout24 API Setup AutoScout24 API Setup
External API Credentials External API Credentials
Server Cron Setup Server Cron Setup
Webhook Integration Webhook Integration
Theme Integration Theme Integration
Page Builder Integration Page Builder Integration
Template Override Guide Template Override Guide
Custom CSS Guide Custom CSS Guide
Translation and Poedit Guide Translation and Poedit Guide
Staging to Live Migration Staging to Live Migration

Documentation links follow the active website language. English is the source language. Other language folders use localized folder and file names.

Continue exploring

Open Documentation Open System Requirements Open API and Webhooks