mobile_app_key. SDK-backed operations are traced to official source files in the coverage report. Routes without an SDK wrapper are explicitly marked contract-only.
Error envelope
Non-2xx responses use the StackShift response envelope. Checksuccess: false, then read the structured error value and HTTP status. SDK clients surface the status, code, message, and details through their native error type.
Examples
These static examples show the verified route and authentication boundary. Use the official SDK method shown in each heading so serialization and response unwrapping remain consistent with the contract.POST /observe/{appKey}/events
The SDK sends this request to the endpoint supplied by your application. StackShift does not publish a universal mobile endpoint in this reference.
/observe/{appKey}/events and authenticates with the appKey path value. A successful ingestion returns 2xx with no response body.