Bitbond Documentation
About BitbondAPI documentation
Search…
Introduction
Operating model
Offering Manager
Intro Offering Manager
Protocols and blockchains
Admin user accounts
Offerings
Investors
Orders
Labs
Configuration
Payments
Token custody
Email communication
Offering Manager API
Token Tool
Intro Token Tool
Create Token
Manage Token
Distribute Token
Create Token Sale
Manage Token Sale
Create Token Locker
Create NFT
Distribute NFT
Investor UI
Intro Investor UI
Powered By GitBook
Configuration
The configuration page is used to apply settings to the Offering Manager setup.

General Settings

Time zone sets the system time zone. This time zone is also used for the time stamp of Registrar snapshots.

Webhooks

Webhook URLs can be added by clicking on the "Add New" link. The Bitbond API will automatically retry a webhook if the response status code will be anything other than 200. Webhooks are called with payload in POST request body when the following events happen:
  • order_created
    • Is triggered when the endpoint POST /users/:user_id/projects/:project_id/orders is used and after a new order is successfully created.
  • order_fulfilled
    • Is triggered when the endpoint POST /admin/investments/:id/allocate is used and after the investment is successfully allocated in the system.
    • Is triggered when a bank payment transaction is received by the bank and after new investment is successfully allocated in the system.
    • Is triggered when admin user is seeding test environment with test investment data using Asset Manager Labs section (does not apply to production)
  • order_cancelled
    • Is triggered when admin user cancels the order in Asset Manager
  • investment_received
    • Is triggered automatically when investment funds are received on BVDH bank account
    • Is triggered when admin user manually allocates the investment in the Asset Manager
    • Is triggered when admin user is seeding test environment with test investment data using Asset Manager Labs section (does not apply to production)
  • kyc_video_identification_success
    • Is triggered after the investor goes through a successful IDnow KYC process.
    • Is triggered when KYC process is mocked using Asset Manager Labs section (does not apply to production)
  • kyc_approved
    • Is triggered after a successful auto-approval process when the investor finishes the KYC process.
  • kyc_rejected
    • Is triggered when admin user rejects the investor in Asset Manager
  • distribution_created
    • Is triggered when distribution to Blockchain was processed.
  • transaction_created (WIP)
Offering Manager - Previous
Labs
Next - Offering Manager
Payments
Last modified 6mo ago
Copy link
Outline
General Settings
Webhooks