Push Projects to a PSA Using the V2 API
Use the public V2 API to push a ScopeStack project to ConnectWise Manage, Autotask, or HaloPSA. Use an active access token for the account that owns the project and the ID of a PSA connection in that account. See API Quick Start for help getting a token.
Start a push
Send POST /v2/projects/{project_id}/psa-project once per ScopeStack project.
Use PATCH to retry a saved push.
To find the connection ID, go to Settings > Account > Connected Apps in ScopeStack and open your PSA connection.
Copy the ID after /manage/ in the browser address and use it in data.relationships.account-connection.data.id.
Use YYYY-MM-DD for the required start-on and end-on dates.
The keys and values in project-options depend on your PSA and the type of export.
Set import to new to create a project in the PSA, existing to push into the PSA project named by project_id, or service_ticket for a ConnectWise service-ticket export. The company, board, status, priority, and project_type values are IDs from your PSA.
- ConnectWise Manage. To create a project, set
importtonewand use the ConnectWise company ID forcompanyand project board ID forboard. - Autotask. Use the Autotask company ID for
companyand the Autotask picklist values forproject_typeandstatus. - HaloPSA. To create a project, set
importtonewand use the HaloPSA client ID forcompany, the status ID forstatus, and the priority ID forpriority.
For more options, see the v2_PsaProjectOptions schema in the V2 API reference .
This example queues the creation of a ConnectWise project. Replace the ScopeStack project ID, access token, dates, ConnectWise company and board IDs, and ScopeStack connection ID with your own values.
POST https://api.scopestack.io/v2/projects/100000001/psa-project
Authorization: Bearer YOUR_ACCESS_TOKEN
Accept: application/vnd.api+json
Content-Type: application/vnd.api+json
{
"data": {
"type": "psa-projects",
"attributes": {
"start-on": "2026-12-01",
"end-on": "2026-12-08",
"project-options": {
"import": "new",
"company": "250",
"board": "3"
}
},
"relationships": {
"account-connection": {
"data": {
"type": "account-connections",
"id": "400000004"
}
}
}
}
}ScopeStack returns HTTP 201 Created when it saves the record and queues the push. The push runs in the background.
The POST response includes the new ScopeStack PSA project record ID, shown in this excerpt.
{
"data": {
"type": "psa-projects",
"id": "200000002"
}
}If you get 401 Unauthorized, check that the request uses an active access token.
POST returns 422 Unprocessable Entity if a required date is blank or the connection belongs to another account.
Resubmit a push with PATCH
Send GET /v2/projects/100000001/psa-project to check for a saved push record.
The GET response has a data array with at most one record.
An empty array means ScopeStack has no saved PSA project record for this project.
This GET response excerpt shows a saved record with a linked PSA project.
{
"data": [
{
"type": "psa-projects",
"id": "200000002",
"attributes": {
"project-id": "300000003"
}
}
]
}100000001stays in the URL as the ScopeStack project ID.200000002is the ScopeStack PSA project record ID to copy from GETdata[0].idinto PATCHdata.id.300000003is the PSA’s project ID in the read-onlydata[0].attributes.project-idfield.
Warning: If the saved project-options.import is new and there is no linked CRM opportunity, PATCH can create another project in the PSA.
In that case, check the PSA before retrying.
If the project already exists and you want to keep it, skip PATCH and make any remaining changes in the PSA.
A resubmit to a linked PSA project can also add missing services, remove services no longer on the ScopeStack project, and update existing services.
After the previous push finishes, address any reported error before you retry.
Send a single data object with an empty attributes object to retry with the saved settings.
Replace the example IDs and token with your own values.
PATCH https://api.scopestack.io/v2/projects/100000001/psa-project
Authorization: Bearer YOUR_ACCESS_TOKEN
Accept: application/vnd.api+json
Content-Type: application/vnd.api+json
{
"data": {
"type": "psa-projects",
"id": "200000002",
"attributes": {}
}
}ScopeStack returns HTTP 200 OK when it accepts the PATCH, clears the saved error, and queues another push.
PATCH returns 422 Unprocessable Entity if a required date is blank or the request changes project-options.subtasks, the setting for how services and subservices become PSA items.
Check the push result
Send the same GET again and read attributes.error-message for any saved push error.
The presence of project-id confirms a link to a PSA project. ScopeStack can set that ID before it finishes exporting phases and work items.
The GET response has no field that marks the push as finished. To confirm a finished export, check the activity log below or open the project in your PSA.
To review the export, open Settings > Account > Connected Apps and select the PSA connection. You need Connected Apps at Manage to see the activity log.
On this screen: The Integration Activity tab lists Time and Activity. Find the entry by time and ScopeStack project ID. Use it to see which export steps ran and read any errors.
Open the linked project in your PSA to confirm the expected phases and work items are there. For a ConnectWise service-ticket export, check for the expected tickets on the service board.
New to ScopeStack?
ScopeStack automates scoping, pricing, and SOW generation for IT services teams. See how it fits your process.