Vora API - Overview for Developers

Internal Public
🔗 Developers & API 42 views Updated 1 month ago

Vora API for Developers

Vora exposes a REST API so you can build on top of your space: read proposals and results, manage idea challenges, and integrate voting into your own tools. This page is the starting point; the full, always-current endpoint reference is the live interactive schema linked below.

Base URL

https://api.voiceofthenewera.com/api/v1

Interactive API reference (always current)

The complete endpoint list, request and response shapes, and a "try it" console are generated directly from the running API:

  • Swagger UI: https://api.voiceofthenewera.com/api/docs/
  • ReDoc: https://api.voiceofthenewera.com/api/redoc/
  • OpenAPI schema (JSON): https://api.voiceofthenewera.com/api/schema/

Because these are generated from the live service, they never go stale.

Authentication

Vora supports two ways to authenticate, depending on what you are building.

1. User access tokens (JWT)

For actions taken on behalf of a logged-in user. Obtain a token pair from the auth endpoints, then send it as a Bearer token:

Authorization: Bearer <access_token>

Access tokens are short lived; use the refresh token to get a new one.

2. Space API keys (server to server)

For integrations that act for a space rather than a person, use an API key sent in the X-API-Key header:

X-API-Key: <your_key>

There are two kinds of key, and the difference matters:

  • Public read key: read-only access to your space's public data. It can never write.
  • Management key (prefix cathedral_mgmt_): a secret, write-scoped key that lets a Pro space manage idea challenges and proposals. Generate and rotate it yourself in Settings. Keep it secret; treat it like a password.

If a request that should write comes back 401, you are almost certainly using the public read key where a management key is required.

Rate limits

Public endpoints are throttled to protect the platform. If you exceed a limit you will receive HTTP 429; back off and retry. Design integrations to be idempotent where possible.

A quick example

Read the published proposals for a space (public, read-only):

curl -H "X-API-Key: <public_read_key>" \
  https://api.voiceofthenewera.com/api/v1/spaces/<your-space-slug>/proposals/

Where to go next

  • Browse the live Swagger reference for every endpoint: https://api.voiceofthenewera.com/api/docs/
  • Not sure which key you need, or how to enable API access on your plan? Ask the Vora Support Assistant in the Support Center, or email hello@voiceofthenewera.com.

On This Page