API & webhooks overview
VipraGo exposes a versioned REST API (/api/v1) and outbound webhooks on Growth and Enterprise plans. Here's the integration model and how to get access during beta.
The API model
- Versioned REST endpoints under /api/v1 covering employees, attendance, leave, payroll runs, reimbursements, projects, and tasks.
- JSON request/response with a consistent envelope; list endpoints support pagination and filtering.
- Authentication: bearer tokens scoped to your organization — multi-tenant isolation is enforced server-side on every query.
Webhooks
- Outbound notifications post JSON to your Slack or Microsoft Teams incoming-webhook URLs, and automation rules can call generic REST webhooks on events (leave approved, payroll published, task moved).
- An inbound GitHub webhook links commits and PRs to task keys for engineering teams — verified with HMAC-SHA256 signatures.
- See the dedicated Webhooks guide for endpoints, payloads, and verification details.
Automation without code
- Rule-based automations (when X then Y) cover common cases — reminders, escalations, scheduled exports — without writing an integration.
- Zapier-style REST webhooks connect VipraGo events to thousands of downstream tools.
Beta access
- API access is included on Growth and Enterprise plans. During open beta, request credentials at support@viprasoftware.com — a public OpenAPI specification and developer portal are on the roadmap.
Tips
- Treat webhook endpoints as untrusted-input handlers: verify signatures and respond 2xx fast, process async.
FAQ
- Is there an OpenAPI spec?
- A public OpenAPI 3.1 specification and interactive reference are in development; beta customers receive endpoint documentation with their credentials.
- Are rate limits applied?
- Yes — tiered rate limits per organization protect the platform; limits and headers are documented with your credentials.