​

PUT (/json/users/xuid()/scids//data/,json)

Uploads a file. Multi-block upload is not supported for data of type json. The domain for these URIs is titlestorage.xboxlive.com.

• URI parameters
• Authorization
• Optional Query String Parameters
• Required Request Headers
• Optional Request Headers
• Request body
• HTTP status codes
• Response body

​

URI parameters

​

Authorization

The request must include a valid XBOX LIVE authorization header. If caller is not allowed to access this resource, the service will return a 403 Forbidden response. If the header is invalid or missing, the service will return a 401 Unauthorized response.

​

Optional Query String Parameters

| Parameter| Type| Description| | --- | --- | --- | --- | --- | --- | | clientFileTime| DateTime| Date/Time of the file on whatever client last uploaded the file.| | displayName| string| Name of the file that should be shown to the user.|

​

Required Request Headers

| Header| Value| Description| | --- | --- | --- | --- | --- | --- | --- | --- | --- | | x-xbl-contract-version| 1| API contract version.| | Authorization| XBL3.0 x=[hash];[token]| STS authentication token. STSTokenString is replaced by the token returned by the authentication request. See Authenticating and Authorizing XBOX LIVE Services Requests for additional information about retrieving an STS token and creating an authorization header.|

​

Optional Request Headers

| Header| Description| | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | If-Match| Specifies an ETag that must match an exisitng item to complete the operation.| | If-None-Match| Specifies an ETag that must not match any exisitng items to complete the operation.|

​

Request body

The request body contains the complete contents of the file being uploaded.

​

HTTP status codes

The service returns one of the status codes in this section in response to a request made with this method on this resource. For a complete list of standard HTTP status codes used with XBOX Live Services, see Standard HTTP status codes. | Code| Reason phrase| Description| | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 200| OK | The request was successful.| | 201| Created | The entity was created.| | 400| Bad Request | Service could not understand malformed request. Typically an invalid parameter.| | 401| Unauthorized | The request requires user authentication.| | 403| Forbidden | The request is not allowed for the user or service.| | 404| Not Found | The specified resource could not be found.| | 406| Not Acceptable | Resource version is not supported.| | 408| Request Timeout | The request took too long to complete.| | 500| Internal Server Error | The server encountered an unexpected condition which prevented it from fulfilling the request.| | 503| Service Unavailable | Request has been throttled, try the request again after the client-retry value in seconds (e.g. 5 seconds later).|

​

Response body

If the upload is successful, a 201 is returned with a response.

​

See also

Parent

/json/users/xuid()/scids//data/,json