While you're here could you fix up this sentence.

In RB6+ we have QueryArgs and HTTPHeader type aliases defined in /reviewboard/hostingsvcs/base/http.py. Would it be appropriate to use them here?

Small nit which I'm not sure even matters but I notice we usually use * instead of - in docstrings.

Could we use JSONDict instead?

Ship It!

Looks very good. Just a few comments here.
One thing I was trying to think about when looking at this is whether we should be typing resource payloads as list[...]/dict[...] or Sequence[...]/Mapping[...]. I don't think we want to allow mutability for the caller, so the latter is probably more correct, but then I don't know whether that imposes new challenges when populating the resource wrapper.

We can avoid the issubclass and optimize out the call if we do:

assert token is None or not issubclass(...)

If we go with Python 3.9+, we could do key = name.removeprefix(_EXTRA_DATA_PREFIX)

Can you make these parameter names inline literals?

This reads kind of awkwardly, given the length of the value. Maybe alias it, or do:

SPECIAL_LINKS: dict[
    str,
    tuple[...]
] = {
    ...
}


Also, we should use Mapping, since this isn't meant to be mutated.

Missing Returns.

No blank line here.

Missing docs with Version Added.
Also, probably should be Optional[Union[...]]. I know it's the same thing, but Optional[] is more consistent.

Let's swap the order here, keep it alphabetical.

Are these Any or JSONValue? Maybe the former is safer all around, but floating the question.

Can be later, but it'd be nice to start moving to keyword-only arguments so these are all easier to manage over time.
Same applies to other base resource functions.

We're doing this | and attribute access per-item in data. Let's build the exclusion list only once before the loop.

Ship It!