The Parallax API allows developers to integrate with core platform data related to clients, projects, and opportunities. It is primarily designed to support CRM integrations, enabling systems to push and pull data in and out of Parallax for better visibility and coordination.The API uses standard REST principles, with JSON responses and token-based authentication. It is versioned and designed to expand over time.A timesheet API is planned for future versions, which will support time entry, reporting, and resource planning features.
Parallax Api (v1)
ActualTime
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.
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.
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.
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.
- Mock serverhttps://developer.getparallax.com/_mock/api-documentation/swagger/v1/people
- Production Serverhttps://api.getparallax.com/v1/people
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.getparallax.com/_mock/api-documentation/swagger/v1/people?page=0&page_size=0&archived=true' \
-H 'X-API-KEY: YOUR_API_KEY_HERE'{ "count": 0, "total": 0, "page": 0, "total_pages": 0, "page_size": 0, "results": [ { … } ] }
- application/json-patch+json
- application/json
The capacity of this Person if they are using a custom capacity instead of their Role's capacity.Note: This value can be cleared out by sending null in the request body.
Id of the Role to be used as the primary (default) Role for this person. If null, the unassigned role will be applied instead.
The billable utilization target of this Person if they are using a custom target utilization instead of their Role's target utilization. Note: This value can be cleared out by sending null in the request body.
Denotes whether this Person's time worked is billable. Defaults to true for new records.
The earliest date this Person is available for resourcing on a Project. The Person's capacity prior to this date is 0%.
If this Person will have or has had their employment or contract terminated, this is the last date they are available for resourcing on a project. They will automatically be archived after this date has passed, and their capacity will drop to 0%. This value can be cleared out by sending null in the request body.
A list of tags used to categorize the Person for filtering, reporting, or custom grouping.
- Mock serverhttps://developer.getparallax.com/_mock/api-documentation/swagger/v1/people
- Production Serverhttps://api.getparallax.com/v1/people
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://developer.getparallax.com/_mock/api-documentation/swagger/v1/people \
-H 'Content-Type: application/json-patch+json' \
-H 'X-API-KEY: YOUR_API_KEY_HERE' \
-d '{
"given_name": "string",
"family_name": "string",
"email_address": "string",
"capacity": 0.1,
"role_id": "ac4e70c8-d5be-48af-93eb-760f58fc91a9",
"billable_utilization_target": 0.1,
"billable": true,
"start_date": "2019-08-24",
"end_date": "2019-08-24",
"worker_type": {},
"tags": [
"string"
],
"image_url": "string"
}'Created
The capacity of this Person if they are using a custom capacity instead of their Role's capacity.Note: This value can be cleared out by sending null in the request body.
The billable utilization target of this Person if they are using a custom target utilization instead of their Role's target utilization. Note: This value can be cleared out by sending null in the request body.
The earliest date this Person is available for resourcing on a Project. The Person's capacity prior to this date is 0%.
If this Person will have or has had their employment or contract terminated, this is the last date they are available for resourcing on a project. They will automatically be archived after this date has passed, and their capacity will drop to 0%. This value can be cleared out by sending null in the request body.
A list of tags used to categorize the Person for filtering, reporting, or custom grouping.
The date and time when the Person record was last modified in Parallax.
Indicates whether the Person is archived and no longer active for project assignment or planning.
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "given_name": "string", "family_name": "string", "email_address": "string", "capacity": 0.1, "role_id": "ac4e70c8-d5be-48af-93eb-760f58fc91a9", "billable_utilization_target": 0.1, "billable": true, "start_date": "2019-08-24", "end_date": "2019-08-24", "worker_type": {}, "tags": [ "string" ], "created_date": "2019-08-24T14:15:22Z", "modified_date": "2019-08-24T14:15:22Z", "image_url": "string", "archived": true, "current_cost_rate": { "currency_code": "string", "amount": 0 } }
- Mock serverhttps://developer.getparallax.com/_mock/api-documentation/swagger/v1/people/{id}
- Production Serverhttps://api.getparallax.com/v1/people/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.getparallax.com/_mock/api-documentation/swagger/v1/people/{id}' \
-H 'X-API-KEY: YOUR_API_KEY_HERE'OK
The capacity of this Person if they are using a custom capacity instead of their Role's capacity.Note: This value can be cleared out by sending null in the request body.
The billable utilization target of this Person if they are using a custom target utilization instead of their Role's target utilization. Note: This value can be cleared out by sending null in the request body.
The earliest date this Person is available for resourcing on a Project. The Person's capacity prior to this date is 0%.
If this Person will have or has had their employment or contract terminated, this is the last date they are available for resourcing on a project. They will automatically be archived after this date has passed, and their capacity will drop to 0%. This value can be cleared out by sending null in the request body.
A list of tags used to categorize the Person for filtering, reporting, or custom grouping.
The date and time when the Person record was last modified in Parallax.
Indicates whether the Person is archived and no longer active for project assignment or planning.
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "given_name": "string", "family_name": "string", "email_address": "string", "capacity": 0.1, "role_id": "ac4e70c8-d5be-48af-93eb-760f58fc91a9", "billable_utilization_target": 0.1, "billable": true, "start_date": "2019-08-24", "end_date": "2019-08-24", "worker_type": {}, "tags": [ "string" ], "created_date": "2019-08-24T14:15:22Z", "modified_date": "2019-08-24T14:15:22Z", "image_url": "string", "archived": true, "current_cost_rate": { "currency_code": "string", "amount": 0 } }
ProjectOfferingRoles
A Project Offering Role defines the specific role, resource allocation, and scheduled hours needed within a Service 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.
ProjectOfferings
A Project Offering (Service 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.
Roles
A Role defines the type of work or skill set associated with resource assignments across projects and offerings. Roles are used to categorize resources, shape staffing needs, and support forecasting by identifying which types of personnel are required for each project or service offering.