LogoLogo
SDKAPI
Next
Next
  • Learn
    • Introduction
      • Obol Collective
      • OBOL Incentives
      • Key Staking Concepts
      • Obol vs Other DV Implementations
      • Obol Splits
      • DV Launchpad
      • Frequently Asked Questions
    • Charon
      • Introduction to Charon
      • Distributed Key Generation
      • Cluster Configuration
      • Charon Networking
      • CLI Reference
    • Futher Reading
      • Ethereum and Its Relationship With DVT
      • Community Testing
      • Peer Score
      • Useful Links
  • Run a DV
    • Quickstart
      • Quickstart Overview
      • Create a DV Alone
      • Create a DV With a Group
      • Push Metrics to Obol Monitoring
    • Prepare to Run a DV
      • How and Where To Run DVs
      • Deployment Best Practices
      • Test a Cluster
    • Running a DV
      • Activate a DV
      • Update a DV
      • Monitoring Your Node
      • Claim Rewards
      • Exit a DV
    • Partner Integrations
      • Create an EigenLayer DV
      • Create a Lido CSM DV
      • DappNode
  • Advanced & Troubleshooting
    • Advanced Guides
      • Create a DV Using the SDK
      • Migrate an Existing Validator
      • Enable MEV
      • Combine DV Private Key Shares
      • Self-Host a Relay
      • Advanced Docker Configs
      • Beacon node authentication
    • Troubleshooting
      • Errors & Resolutions
      • Handling DKG Failure
      • Client Configuration
      • Test Commands
    • Security
      • Overview
      • Centralization Risks and Mitigation
      • Obol Bug Bounty Program
      • Smart Contract Audit
      • Software Development at Obol
      • Charon Threat Model
      • Contacts
  • Community & Governance
    • Governance
      • Collective Overview
      • The Token House
      • The RAF
      • The OBOL Token
      • Delegate Guide
      • RAF1 Guide
    • Community
      • Staking Mastery Program
      • Techne
    • Contribution & Feedback
      • Filing a Bug Report
      • Documentation Standards
      • Feedback
  • Walkthrough Guides
    • Walkthroughs
      • Walkthrough Guides
  • SDK
    • Intro
    • Enumerations
      • FORK_MAPPING
    • Classes
      • Client
    • Interfaces
      • ClusterDefinition
      • RewardsSplitPayload
    • Type-Aliases
      • BuilderRegistration
      • BuilderRegistrationMessage
      • ClusterCreator
      • ClusterLock
      • ClusterOperator
      • ClusterPayload
      • ClusterValidator
      • DepositData
      • DistributedValidator
      • ETH_ADDRESS
      • OperatorPayload
      • SplitRecipient
      • TotalSplitPayload
    • Functions
      • validateClusterLock
  • API
    • What is this API?
    • System
    • Metrics
    • Cluster Definition
    • Cluster Lock
    • State
    • DV Exit
    • Cluster Effectiveness
    • Terms And Conditions
    • Techne Credentials
    • Address
    • OWR Information
  • Specification
Powered by GitBook
On this page
Edit on GitHub
  1. API

Terms And Conditions

PreviousCluster EffectivenessNextTechne Credentials
  • POSTSaves user's approval latest terms and conditions
  • GETVerify Signature on Terms and Conditions

Verify Signature on Terms and Conditions

get

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
200
This value returns true if the Terms and Conditions have been signed; otherwise, it returns false.
application/json
Responseany of
400
The Address provided is not valid
500
An unknown error occurred
get
GET //v1/termsAndConditions/{address} HTTP/1.1
Host: api.obol.tech
Accept: */*
{
  "isTermsAndConditionsSigned": true
}

Saves user's approval latest terms and conditions

post

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

Authorizations
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
400
Invalid terms and conditions hash
401
Signature verification failed
500
An unknown error occurred
post
POST //v1/termsAndConditions HTTP/1.1
Host: api.obol.tech
Authorization: Bearer JWT
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