Add missing api entities

What does this MR do?

Add entities to be specific about API contents. Will update docs once the keys are agreed upon.

Are there points in the code the reviewer needs to double check?

Whether all the fields should continue to be exposed (or whether something else is wrong).

Why was this MR needed?

Over the past few releases, both of these objects have changed in the API; I'd like them to not :) .

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• CHANGELOG entry added
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Mentioned in the commit messages: #23895 (closed) #23877 (closed).