How a refresh went

GET

/v1/refreshes/{id}

const url = 'https://api.sotirea.com/v1/refreshes/example';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.sotirea.com/v1/refreshes/example \
  --header 'Authorization: Bearer <token>'

Authorizations

bearer

Parameters

Path Parameters

required

string

The refresh’s id, as RefreshVault answered.

Responses

200

Done.

application/json

object

data

required

object

chain_id

required

string

completed_at

required

Any of:

string
null

string format: date-time

discrepancies

required

How many it found different from what Sotirea had counted.

integer

required

Follow it with GET /v1/refreshes/{id}.

string

requested_at

required

string format: date-time

status

required

Requested until the network has answered, then answered; failed if it could not be asked, expired if it never answered.

string

targets

required

How many addresses it asked about.

integer

meta

object

request_id

Quote it when asking about a request; it is in the X-Request-Id header too.

string

success

required

Example

{
  "success": true
}

default

Refused or failed, in words a person can act on.

application/json

object

error

required

object

code

required

string

fields

object

key

additional properties

string

message

required

string

meta

object

request_id

Quote it when asking about a request.

string

success

required

Example

{
  "success": false
}