Skip to content

Transfer team ownership

Open .md

POST/v1/api/store/{team_slug}/setting/user/{hash_id}/make_owner

v1Operation ID v1_public_user_make_owner

Makes another member the team owner. Only the current owner can do this, using their own API key.

The new owner gets every permission and control of YoPrint billing. The previous owner stays on the team with their permission group, and loses the owner's extra rights. Only the new owner can transfer ownership back.

There is no confirmation step: the change applies at once.

Permission

Only the team owner. The route also needs Manage Settings, which the owner always has.

Business rules

  • The caller must be the current owner, and the new owner must already be a member of the team.

Side effects

  • Who can manage YoPrint billing changes: the owner always can.

Path parameters

  • team_slugstringrequired

    Your team slug, shown as Team ID next to your API key in Profile.

    • Example your-team
  • hash_idstringrequired

    The member who becomes the owner. Its hash id from an earlier answer; there is no unique key for it.

    • Example E6LjYJJimQNFVF

Request body

This operation takes no request body.

Response

200Successful response.

Errors

  • 401The API key is missing or wrong (unauthenticated).

  • 403You are not allowed to do this. api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only {"message": "Insufficient Permission"}. Other refusals use the error envelope, with unauthorized or user_is_not_authorized.

  • 404Not found. page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. code: null, with a message that starts "No query results for": there is no record with that id.

  • 500A business rule refused the request (see the operation's errors), or something failed inside YoPrint. Refusals use the error envelope with a code such as action_not_allowed; an unexpected failure answers {"message": "Server Error"}. Repeating a refusal gets the same answer; after an unexpected failure, read the record back before you retry a change.

    When
    You are not the owner, or the person is not a member of the team. Nothing changes. The body is the error envelope with error.code and error.message null.
    Fix
    Call it with the owner's API key, for a member from the members list.

Notes

  • AI apps (MCP connections) can't call this operation: they get 403 agent_operation_not_available. Use a personal API key.