Terms And Conditions

Saves user's approval latest terms and conditions

post
/v1/termsAndConditions

Saves user's signature to latest Obol's terms and conditions hash and it's version

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Header parameters
authorizationstringRequired

EIP712 terms and conditions hash as bearer token

Body
addressstringRequiredExample: v1.0.0
versionnumberRequiredExample: 1
terms_and_conditions_hashstringRequired
fork_versionstring · enumOptionalExample: 0x00000000Possible values:
Responses
201

success message

No content

post
/v1/termsAndConditions
POST /v1/termsAndConditions HTTP/1.1
Host: api.obol.tech
Authorization: Bearer YOUR_SECRET_TOKEN
authorization: text
Content-Type: application/json
Accept: */*
Content-Length: 91

{
  "address": "v1.0.0",
  "version": 1,
  "terms_and_conditions_hash": "",
  "fork_version": "0x00000000"
}

No content

Verify Signature on Terms and Conditions

get
/v1/termsAndConditions/{address}

This endpoint is used to check whether the Terms and Conditions has been signed by the user.

Path parameters
addressstringRequired

The address to check the Terms and Conditions.

Responses
get
/v1/termsAndConditions/{address}
GET /v1/termsAndConditions/{address} HTTP/1.1
Host: api.obol.tech
Accept: */*
{
  "isTermsAndConditionsSigned": true
}

Last updated

Was this helpful?