DEVELOPER DOCUMENTATION

Technical developer notes for ADP Car Market Hub integration

Explore the public developer documentation for ADP Car Market Hub, including architecture, hooks, filters, REST API references, AJAX actions, cron hooks, template overrides, security guidelines, debugging and release workflow.

Open Developer Documentation Open Hooks and Filters

Developer documentation overview

The developer documentation gives technical implementers a structured entry point into the plugin architecture, extension points, endpoint behavior and safe customization workflows.

Extension points

Use documented actions, filters, hooks and extension points instead of editing plugin core files.

Hooks and Filters

API and background processing

Review REST API behavior, AJAX actions, cron hooks and scheduled processing boundaries.

REST API for Developers

Templates and frontend assets

Use template overrides, frontend assets and shortcode behavior to customize output safely.

Template System and Overrides

Security and release workflow

Follow capability checks, sanitization, escaping, testing and release guidance before deploying changes.

Security and Capability Checks

Developer entry points

Start with the documents that match your role and implementation task.

New developer onboarding Getting started
Developer Overview Local Development Setup Repository Structure Coding Standards
Plugin architecture Architecture
Plugin Architecture for Developers Database Tables for Developers Option Keys and Settings Storage Custom Post Types and Taxonomies
Extension development Extension points
Hooks and Filters Actions Reference Filters Reference Import Engine Extension Points
Frontend customization Frontend
Template System and Overrides Frontend Assets Admin Assets Shortcodes for Developers

Architecture and codebase orientation

Before adding integrations or customizations, developers should understand the plugin lifecycle, repository structure, data model and storage behavior.

Core architecture topics

  • Plugin lifecycle
  • Repository structure
  • Data model
  • Database tables
  • Options and settings storage
  • Custom post types and taxonomies
  • Import engine
  • Image import queue
  • Cron scheduler

Recommended reading order

Open Developer Overview Open Plugin Architecture Open Data Model

Extension points

Custom integrations should use documented extension points instead of modifying plugin core files.

Extension area Use case Recommended document
Actions React to plugin events or processing steps Actions Reference
Filters Modify values or output through controlled filter points Filters Reference
Hooks and filters overview Understand available extension mechanisms Hooks and Filters
Import engine extension points Extend or adjust import related behavior safely Import Engine Extension Points
Image import extension points Customize image handling or queue behavior where supported Image Import Extension Points
Lead processing extension points Integrate lead handling with external workflows Lead Processing Extension Points
Analytics extension points Extend analytics related behavior where supported Analytics Extension Points
Market Insights extension points Review extension boundaries for market related logic Market Insights Extension Points
PDF manager extension points Extend or customize PDF related workflows where supported PDF Manager Extension Points

API, AJAX and background processing

Developers should review endpoint behavior, AJAX actions and cron hooks before extending technical workflows.

Templates and frontend assets

Frontend customization should use the documented template system, shortcode behavior and asset structure.

Template system

  • Template overrides
  • Archive output
  • Vehicle detail output
  • Shortcodes
  • Frontend modules
  • Theme compatibility
Template System and Overrides Template Overrides Shortcodes for Developers Frontend Guide

Assets and UI behavior

  • Frontend assets
  • Admin assets
  • Responsive behavior
  • Page builder integration
  • Custom CSS
  • Admin interface constraints
Frontend Assets Admin Assets Custom CSS Guide Page Builder Integration

Security, sanitization and capability checks

Developer work must follow WordPress security practices and avoid exposing private data or unsafe operations.

Required practices

  • Use capability checks for privileged actions
  • Validate nonces for AJAX and form actions
  • Sanitize incoming data
  • Escape output
  • Avoid exposing credentials
  • Do not log sensitive values
  • Use prepared database queries
  • Respect privacy and retention settings

Developer references

Security and Capability Checks Sanitization and Escaping Access Control and Capabilities Privacy, Security and Compliance Known Limitations and Open Risks

Debugging, testing and release workflow

Before deploying changes, developers should review logging, debugging, testing and release workflow documentation.

  1. Debug locally Use local development and logging guidance to reproduce issues before changing production behavior.
    Local Development Setup Logging and Debugging
  2. Validate behavior Test import workflows, API responses, cron hooks, frontend output and admin screens after changes.
    Testing Guide Import Engine Extension Points
  3. Review security Check sanitization, escaping, capabilities and public data exposure before release.
    Security and Capability Checks Sanitization and Escaping
  4. Prepare release Follow release, build and contribution guidance before packaging or deploying changes.
    Release and Build Process Contribution Guidelines

Public developer documentation rules

Developer documentation should be useful for implementation partners without exposing private implementation details.

Safe to publish

  • Architecture overviews
  • Public hooks and filters
  • General endpoint behavior
  • Template override guidance
  • Coding standards
  • Testing workflow
  • Troubleshooting guidance
  • Release process
  • General extension points

Do not publish

  • API secrets
  • Private access tokens
  • Internal server paths
  • Customer data
  • Private API URLs
  • Raw credentials
  • Security sensitive exploit details
  • Confidential implementation notes
  • Internal risk notes

Developer documentation

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

Getting started for developers

Architecture and storage

Extension points

API and background processing

Security, debugging and release

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

Continue exploring

Open API and Webhooks Open Integration Guide Open System Requirements