Page cover

API Overview

API Overview

CRE8 likely exposes RESTful APIs that allow authorized access to various functionalities:

  • Authentication API: to manage user auth for API usage (could be via API keys or OAuth). Alternatively, since CRE8 is Web3, authentication might involve signing a message with a wallet to then receive a JWT for subsequent calls.

  • Listings API: endpoints to create and manage service listings. This would cover creating a new service (which might trigger token minting on-chain), updating details, or fetching listings.

  • Marketplace API: endpoints to search or fetch available service tokens. E.g., GET /api/v1/marketplace/listings?category=design&status=active could return all active design listings.

  • Purchase/Order API: endpoints to initiate a purchase (though final payment is on-chain, the API can coordinate off-chain parts like creating an order record or providing necessary data for the transaction). For instance, POST /api/v1/orders with payload including listing_id and buyer info might return a structured transaction for the buyer to sign or a reference to track the escrow.

  • Escrow API: endpoints to check status of escrows or release conditions. GET /api/v1/orders/{order_id} might return the status (e.g., “in_escrow”, “dispute”, “completed”, etc.) and relevant addresses.

  • Chat API: Possibly websockets or REST endpoints for sending/receiving messages if exposing that to external integrations (maybe not open to third-party for privacy reasons, unless the user provides their token).

  • Review API: endpoints for submitting and retrieving reviews programmatically, for use cases like external reputation aggregators.

  • User Profile API: to fetch profile info of a user (public stats, reputation, etc.) by wallet or user ID.

  • Wallet/Payments API: possibly endpoints to initiate deposits/withdrawals if they have a custodial element or to retrieve current token balances (though those could also be read on-chain directly by the developer using Solana RPCs).

  • SDK usage often wraps these API calls and on-chain interactions to simplify tasks.

Last updated