Identity Management

GET /anonymous/users

Requires authentication with server access token.

Deprecated since version 2.84

Retrieve an anonymized list of users that was created or updated in the given period. Users that have been removed will be returned as an object with just the id and deleted set to true.

Pagination parameters since and until default to "yesterday" and "today", respectively.

NB! Do not use until=NOW with pagination, as the paginated sequence will never end.

Anonymous user data

The data returned from this endpoint is pulled from users' public profiles, and except for the uid (which is the user's userId), no data can be used to uniquely identify users. As such, this data is suitable for aggregating into user segments.

Note that most clients can use the data returned to retrieve full user profiles from the GET /user/{userId} endpoint. The purpose of the anonymized form of the returned data in this endpoint is that it can be freely used in further calculations without fear of compromising your user's identity - so long as the uid is removed first.

See also

Help us improve

Did you spot an error? Or maybe you just have a suggestion for how we can improve? Leave us a comment.

Request

GET /api/2/anonymous/users

The pagination parameters since, until, and offset are also supported.

Example request

curl
curl https://login.schibsted.com/api/2/anonymous/users -G \
   -H "Authorization: Bearer [access token]"

Response

This endpoint supports the JSON response format.

Success: 200 OK

Returns a list of anonymized user data

Anonymized user data

uid ✓

integer (as string)

The user's userId

gender

string

yob

string

The user's year of birth, four digits

post

string

The user's zip code/postal code

country

string

city

string

deleted

boolean

true if user is deleted. When that is the case, only this field and the uid will be returned.

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

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.

  • 400 Bad Request Required client ID missing
  • 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 Schibsted account to request access.
  • 403 Forbidden Requesting IP is not whitelisted
  • 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

Sample response

JSON
[
  {
    "uid": "236900",
    "gender": "M",
    "yob": "1984",
    "post": "",
    "country": "",
    "city": ""
  }
]

Comments/feedback

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