Understanding PBS API Data Format and Integration Requirements

Summary: PBS transmits and stores structured user data via integration payloads and API responses; integrations are coordinated by project and partner managers and require completed certifications before any production use.

How is user data formatted and returned by PBS APIs?

User data is transmitted as structured fields in JSON payloads (for example: name fields, contact method, employment, income, residence and vehicle preferences). API responses use a success flag and a data object that can include an internal id, user names, and an accessToken.

How are integrations and production access managed?

Integrations are managed through a coordinated integration process involving project and partner program contacts. Certifications must be confirmed and completed before any production uses are allowed — this applies to both testing and live environments.

Who coordinates integration and communication between teams?

Integration coordination is handled by designated project managers and partner program account managers. Communication occurs through direct project emails and handoffs between those contacts.

What privacy or confidentiality practices are indicated?

Communications include a privacy and confidentiality notice that states messages and attachments are confidential and intended only for the addressed recipient, and requests that recipients notify the sender and delete the message if received in error.

Conclusion: PBS exchanges structured JSON user data and returns success/data responses including tokens; integrations are overseen by named project and partner managers and require completed certifications before enabling production usage, with confidential email communication used for coordination.