What this surface enables
Retail and Logistics Logs for 1.2.0
No durable provider record or application workflow contract was established from the source identity or bounded document evidence; view, camera, callback, and authentication sessions alone do not make a source stateful.
Authority: Conservative Default · No durable-state signal promoted from incidental vocabularyUnspecified
Other
No fenced language tags in the source README
No explicit authentication signal detected
Prepare the integration
The source does not declare a platform-specific prerequisite. Confirm product entitlement, supported version, and authentication in the current developer console before integration.
Topics documented by the source
01v1.2.0-logs
Retail and Logistics logs for 1.2.0 certification - test scenarios for retail and logistics
To submit logs for protocol compliance verification, following steps need to be followed:
1. Create a fork of the "v1.2.0-logs" repository
2. Create a branch with the name of your entity under "logs"
3. Merge your logs into this branch (logs should include request & response payloads for all enabled APIs)
4. Create PR for your branch
Service references found
URLs are sanitized during ingestion and may include documentation or legacy hosts. Use them to trace the source, not as a substitute for the current API contract.
https://docs.google.com/spreadsheets/d/1JZV6ZQzXcHUsOwegGtArX3DdIXYIy3gxkhQ00q7kICc/edit#gid=1367601795https://docs.google.com/spreadsheets/d/1JZV6ZQzXcHUsOwegGtArX3DdIXYIy3gxkhQ00q7kICc/edit#gid=1670900093