Home

Awesome

Build Status

You can read the documentation at apiary

Blobvault v1

Welcome to the Blobvault v1 API. This API provides access to the Ripple Blobvaut.

Blobvault Links

There are three types of signing, HMAC-RECOV, HMAC and ECDSA

Group ECDSA-RECOV signing

This signature is specifically for account recovery. Applicable for requesting the encrypted blob and the encrypted_blobdecrypt_key

GET /your/path{?signature,signature_date,signature_type,signature_username}

Group ECDSA Signing

example:'https://id.staging.ripple.com/v1/user?signature=AAAAHC2k5dWAnmC7zXr2N0ZEDbiF0kNQxHgf1xS-bixub5pmQFo-SMcDe0U-n6jkGaFrKfOn7NAlraTogHISkdzyUDY&signature_date=2014-05-19T17:21:34.000Z&signature_blob_id=92da7f762e240b40c23c1f15c55cee6f488c8cc8adfea079d5e738b5b152ab2b&signature_account=rfaPezp7ShpR2c89J3pZehnXHmSKd85MCY&signature_type=RIPPLE1-ECDSA-SHA512'

In this example we just use GET but it applies to any HTTP Method (GET, POST) that is marked as using ECDSA

GET /your/path{?signature_account,signature_type,signature,signature_date,signature_blob_id}

Group HMAC Signing

In this example we use GET but it can apply to any HTTP Method for any route marked using HMAC

GET /your/path{?signature,signature_blob_id,signature_date}

Group Creating a user - uses ECDSA

POST /v1/user

Group Deleting a user - uses ECDSA

example: DELETE /v1/user/foo will delete user foo

DELETE /v1/user/{username}

Group Looking up a user - by username

GET /v1/user/{username}

Group Looking up a user - by address

GET /v1/user/{address}

Group Looking up a user via querstring

Example: /v1/authinfo?username=foo

GET /v1/authinfo{?username}

Group 2FA - Setting Two Factor Authentication 2FA Settings - uses ECDSA

POST /v1/blob/{blob_id}/2FA

Group 2FA - Getting Two Factor Authentication 2FA Settings - uses ECDSA

GET /v1/blob/{blob_id}/2FA{?device_id}

Ex. /v1/blob/<blobid>/2FA?device_id=57261be82601452ada0f2795bc709734

Group 2FA - Request 2FA Token

This is not a signed request but requires the blob id. No device ID required.

GET /v1/blob/{blob_id}/2fa/requestToken

Group 2FA - Verify Device Token

This is not a signed request but requires the blob id. Client supplies device ID.

POST /v1/blob/{blob_id}/2fa/verifyToken

Group Recovering a user blob - uses ECDSA-RECOV

GET /v1/user/recov/{username}

Group Setting a user blob and fields - uses ECDSA

This is meant to be used for either resetting the blob after client blob recovery, or this can be used password change, where all the listed fields in the request must be changed.

Since this endpoint changes the blob_id, please note to use the old blob_id for the ECDSA signature.

POST /v1/user/{username}/updatekeys

Group Renaming a user - uses ECDSA

Since this endpoint changes the blob_id, please note to use the old blob_id for the ECDSA signature.

POST /v1/user/{username}/rename

Group Changing email address - uses ECDSA

POST /v1/user/email

Group Resending Email - uses ECDSA

POST /v1/user/email/resend

Group Verifying Email Token

GET /v1/user/{username}/verify/{token}

Group Requesting Phone Token

POST /v1/user/{username}/phone

Group Validating Phone Token

POST /v1/user/{username}/phone/validate

Group Adding Profile Detail - uses HMAC

Choose any number of the following to add

POST /v1/user/{username}/profile

Group Retrieve a blob

GET /v1/blob/{blob_id}{?device_id}

Group Add a blob patch - uses HMAC

POST /v1/blob/patch

Group Get a blob Patch

GET /v1/blob/{blob_id}/patch/{patch_id}

Group Consolidate a set of blob patches - uses HMAC

POST /v1/blob/consolidate

Group Service Health

GET /health