Obtain an access token with the scope https://purl.imsglobal.org/spec/lti/scope/noticehandlers from the platform's token endpoint
GET the Platform Notification Service endpoint to discover which notice types the platform supports and which handlers (if any) the tool has already registered
PUT a notice handler registration to the same endpoint specifying the notice type(s) to subscribe to and the tool's handler URL that will receive the JWT-signed notice payloads
Implement the handler endpoint to receive POST requests containing JWT notice envelopes; validate the JWT signature using the platform's JWKS, then process each notice object in the notices array
Handle batch notices correctly: the platform may deliver multiple notices in a single POST; process each notice idempotently and acknowledge receipt with an appropriate HTTP 200 response
Known gotchas
The Platform Notification Service is a relatively new addition to the LTI ecosystem and platform support is not universal; verify the platform exposes the service endpoint in its OpenID configuration before building a dependency on it
Notice JWTs are signed with the platform's private key using the same mechanism as LTI launch JWTs; a tool that does not maintain an up-to-date cache of the platform's JWKS will fail to verify notices after a platform key rotation
The handler URL registered with the platform must be publicly reachable; tools running in development environments behind NAT will not receive notices even after a successful PUT registration
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp