跳到主要内容

approveGuestShareLink

EmployeeFullWrapper approveGuestShareLink(EmailMemberRequestDto)

POST /api/2.0/people/guests/share/approve

Approve a guest sharing link

Accepts a guest that another member shared, which links that guest to the calling account and makes it visible in the caller's list of guests. Everything the operation needs comes from the confirmation token of the link produced by GET api/2.0/people/guests/{userId}/share: the request body is not read at all, so there is nothing to fill in, and an expired or already used token is answered with 401. The caller has to be a room admin or a DocSpace admin; a member or a guest gets 403. The account the token names has to exist and still be a guest, otherwise the operation answers 404 or 400. The call is idempotent: a guest that is already linked to the caller is simply returned again. The answer is the full profile of the guest.

Parameters​

NameInTypeDescriptionNotes
EmailMemberRequestDtobodyEmailMemberRequestDto[optional]

Responses​

Status codeDescriptionTypeResponse headers
200The full profile of the guest now linked to the callerEmployeeFullWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400The account named by the token is not a guest--
403The caller is a member or a guest--
404The account named by the token no longer exists--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

EmployeeFullWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: application/json
  • Accept: application/json