Verify the connection and hand over

Updated Nov 8, 2026 · Based on web research, 2026-11-08

Once auth and schema mapping are done, send a test event and confirm it lands in Data Cloud before you call the integration “done.” Then hand it off cleanly so another team can own it long-term.

Send and verify a test event

1. Send one test record through the Ingestion API endpoint you mapped, using the auth flow you set up.
2. Check the HTTP response: 202 Accepted or 201 Created means Salesforce accepted the request — not that it finished processing.
3. Wait at least 30 seconds, then check that the record is queryable in Data Cloud.
4. For a streaming data stream, allow up to roughly 3 minutes for the event to finish processing before you query it.
5. Confirm the record’s fields match what you sent, including the Primary Key and Record Modified values.

Hand over to the operating team

Server-to-Server handover checklist Copy list

• Connected app details (name, consumer key) documented in the team's runbook — secrets kept out of the doc itself
• Credential owner named: who rotates the consumer secret or certificate, and how often
• Monitoring owner named: who checks that the data stream keeps receiving events
• Escalation contact named: who to page if events stop arriving or auth starts failing
• A known-good test event and its expected result recorded, so a future check has something to compare against
• Access to the connected app and OAuth settings transferred to the operating team
• This page and the auth/schema pages shared with the operating team as reference