Identity Management

POST /attach_jwt

Requires authentication with user access token.

Deprecated since version 2.84

Attach third-party (Facebook, Google) login information to an existing user.

This endpoint uses JWT (JSON Web Token) to transfer data.

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

POST /api/2/attach_jwt

jwt

required

Example request

curl
curl https://login.schibsted.com/api/2/attach_jwt \
   -X POST \
   -H "Authorization: Bearer [access token]" \
   -d "jwt={}"

Response

This endpoint supports the JSON response format.

Success: 200 OK

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 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

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.