Asset ID

GET /user/{id}/assets/{assetIds}

Requires authentication with server or user access token.

Get asset-access objects by user id and list of asset ids. Will be available in version 2.71.1.

See also

Assets guide

Request

GET /api/2/user/{id}/assets/{assetIds}

id

required path parameter

ID of the user to associate data with

assetIds

required path parameter

The comma-separated asset ids. Max length is 255 bytes.

Example request

cURL
curl https://login.schibsted.com/api/2/user/1337/assets/vg-pluss-william-slutter-i-skam,vg-pluss-martha-og-englene -G \
   -d "oauth_token=[access token]"
Java
SpidOAuthToken token = spidClient.getUserToken(code);
String responseJSON = spidClient.
    GET(token, "/user/1337/assets/vg-pluss-william-slutter-i-skam,vg-pluss-martha-og-englene").
    getResponseBody();

This example is an excerpt, see a full example

PHP
<?php
$client->auth();
echo var_dump($client->api("/user/1337/assets/vg-pluss-william-slutter-i-skam,vg-pluss-martha-og-englene"));

This example is an excerpt, see a full example

Clojure
(ns example
  (:require [spid-client-clojure.core :as spid]))

(let [client (spid/create-client "[client-id]" "[secret]")
      token (spid/create-user-token client "[code]")]
  (spid/GET client token "/user/1337/assets/vg-pluss-william-slutter-i-skam,vg-pluss-martha-og-englene"))

Response

This endpoint supports the JSON response format.

Success: 200 OK

Returns array with assets user has access to

Asset Access

Defines user access to the asset.

merchantId

integer (as string)

The ID of the merchant the client belongs to

uuid

string

User identifier

userId

integer (as string)

User identifier

assetId

assetId

Asset identifier

accessUntil

date-time

Access expiration date

status

Asset Access status

Asset access current status

updated

date-time

The time the access was last updated

created

date-time

The time the access was created

The check mark indicates that the field always contains a valid non-empty value.

Asset Access status

An enum, with the following possible values:

"0"

Deleted

"1"

Active

Failure cases

Some HTTP response codes are used for multiple error situations. There is no consistent way to tell these apart, but the error object will contain a textual explanation of the reason for the error. For explanation on OAuth related failures and errors see OAuth authentication failures.

  • 401 Unauthorized You don't have administration rights for this client.
  • 401 Unauthorized Your client doesn't have administration rights for this client.
  • 403 Forbidden Client is not authorized to access this API endpoint. Contact SPiD to request access.
  • 403 Forbidden Requesting IP is not whitelisted
  • 403 Forbidden User does not have access
  • 403 Forbidden Access token rejected
  • 404 Not Found Unknown client ID
  • 404 Not Found Client ID mismatch. The client making the request is no the owner of this resource, and does not have administrative privileges for it.
  • 420 Request Ratelimit exceeded

Comments/feedback

Do you have questions, or just want to contribute some newly gained insight? Want to share an example? Please leave a comment. SPiD reads and responds to every question. Additionally, your experience can help others using SPiD, and it can help us continuously improve our documentation.