Runvello developer platform

Connect your systems to the client work already in Runvello.

Use a tenant-scoped JSON API to integrate CRM, scheduling, project, contract, campaign, and billing workflows without exposing data across workspaces.

Quickstart

Make your first request

Generate a least-privilege token from Admin → API access, store it on your server, and call the workspace host that issued it.

Server-side only
curl --request GET \
  --url "https://your-workspace.runvello.com/api/v1/clients?page=1&per_page=25" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer $RUNVELLO_API_TOKEN"

React security: the component calls an application-owned server route. The server—not the browser—adds the Runvello bearer token.

Authentication

Every credential belongs to one workspace.

Send the token in the Authorization header over HTTPS. Raw tokens are shown once and stored by Runvello only as SHA-256 digests.

01

Create one token per integration

Descriptive names, independent expiration dates, and separate activity make rotation and incident response safer.

02

Choose the smallest scopes

Read and write scopes are separate. Contracts, invoices, campaigns, projects, and tasks remain read-only.

03

Keep tokens server-side

Never place a token in browser JavaScript, a mobile bundle, URL, log, screenshot, or source-control history.

Resources

API coverage across the client lifecycle

All collection endpoints are paginated unless the reference explicitly documents a compatibility exception.

CRM

Clients, people, and leads

Read and safely create or update customer records. Preview and execute lead conversion with a dedicated scope.

Scheduling

Bookings

Read, create, and update bookings while retaining plan limits and tenant-safe relationship checks.

Work

Projects and tasks

Read project delivery state, project tasks, and standalone work without exposing cross-workspace records.

Finance

Contracts, invoices, and time

Read signed-work and billing context. Financial writes remain deliberately unavailable.

Marketing

Email campaigns

Read campaign configuration and delivery status without allowing remote campaign mutation.

Errors and reliability

Predictable responses for production clients

Error bodies are JSON. Retry throttling and transient server errors with exponential backoff; do not retry validation failures without changing the request.

400
Malformed or missing parameters
401
Missing, invalid, expired, or revoked token
403
Plan entitlement or scope denied
404
Resource not found in this workspace
422
Validation failed
429
Request rate exceeded
503
Workspace data temporarily unavailable

Ready to integrate?

Use the contract that fits your workflow.

Explore the browser reference, import one Postman collection, or download the canonical OpenAPI specification.