Actual Time represents the timesheet data capturing the work performed by employees and logged against assigned Project Offerings. Actual Time is used to compare planned vs. actual effort, drive utilization reporting, support variance analysis, and inform project health and forecasting across the platform.
Parallax Api (v1)
Access to the Parallax API is available exclusively to Parallax API customers. To learn more about becoming a Parallax API customer, please reach out to your Customer Success Manager.
All Parallax API calls are made under https://api.getparallax.com and all responses return standard JSON. The following HTTP methods are supported:
- GET
- POST
- PATCH
- DELETE
Download OpenAPI description
Overview
License
Languages
Servers
Mock server
https://developer.getparallax.com/_mock/api-documentation/swagger/
Production Server
https://api.getparallax.com/
| Header | Description |
|---|---|
X-Parallax-Signature | HMAC-SHA256 signature of the payload, prefixed with sha256= |
X-Parallax-Timestamp | Unix timestamp (seconds) when the signature was computed |
- Extract the
X-Parallax-SignatureandX-Parallax-Timestampheaders - Read the raw request body (the JSON payload)
- Concatenate the timestamp and body:
{timestamp}.{body} - Compute HMAC-SHA256 of this string using your webhook secret
- Compare your computed signature to the received signature
- Verify the timestamp is recent (within ~10 minutes) to prevent replay attacks
Regarding replay attacks: Parallax signs the request payload once. The same signature will be used in retries, if applicable.
All webhooks use a consistent envelope structure:
{
"Payload": {
"Id": "497f6eca-6276-4993-bfeb-53cbbbba6f08"
},
"Topic": "project.created",
"CorrelationId": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
"EventOccurredOn": "2025-01-01T12:00:00Z"
}| Field | Description |
|---|---|
Payload | Event-specific data (varies by topic) |
Topic | The event type (e.g., project.created) |
CorrelationId | Unique identifier for this event delivery |
EventOccurredOn | ISO 8601 timestamp when the event occurred |
Clients
A client represents the customer organization associated with one or more projects. Clients serve as the primary entity used to group projects, service offerings, and resource plans, allowing for aggregated reporting on revenue, margin, utilization, and forecasting. Each project is tied to a client, enabling organizations to track work and financial performance at both the individual project and client account levels.
Operations
Departments
A department is used to categorize and group roles within the organization based on functional teams or disciplines. Departments help segment resource capacity, manage utilization targets, and support filtering within reporting and planning workflows. Each role in Parallax belongs to a department for organizational clarity and capacity planning.
Operations
People
People represent the individual resources available for assignment to projects. People are assigned roles, billable capacity, and utilization targets, and can be categorized by worker type, billing type, and department. A Persons record is central to capacity planning, resource allocation, forecasting, and reporting across the platform.
Operations
ProjectOfferingRoles
A Project Offering Role defines the specific role, resource allocation, and scheduled hours needed within a Project Offering. These roles form the basis of the resource plan by identifying the skill sets, timelines, and capacity requirements for successful delivery of the scoped work.
Operations
ProjectOfferings
A Project Offering represents a distinct scope or phase of work within a Project. Each Project Offering contains resource plans, financial models, and revenue data, allowing organizations to model different work types and billing structures within a single project. Offerings help align sales, delivery, and operations teams around specific scopes of work and resourcing needs.
Operations
WebhookSubscribers
Webhook configurations enable organizations to receive real-time event notifications via HTTP callbacks. Organizations can configure a single webhook endpoint to receive notifications about events such as project or offering, creation or changes. Each webhook includes a secret key for validating the authenticity of incoming requests.Only one Webhook Subscriber is currently allowed per organization.
Operations