feat(api): add analytics and project report forwarding - #30
Merged
Merged
Conversation
Bjornftw
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review sending-openapi.json and team-openapi.json from the current documentation source.
Source fingerprints:
The source specifications remain outside this repository and are not changed.
Changes
Add POST /analytics and its request and response types. Add project report-forwarding retrieve, update, delete, verify, and resend-code methods. Handle the empty HTTP 204 delete response.
Update project, route, webhook, RBAC, and suppression contracts. Keep project creation API tokens and both successful suppression deletion results. Keep existing public type names, scheduling helpers, builders, and cursor types. Check all 55 object component field sets against the current source. No public model type names are removed.
Keep string-valued header maps for single-message and batch sending. Both current source schemas define headers as an object with string-valued additional properties.
Validation
Ruff, mypy, 70 tests, and wheel/source package builds passed. The installed mypy warns that its Python 3.9 configuration is no longer supported. CI must check supported Python versions.
Compatibility corrections
Keep reschedule, cancel, and process on AsyncMessagesEndpoint. Restore the old AsyncDomainsEndpoint calls as forwarders to that message endpoint. Both client paths use the specified HTTP methods, escaped message IDs, Bearer auth, bodies, and HTTP 200/202 responses. Ruff, mypy, all 70 tests, and wheel/source builds passed.
Keep the specification corrections for fields and enum values that the API no longer returns or accepts. Do not restore those as current wire contracts.