Projects and Contracts#

This page explains what each core screen does.

Projects screen#

Use Projects to manage workspace boundaries.

A project contains:

  • Contracts
  • API keys
  • Transactions
  • Stream data
  • Webhooks

Use separate projects for separate products or environments.

Contracts screen#

Use Contracts to define and release business behavior.

Each contract has:

  • Template or custom setup
  • Builder configuration
  • Deployment status
  • Runtime function endpoints

Typical console flow#

  1. Create project
  2. Create contract
  3. Configure builder
  4. Deploy
  5. Call endpoints from Functions

What to copy for runtime calls#

From console, keep these values ready:

  • Project ID
  • Contract ID
  • Runtime API key
  • Function names from Functions tab

What just happened#

  • You created a clear workspace with a project.
  • You added a contract that can be deployed as APIs.
  • You identified the values needed for runtime integration.