Roles

Reject Join Request

Turn a pending join request down. Nobody gains access.

Published although its twin approve is not, for the same reason DELETE /roles/pending-invites/{email} is: this direction only ever REFUSES access, and the direction that admits a person - possibly at an Owner or Admin role - is the one that needs a human.

400 when the request is no longer pending; 404 when it is not this organisation's.

post/roles/join-requests/{request_id}/reject

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/roles/join-requests/{request_id}/reject
  • Auth: HTTP bearer

Path parameters

request_idstring required

Join request id (UUID).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataOrgPayload required

An open envelope for a single role, team, member or account record.

Open on purpose. The app's own response models on this surface grow with the product - RoleResponse gained rep_limits and manages_role_slugs, TeamResponse gained channel counts and a campaign count - and a pinned mirror would SILENTLY DROP whatever it had not caught up on. A dropped permission in a role read is the worst possible kind of stale: it reads as "they do not have it".

Changes

No recorded changes to this operation across all 2 revisions of this API.