Skip to content

Wewed developers

API Reference

The resource and protocol structure reserved for Wewed’s supported public API without exposing undocumented internal endpoints.

Back to Developer Center
API preview

Public endpoint availability

No supported public API base URL is generally available at this time. Paths used internally by wewed.pro are private application implementation details and are not part of this reference until Wewed explicitly documents them as supported.

Resource families

  • Accounts and authorized identities.
  • Wedding workspaces.
  • Wedding memberships and roles.
  • Planner organizations and teams.
  • Vendors and marketplace profiles.
  • Tasks, timelines, budgets and planning resources.
  • Guests and participation data where authorization permits.
  • Subscription metadata when relevant to the authorized account.

Request conventions

  • HTTPS only for supported production access.
  • Versioned requests once a public version is announced.
  • Structured JSON request and response bodies unless an endpoint documents another format.
  • Stable machine-readable error identifiers.
  • Pagination for collection endpoints.
  • Idempotency or equivalent retry protection for consequential write operations where documented.

Privacy boundary

API access must never turn private wedding or guest data into broadly discoverable information. A public API must preserve the same or stricter tenant, wedding, role and resource permissions as the Wewed product.