GET
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
PUT
DELETE
GET
GET
GET
PUT
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
PUT
DELETE
GET
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
POST
GET
GET
PUT
DELETE
GET
GET
GET
PATCH
DELETE
GET
GET
GET
POST
GET
GET
GET
GET
GET
GET
GET
PUT
DELETE
GET
GET
POST
GET
DELETE
GET
POST
GET
POST
GET
GET
PUT
DELETE
GET
POST
GET
POST
GET
PATCH
DELETE
GET
PATCH
GET
GET
POST
POST
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
GET
PUT
DELETE
POST
POST
GET
POST
PUT
DELETE
GET
POST
GET
GET
GET
GET
GET
GET
POST
GET
PATCH
DELETE
POST
GET
GET
GET
PATCH
DELETE
GET
POST
GET
GET
GET
GET
GET
POST
GET
GET
GET
GET
PUT
GET
GET
GET
GET
POST
GET
PUT
DELETE
GET
POST
GET
GET
POST
GET
PATCH
DELETE
GET
This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See "Secondary rate limits" and "Dealing with secondary rate limits" for details.
For more information on permission levels, see "Repository permission levels for an organization".
Note that, if you choose not to pass any parameters, you'll need to set Content-Length
to zero when calling out to this endpoint. For more information, see "HTTP verbs."
The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.
Rate limits
You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.