External API access
External API access provides the vehicle data that is imported and synchronized inside WordPress.
View related docsAPI AND WEBHOOKS
Review how ADP Car Market Hub connects to external vehicle data, handles API credentials, exposes technical endpoints, supports webhook workflows and validates secure network communication.
This page summarizes the technical interfaces involved in connecting ADP Car Market Hub with external data sources and WordPress based integration workflows.
External API access
External API access provides the vehicle data that is imported and synchronized inside WordPress.
View related docsCredential management
Credentials authorize API requests and should only be stored in protected plugin settings.
View related docsREST and AJAX endpoints
Technical endpoints support plugin operations, frontend workflows and controlled WordPress admin interactions.
View related docsWebhook workflows
Webhook documentation explains how integration events or external signals can be handled where supported.
View related docsDiagnostics and support
Connection tests, logs and troubleshooting documents help identify failed requests, blocked endpoints or configuration errors.
View related docsA reliable API integration depends on secure outbound requests, valid credentials, correct endpoint configuration and observable error handling.
API access must be configured carefully because credentials control which external data can be requested by the plugin.
Required values
Credential handling rules
Most API issues are caused by blocked outbound requests, invalid credentials, SSL problems, wrong URLs or account permission issues.
The plugin may use REST API endpoints and AJAX actions for controlled admin operations, frontend workflows and integration behavior.
REST API documentation describes the plugin endpoint surface, expected behavior and technical usage boundaries.
AJAX documentation describes controlled admin or frontend interactions that rely on WordPress AJAX behavior.
Webhook documentation explains how integration events or external signals can be handled where supported by the plugin workflow.
Use webhooks to understand how event driven integration patterns can complement scheduled imports and manual actions.
Webhook IntegrationWebhook handling should validate the request source, sanitize input, log failures and avoid exposing private data.
Webhooks Technical DocumentationFailed webhook calls should be diagnosed through logs, endpoint reachability, authentication checks and payload validation.
TroubleshootingWebhook availability and behavior depend on the installed plugin version and configured integration scenario.
API and webhook integrations should be documented and operated without exposing sensitive data.
Safe integration practices
Do not publish
When API or webhook communication fails, start with connection tests, credentials, network rules and logs.
| Issue | Likely cause | Recommended check | Documentation |
|---|---|---|---|
| Connection test fails | Wrong URL, blocked outbound request or SSL issue | Check API URL, DNS, hosting firewall and SSL chain | API Network and SSL API Connection Errors |
| Authentication fails | Invalid client ID, client secret, token endpoint or account permissions | Check credentials and seller account access | API Credentials Setup External API Credentials |
| Imports return no vehicles | Seller ID, account mapping or API permissions do not match expected inventory | Check account access and import configuration | AutoScout24 API Setup |
| Webhook not received | Endpoint not reachable or external sender not configured | Check webhook URL, authentication and logs | Webhook Integration |
| AJAX request fails | Nonce, permission or malformed request issue | Check browser console, admin permissions and logs | AJAX Actions |
| REST request fails | Authentication, capability or endpoint issue | Check endpoint namespace, request method and response | REST API Endpoints |
Developers can use the technical documentation to review endpoint behavior, extension points, request handling and integration boundaries.
REST API for Developers
Technical reference for developers integrating with the plugin REST API surface.
REST API for DevelopersAJAX Actions for Developers
Developer documentation for AJAX action handling, nonces and capability checks.
AJAX Actions for DevelopersREST API Endpoints
Technical reference for all REST endpoints exposed by the plugin.
REST API EndpointsAJAX Actions
Technical reference for all AJAX actions registered by the plugin.
AJAX ActionsWebhooks
Technical documentation for webhook behavior and integration patterns.
WebhooksSecurity and Capability Checks
Security patterns, capability checks and access control for plugin endpoints.
Developer DocumentationSanitization and Escaping
Input sanitization and output escaping patterns used across the plugin codebase.
Developer DocumentationLogging and Debugging
Logging, debug output and diagnostic tooling available for developers.
Developer DocumentationTesting Guide
Testing guidance and quality assurance workflows for plugin integrations.
Developer DocumentationOpen the relevant API, webhook, network and developer documents directly in the public documentation repository.
Integration Guide
Getting Started and Requirements
Technical Documentation
Developer Documentation
Documentation links follow the active website language. English is the source language. Other language folders use localized folder and file names.