Team, invitations and transfers
Who works on an application, how they are invited, and how ownership moves.
12 routes
Roles are owner, admin, developer, viewer and billing. Ownership is never given by invitation; it moves by a transfer the new owner accepts with a passkey.
The guide for this family is Teams and ownership.
GET /v1/developer/application-invitations/{token}
GET /v1/developer/application-invitations/{token}Authentication- Developer console session
Sends the invitation again with a new 7-day link; the previous link stops working.
POST /v1/developer/application-invitations/{token}/accept
POST /v1/developer/application-invitations/{token}/acceptAuthentication- Developer console session
GET /v1/developer/application-transfers
GET /v1/developer/application-transfersAuthentication- Developer console session
POST /v1/developer/application-transfers/{transferId}/accept
POST /v1/developer/application-transfers/{transferId}/acceptAuthentication- Developer console session
POST /v1/developer/application-transfers/{transferId}/decline
POST /v1/developer/application-transfers/{transferId}/declineAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/invitations
POST /v1/developer/applications/{applicationId}/invitationsAuthentication- Developer console session
DELETE /v1/developer/applications/{applicationId}/invitations/{invitationId}
DELETE /v1/developer/applications/{applicationId}/invitations/{invitationId}Authentication- Developer console session
POST /v1/developer/applications/{applicationId}/invitations/{invitationId}/resend
POST /v1/developer/applications/{applicationId}/invitations/{invitationId}/resendAuthentication- Developer console session
Sends the invitation again with a new 7-day link; the previous link stops working.
DELETE /v1/developer/applications/{applicationId}/members/{memberId}
DELETE /v1/developer/applications/{applicationId}/members/{memberId}Authentication- Developer console session
PATCH /v1/developer/applications/{applicationId}/members/{memberId}
PATCH /v1/developer/applications/{applicationId}/members/{memberId}Authentication- Developer console session
GET /v1/developer/applications/{applicationId}/members/{memberId}/profile-photo
GET /v1/developer/applications/{applicationId}/members/{memberId}/profile-photoAuthentication- Developer console session
GET /v1/developer/applications/{applicationId}/team
GET /v1/developer/applications/{applicationId}/teamAuthentication- Developer console session
What this does not do
- Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
- This page is generated. It was read from the API at commit
234dba22. Editing it by hand changes nothing; the next sync overwrites it.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.