Transfer seat
Added by Chetana Rachappanavar | Edited by IBM contributorElizabeth Bowling on July 20, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Transfer seat from one subscription to another subscription within the same organization.

Table 1. API details

 

Method
Resource address
Operation header
POST
resource/subscription/<subscription1_id>/seat/<seat_id>?targetSubscription=<subscription2_id>
transferSeat

This operation transfers seat from one subscription to another subscription of same organization and both subscriptions should belong to same offering family.

URL parameters


Provide the following parameter.

Table 2. URL parameters

 

Parameter
Required
Description
subscription1_id
Yes
The ID of the source subscription from which seat needs to be transferred.
seat_id
Yes
Seat ID when entitled to source subscription
subscription2_id
Yes
The ID of the target subscription to which seat needs to be transferred.


Response Codes:

 

Error Code
Possible Error Messages
Reason for Error Message
403
User is not authorized to perform this operation.
User doesn't have necessary privileges to execute this service
404
The seat cannot be transferred because it is currently being entitled
The seat cannot be transferred because it is currently being entitled
400
Either purchase more seats in the target subscription, or remove another subscriber's seat in the target subscription before transferring the seat
The seat cannot be transferred because the target subscription does not have any available seats.
500
Internal Server Error
Any unexpected exception

Example:

URI: resource/subscription/10002/seat/10001?targetSubscription=10003
operation header : transferSeat

Method: POST

Response Code : 204 No Content

 

For a list of common HTTP status codes that are returned for API calls, see HTTP status codes.

Parent topic: Subscription management services