Identity Management

POST /devices

Requires authentication with user access token.

Endpoint used to store mobile Device Fingerprints for every user log in or sign up actions. As a result it generates device fingerprint hash based on unique device identifier, unified platform name and application name.

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.


POST /api/2/devices



Unique ID of mobile device



Mobile platform name (one of iPad, iPhone or Android)



Name of client application



Version of client application

Example request

Minimal example
curl \
   -X POST \
   -H "Authorization: Bearer [access token]" \
   -d "deviceId=392a0a88-a1ab-4832-b092-5269c8722328" \
   -d "platform=iPhone" \
   -d "applicationName=Sample app"
With all parameters
curl \
   -X POST \
   -H "Authorization: Bearer [access token]" \
   -d "deviceId=392a0a88-a1ab-4832-b092-5269c8722328" \
   -d "platform=iPhone" \
   -d "applicationName=Sample app" \
   -d "applicationVersion=139.83.13"


This endpoint supports the JSON response format.

Success: 201 Created

Device fingerprint created successfully

Device Fingerprint



Generated device fingerprint hash

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 Invalid payload data
  • 401 Unauthorized You don't have administration rights for this client.
  • 401 Unauthorized Your client doesn't have administration rights for this client.
  • 401 Unauthorized Invalid token
  • 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 Unauthorised 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

Sample response

  "hash": "796fb583aec3115cdc4bda02e2ad2e4a25211f8871f54221ede1f4ee28b8d9ce"


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.