PBS integration requirements
Research: 2026-10-16
Public-source requirements profile; not an implemented integration
Four public documentation pages; not a complete PBS API inventory.
The undated changing-data page names ARISTOGOLD; present availability of a page does not establish a current contract.

Access
Finding: PartnerHub describes HTTPS authentication and account access limited to authorized dealership SerialNumbers.
Freshness: Public documentation only; live behavior untested.
Proposed requirement: Verify approved accounts, dealership mapping and revoked-access behavior before any data access.
Source: https://partnerhub.pbsdealers.com/basics

Read scope
Finding: Get requests require SerialNumber; empty criteria are ignored.
Freshness: Public documentation only; live behavior untested.
Proposed requirement: Require explicit local filters and field allowlists; confirm pagination, change cursors and deletion handling.
Source: https://partnerhub.pbsdealers.com/getting

Queued writes
Finding: The ARISTOGOLD description queues changes for roughly minute-level processing.
Freshness: Undated legacy description; current behavior unconfirmed.
Proposed requirement: Separate acceptance from committed state; agree on read-back confirmation and timeout handling.
Source: https://partnerhub.pbsdealers.com/changing

Record matching
Finding: Changes match records or create new ones; omitted or empty update fields are ignored.
Freshness: Undated legacy description; current behavior unconfirmed.
Proposed requirement: Confirm identifiers and field-clearing rules. Test failed matches and replay without creating duplicates.
Source: https://partnerhub.pbsdealers.com/changing

Failure signals
Finding: The sample pairs HTTP 200 with WasSuccessful:false.
Freshness: Public documentation only; live behavior untested.
Proposed requirement: Check operation-specific response bodies and errors; never infer success from HTTP status alone.
Source: https://partnerhub.pbsdealers.com/json/metadata?op=NotificationChange

Event direction
Finding: NotificationChange is a request sent to PBS, not evidence of outbound webhooks.
Freshness: Public documentation only; live behavior untested.
Proposed requirement: Obtain a separately documented event contract before promising push notifications.
Source: https://partnerhub.pbsdealers.com/json/metadata?op=NotificationChange

Unknowns: Current product/version applicability, approved operations and fields, sandbox access, fees, rate limits, delivery guarantees, idempotency and support SLA remain unconfirmed.

Proposed acceptance (not run): In an authorized test environment, demonstrate allowed and denied dealership reads, scoped queries, duplicate-free replay, empty-field behavior, body-level failures and delayed read-back. Record observed latency and quoted cost; set acceptable budgets with the owner before implementation. These checks have not run.

Sources checked October 16, 2026; publication dates not established.