Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.backed.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Integration Patterns

This page is for teams building around Backed rather than only using the product interface. The safest integrations are the ones that follow the same ordering discipline the platform itself relies on: select the environment, identify the project, read the state, then decide whether action is appropriate. Start from the environment and factory:
  1. resolve the deployment manifest,
  2. resolve the factory address,
  3. enumerate or fetch the target project,
  4. resolve the sale address,
  5. derive current state from the relevant contract reads.
This pattern minimizes the chance that your integration will treat a visible project as if it were already approved or a created sale as if it were already resolved. For any privileged action:
  1. bind the correct environment explicitly,
  2. bind the correct signer explicitly,
  3. read the relevant pre-state,
  4. perform the write,
  5. read the relevant post-state for confirmation.

​
Anti-patterns

  • assuming a UI label is equivalent to contract truth,
  • assuming project creation implies approval,
  • mixing testnet and mainnet assumptions in automation,
  • reading only a single surface when sale state is required.