Office API#

Novaza Office exposes a REST API for programmatic access to namespaces, modules, records, workflows, and pages. The API is served directly by the Office product at https://office.novaza.ai and is not proxied through the Novaza Platform Gateway.

Access and Authentication#

Because the Office API is served by the product directly, it has its own authentication handshake that is separate from the Platform Gateway at api.novaza.ai. Clients must obtain an Office access token before calling Office API endpoints.

  • Base URL: https://office.novaza.ai
  • Authentication: OAuth2 Authorization Code flow against Novaza SSO (id.novaza.ai)
  • Token header: Authorization: Bearer <access_token>
  • Requires separate auth: a JWT issued for api.novaza.ai cannot be reused here; exchange via Novaza SSO for an Office-scoped token.

See API Authentication for the OAuth2 flow and token exchange details.

What You Can Do#

The Office API supports the same actions that are available in the Office user interface, including:

  • Listing namespaces, modules, and pages that the authenticated user can access
  • Reading, creating, updating, and deleting records
  • Filtering and searching records
  • Triggering manual workflows
  • Uploading file attachments

API Reference#

For the complete endpoint list, request/response schemas, and parameter documentation, see the Office product’s own API reference available from within the Office application:

Office → Admin → Developer → API Reference

The in-product reference is always in sync with the version of Office deployed to your workspace and includes an interactive request console for testing calls against your live data.

Example: Authenticated Request#

GET /... HTTP/1.1
Host: office.novaza.ai
Authorization: Bearer <office_access_token>
Accept: application/json
Backward API Authentication Platform Gateway API Forward

© 2026 Novaza. All rights reserved.