List requests waiting for me
GET /account/requests/incoming
Lists pending requests about assets you own and items you deleted, oldest first. No capability is needed.
Two kinds of request appear: requests for access to live assets you
own, and requests to restore items you deleted, whether an asset,
post or collection. A request drops out of the list when its asset
is deleted or its item is restored, even though it’s still pending.
A request on one of your assets that names a capability other than
content.access.request is listed too, but only an approver can
decide it.
Each row has decidable_by_caller. Decide with POST /admin/requests/{id}/decide. Page with limit and offset;
requests made at the same moment have no fixed order between pages,
and total is counted separately, so it can differ from the rows if
requests change in between.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”How many requests to skip, for paging. Defaults to 0.
Responses
Section titled “ Responses ”Pending requests about your assets and the items you deleted.
object
A request and where it stands.
object
What target_id refers to. Access requests are always for an
asset; a restoration request can name an asset, post or
collection.
The id of the item the request is about. It isn’t checked when an access request is filed, so it may not exist.
What the request is for, which also decides who can answer it:
content.access.request: a request to see an asset. The asset’s owner can decide it, as can holders ofshare.grantorsystem.admin. Granting it unlocks nothing.content.restore.request: a request to get a deleted item back. Only whoever deleted the item, or a holder ofsystem.admin, can decide it. Granting it restores the item and grants no capability.- Any other code: a request for that capability across the whole
instance. Only holders of
share.grantorsystem.admincan decide it, and granting it gives the requester that capability.
On the two queues, whether you can decide this request, checked when the list was built. It can change before you act, and the decide call checks again. Left out on other responses.
The requester’s reason, if they gave one.
pending until someone decides it, then granted or denied. When the periodic cleanup removes an expired grant, the server tries to mark its request expired; a request can stay granted if that doesn’t happen. Pending requests don’t expire.
The reason recorded with the decision, if any. When a restoration request is granted for an item that was already back, a note says so here.
The expiry given when the request was granted; left out when there
was none. It describes the grant made at that time: approving a
later request for the same capability replaces that instance-wide
grant and its link to this request, so a request can show granted
after its grant has changed or gone.
How many requests are in this queue, counted separately from items.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}