Invites
DELETE
invites/{inviteId}/invitees/{inviteeId}
Deletes an invitee from an invite.
If the invitee being deleted is the invite’s only invitee and the invite is in the NOT_INVITED state, then the invite itself will be deleted. When the invite is not in the NOT_INVITED state (i.e. the invite has already been sent to the bidder company), then the invite cannot be deleted. Even deleting all the invite’s invitees will not delete the invite itself.
Resource Information
| Method and URI | DELETE https://developer.api.autodesk.com/construction/buildingconnected/v2/invites/{inviteId}/invitees/{inviteeId} |
| Authentication Context | User context required |
| Required OAuth Scopes | data:write |
| Data Format | JSON |
Request
Headers
| Authorization* string | Must be Bearer <token>, where <token> is a three-legged access token obtained via an Authorization Code flow. |
* Required
Request
URI Parameters
| inviteId string | The ID of the invite. |
| inviteeId string | The ID of the invitee. |
Response
HTTP Status Code Summary
| 204 No Content | No Content |
| 400 Bad Request | The parameters of the requested operation are invalid. |
| 401 Unauthorized | The provided bearer token is not valid. |
| 403 Forbidden | The user or service represented by the bearer token does not have permission to perform this operation. |
| 404 Not Found | The requested resource could not be found. |
| 429 Too Many Requests | Rate limit exceeded; wait some time before retrying. The ‘Retry-After’ header might provide the amount of the time to wait. |
| 500 Internal Server Error | An unknown error occurred on the server. |
Response
Body Structure (204)
Response for 204 has no body.
Example
No Content
Request
curl -v 'https://developer.api.autodesk.com/construction/buildingconnected/v2/invites/:inviteId/invitees/:inviteeId' \
-X 'DELETE' \
-H 'Authorization: Bearer AuIPTf4KYLTYGVnOHQ0cuolwCW2a'
Response
204 No Content