Partnerships

Revoke a user membership in a Partnership

Changed on

Delegated Aura access tokens require partnerships:write; missing scope returns 403 FORBIDDEN. Idempotently removes the target user membership from the specified Partnership for an authenticated administrator. The target user and Partnership must already exist. A missing membership is a successful no-op. Only the membership row is removed; the user, Partnership, ListingSource, and historical PartnershipApplication records are preserved. The operation is committed in one PostgreSQL transaction and returns no response body. All success and error responses use Cache-Control: no-store.

delete/api/v1/admin/partnerships/{partnershipId}/members/{userId}

Request

  • Base URL: https://api.stage.aura-historia.com
  • URL: https://api.stage.aura-historia.com/api/v1/admin/partnerships/{partnershipId}/members/{userId}
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

partnershipIdstring required

Stable Partnership ID.

userIdstring required

Existing User ID to remove from the Partnership.

Response

Membership removed, or membership was already absent.

Changes

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • info

      for the path request parameter partnershipId, the format was generalized from uuid to no format

    • info

      for the path request parameter userId, the format was generalized from uuid to no format

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      endpoint added