User Feedback route should work using both project ID and Project Name

[donalmacc]

Summary

In the User Feedback documentation, the URL for submitting user feedback to requires specifying the project and organisation names rather than using the organisation ID and the project ID.

Motivation

This means that any application wanting to send user feedback associated with an event must provide an extra endpoint; one taht names the organisation and the project to which it pertains. If the user feedback route was of the form https://sentry.io.api/0/projects/{organization_id}/{project_id}/user-feedback/, an SDK developer would be able to form the user-feedback URL from the DSN, rather than requiring the application developer to provide a DSN and a user feedback url.

Additional Context

N/A

[BYK]

Possibly related: #26208.

[getsentry-release]

Routing to @getsentry/ecosystem for triage. ⏲️

[getsentry-release]

Routing to @getsentry/workflow for triage. ⏲️

[wedamija]

Using org/project slug is standard across our api, we're not likely to change this.

[BYK]

Closing per @wedamija's answer.

[untitaker]

This falls into team-ingest territory. We've been aware of this problem for a while, and as a solution to this and other unrelated problems we now also have a way to submit user feedback as part of an envelope: https://develop.sentry.dev/sdk/envelopes/#user-feedback

This could probably be documented better but the point of envelopes here is that the auth/dsn/project information is sent in a unified format, there is one endpoint that can take arbitrarily many items and as a result you save on HTTP requests.

Let me know if that works for you, I'll reopen this for now.

[donalmacc]

Hey untitaker, thanks for the response.

I can definitely work with the user-feedback envelope!