HTTP Interfaces and External Systems for Auto Service

What data for this category looks like

Marketing content data for auto services comes primarily from three sources: store operation systems, owner service platforms, and brand marketing material libraries. Campaign-style marketing materials are updated in batches per single marketing activity. Customer group tag data is synced daily. Standardized script materials are uploaded temporarily on demand.

Single data entries include fields such as activity ID, store code, material type, effective and expiration time, applicable vehicle level, target customer group tags, and material files. apply_vehicle_level is an enumeration type. push_channel is limited to three categories: SMS, WeChat Work, and owner APP. The unit for material files is MB. Customer group tag fields are comma-separated strings.

What constraints these characteristics impose on HTTP interfaces and external systems

Because the data includes targeted fields like applicable vehicle level and target customer group tags, HTTP interfaces must support filtering and pulling by enumeration values and tag strings. This prevents returning non-targeted invalid data. Single material files have large sizes, so interfaces must support resumable upload mechanisms. Request timeout values must be adapted for large file upload scenarios. Based on the update rhythm of effective and expiration times, interfaces must provide the ability to incrementally pull data by time range. This reduces resource consumption from full synchronization. Store codes must also be included as authentication parameters. This ensures data isolation between different stores and prevents cross-store data misuse.

How to set configurations

Configuration Item	Recommended Value	Rationale
`UPLOAD_MATERIAL_MAX_SIZE`	`500 MB`	Auto service marketing materials are mostly posters and short videos. Single file size usually does not exceed 500 MB, which avoids interface timeout issues.
`DATA_SYNC_INTERVAL`	`3600 seconds`	Customer group tag data is synced daily, and marketing materials are updated on demand. Pulling incrementally every hour balances real-time performance and resource usage.
`FILTER_VEHICLE_LEVEL_ENABLE`	`Enabled`	Data includes applicable vehicle level fields. Enabling this allows filtering results by vehicle type to improve data accuracy.
`REQUEST_TIMEOUT_SECONDS`	`120 seconds`	For large file upload scenarios, 120 seconds covers most upload durations and prevents mid-transfer disconnects.
`AUTH_STORE_ID_REQUIRED`	`Enabled`	Marketing content is isolated by store. Store codes must be included as authentication parameters to ensure correct data permissions.
`MATERIAL_FORMAT_ALLOWED`	`jpg,png,mp4,docx`	Covers commonly used auto service marketing material formats and filters invalid file types.

The parameter values provided on this page are common starting points for configuration. Actual values are affected by material formats, data volume and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.

Three common mistakes

Phenomenon: The collection_id returned after calling the upload interface does not match the actually bound marketing material library. Cause: The collection_id field is not specified in the request parameters. The interface uses the global default collection by default, leading to incorrect material attribution.
Phenomenon: The number of materials returned by the interface does not match expectations, and some content applicable to specific vehicle models is missing. Cause: The FILTER_VEHICLE_LEVEL_ENABLE configuration is not enabled, or the apply_vehicle_level filter field is not passed in the request parameters, resulting in returning full unfiltered data.
Phenomenon: Frequent 504 Gateway Timeout errors occur during large file uploads. Cause: The REQUEST_TIMEOUT_SECONDS configuration is not adjusted to a duration adapted for large file uploads. The default timeout value is insufficient to cover upload durations.

How to confirm configurations are correctly set

Call the marketing material pull interface, pass the specified store code and vehicle level parameters, and verify that the returned results only include materials for the corresponding store and vehicle model.
Upload a single material file that complies with the UPLOAD_MATERIAL_MAX_SIZE limit, confirm that the interface returns correct file_id and collection_id, and that the file is successfully attributed to the specified marketing material library.
Check interface logs to confirm that each request carries a valid store code authentication parameter, with no authentication failure logs.
After adjusting the DATA_SYNC_INTERVAL configuration, verify that the time range of incrementally pulled updated data matches the configuration.

Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.