Start a verification process and get an eID initialization reference to complete the process.
A verified request hash signed with your client sign secret.
curl https://login.schibsted.com/api/2/eid/init \ -X POST \ -d "signicatUniqueId=123456789" \ -d "userId=42" \ -d "hash=7374163eed7a0e88f9bf28e128d8da82"
This endpoint supports the JSON response format.
returns eID initialization object
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 Only active users can have eID
- 400 Bad Request ssn is required
- 400 Bad Request userId is required
- 400 Bad Request User is already verified
- 400 Bad Request User is banned from eID
- 400 Bad Request User is blocked for verification
- 400 Bad Request SSN is blocked for verification
- 400 Bad Request SSN is taken by other user
- 400 Bad Request User has been verified with another SSN in the past
- 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 Invalid verification hash
- 403 Forbidden Token is not authorized to access this user
- 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
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.