TeamGriddeveloper
v1.0.6Status
TeamGriddeveloper
TeamGrid Developer

API v0 to v1 route matrix

Filter all 87 frozen API v0 runtime routes by migration class and open the exact API v1 replacement where one exists.

87 frozen v0 routes37 equivalent49 adaptation required1 retained on v0

Route matrix

Search by method, path, operation ID, or migration change. A replacement is “equivalent” only at the product-capability level; v1 authentication, regional routing, envelopes, and errors still apply exactly as documented.

87 routes shown

API v0 routeClassificationAPI v1 replacementRequired changes
GET /v0_get · supportedadaptation-requiredGET /getApiVersion
1 documented change
  • Consume the documented API v1 resource envelope and error model.
GET /calendar/{token}.icsv0_get_calendar_token_ics · supportedretained-v0No public v1 replacement
1 documented change
  • Calendar token feeds remain on API v0 until the calendar domain is released in v1.
DELETE /callnotesv0_delete_callnotes · deprecated-aliasadaptation-requiredDELETE /call-notes/{id}archiveCallNote
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /callnotesv0_get_callnotes · supportedequivalentGET /call-noteslistCallNotes
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /callnotesv0_post_callnotes · supportedequivalentPOST /call-notescreateCallNote
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
DELETE /callnotes/{_id}v0_delete_callnotes_id · supportedadaptation-requiredDELETE /call-notes/{id}archiveCallNote
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /callnotes/{_id}v0_get_callnotes_id · supportedequivalentGET /call-notes/{id}getCallNote
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
DELETE /contactgroupsv0_delete_contactgroups · unavailableadaptation-requiredDELETE /contact-groups/{id}archiveContactGroup
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /contactgroupsv0_get_contactgroups · supportedequivalentGET /contact-groupslistContactGroups
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /contactgroupsv0_post_contactgroups · unavailableequivalentPOST /contact-groupscreateContactGroup
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
PUT /contactgroupsv0_put_contactgroups · unavailableadaptation-requiredPATCH /contact-groups/{id}updateContactGroup
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
DELETE /contactgroups/{_id}v0_delete_contactgroups_id · unavailableadaptation-requiredDELETE /contact-groups/{id}archiveContactGroup
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /contactgroups/{_id}v0_get_contactgroups_id · supportedequivalentGET /contact-groups/{id}getContactGroup
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /contactgroups/{_id}v0_put_contactgroups_id · unavailableadaptation-requiredPATCH /contact-groups/{id}updateContactGroup
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /contactsv0_get_contacts · supportedequivalentGET /contactslistContacts
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /contactsv0_post_contacts · supportedequivalentPOST /contactscreateContact
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /contactsv0_put_contacts · deprecated-aliasadaptation-requiredPATCH /contacts/{id}updateContact
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
GET /contacts/{_id}v0_get_contacts_id · supportedequivalentGET /contacts/{id}getContact
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /contacts/{_id}v0_put_contacts_id · supportedadaptation-requiredPATCH /contacts/{id}updateContact
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
DELETE /journalEntriesv0_delete_journalEntries · unavailableadaptation-requiredDELETE /project-statements/{id}archiveProjectStatement
5 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /journalEntriesv0_get_journalEntries · supportedadaptation-requiredGET /project-statementslistProjectStatements
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /journalEntriesv0_post_journalEntries · unavailableadaptation-requiredPOST /project-statementscreateProjectStatement
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
PUT /journalEntriesv0_put_journalEntries · unavailableadaptation-requiredPATCH /project-statements/{id}updateProjectStatement
5 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
DELETE /journalEntries/{_id}v0_delete_journalEntries_id · unavailableadaptation-requiredDELETE /project-statements/{id}archiveProjectStatement
5 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /journalEntries/{_id}v0_get_journalEntries_id · supportedadaptation-requiredGET /project-statements/{id}getProjectStatement
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
PUT /journalEntries/{_id}v0_put_journalEntries_id · unavailableadaptation-requiredPATCH /project-statements/{id}updateProjectStatement
5 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Rename the resource from journal entry to project statement and request the required finance scope for financial fields.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
DELETE /listsv0_delete_lists · deprecated-aliasadaptation-requiredDELETE /lists/{id}archiveList
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /listsv0_get_lists · supportedequivalentGET /listslistLists
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /listsv0_post_lists · supportedequivalentPOST /listscreateList
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /listsv0_put_lists · deprecated-aliasadaptation-requiredPATCH /lists/{id}updateList
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
DELETE /lists/{_id}v0_delete_lists_id · supportedadaptation-requiredDELETE /lists/{id}archiveList
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /lists/{_id}v0_get_lists_id · supportedequivalentGET /lists/{id}getList
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /lists/{_id}v0_put_lists_id · supportedadaptation-requiredPATCH /lists/{id}updateList
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
DELETE /productgroupsv0_delete_productgroups · deprecated-aliasadaptation-requiredDELETE /product-groups/{id}archiveProductGroup
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /productgroupsv0_get_productgroups · supportedequivalentGET /product-groupslistProductGroups
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /productgroupsv0_post_productgroups · supportedequivalentPOST /product-groupscreateProductGroup
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /productgroupsv0_put_productgroups · deprecated-aliasadaptation-requiredPATCH /product-groups/{id}updateProductGroup
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
DELETE /productgroups/{_id}v0_delete_productgroups_id · supportedadaptation-requiredDELETE /product-groups/{id}archiveProductGroup
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /productgroups/{_id}v0_get_productgroups_id · supportedequivalentGET /product-groups/{id}getProductGroup
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /productgroups/{_id}v0_put_productgroups_id · supportedadaptation-requiredPATCH /product-groups/{id}updateProductGroup
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
DELETE /productsv0_delete_products · deprecated-aliasadaptation-requiredDELETE /products/{id}archiveProduct
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /productsv0_get_products · supportedequivalentGET /productslistProducts
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /productsv0_post_products · supportedequivalentPOST /productscreateProduct
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /productsv0_put_products · deprecated-aliasadaptation-requiredPATCH /products/{id}updateProduct
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
DELETE /products/{_id}v0_delete_products_id · supportedadaptation-requiredDELETE /products/{id}archiveProduct
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /products/{_id}v0_get_products_id · supportedequivalentGET /products/{id}getProduct
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /products/{_id}v0_put_products_id · supportedadaptation-requiredPATCH /products/{id}updateProduct
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
GET /projectsv0_get_projects · supportedequivalentGET /projectslistProjects
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /projectsv0_post_projects · supportedequivalentPOST /projectscreateProject
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /projectsv0_put_projects · deprecated-aliasadaptation-requiredPATCH /projects/{id}updateProject
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
GET /projects/{_id}v0_get_projects_id · supportedequivalentGET /projects/{id}getProject
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /projects/{_id}v0_put_projects_id · supportedadaptation-requiredPATCH /projects/{id}updateProject
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
DELETE /projectTemplatesv0_delete_projectTemplates · unavailableadaptation-requiredDELETE /project-templates/{id}archiveProjectTemplate
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /projectTemplatesv0_get_projectTemplates · supportedequivalentGET /project-templateslistProjectTemplates
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /projectTemplatesv0_post_projectTemplates · unavailableequivalentPOST /project-templatescreateProjectTemplate
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
PUT /projectTemplatesv0_put_projectTemplates · unavailableadaptation-requiredPATCH /project-templates/{id}updateProjectTemplate
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
DELETE /projectTemplates/{_id}v0_delete_projectTemplates_id · unavailableadaptation-requiredDELETE /project-templates/{id}archiveProjectTemplate
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /projectTemplates/{_id}v0_get_projectTemplates_id · supportedequivalentGET /project-templates/{id}getProjectTemplate
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /projectTemplates/{_id}v0_put_projectTemplates_id · unavailableadaptation-requiredPATCH /project-templates/{id}updateProjectTemplate
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
  • The frozen v0 route is unavailable; v1 provides the governed replacement operation.
GET /scheduledWorkv0_get_scheduledWork · supportedadaptation-requiredGET /planned-worklistPlannedWork
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use the planned-work filters and bounded pagination instead of the legacy scheduled-work query shape.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
GET /servicesv0_get_services · supportedequivalentGET /serviceslistServices
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
GET /services/{_id}v0_get_services_id · supportedequivalentGET /services/{id}getService
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
GET /tagsv0_get_tags · supportedequivalentGET /tagslistTags
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
GET /tags/{_id}v0_get_tags_id · supportedequivalentGET /tags/{id}getTag
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
DELETE /tasksv0_delete_tasks · deprecated-aliasadaptation-requiredDELETE /tasks/{id}archiveTask
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /tasksv0_get_tasks · supportedequivalentGET /taskslistTasks
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /tasksv0_post_tasks · supportedequivalentPOST /taskscreateTask
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /tasksv0_put_tasks · deprecated-aliasadaptation-requiredPATCH /tasks/{id}updateTask
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
DELETE /tasks/{_id}v0_delete_tasks_id · supportedadaptation-requiredDELETE /tasks/{id}archiveTask
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /tasks/{_id}v0_get_tasks_id · supportedequivalentGET /tasks/{id}getTask
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /tasks/{_id}v0_put_tasks_id · supportedadaptation-requiredPATCH /tasks/{id}updateTask
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
POST /tasks/{_id}/startTrackingv0_post_tasks_id_startTracking · supportedequivalentPOST /tasks/{id}/timer/startstartTaskTimer
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
POST /tasks/{_id}/stopTrackingv0_post_tasks_id_stopTracking · supportedequivalentPOST /tasks/{id}/timer/stopstopTaskTimer
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
GET /teamsv0_get_teams · supportedadaptation-requiredGET /workspacegetWorkspace
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
  • The authenticated tenant is exposed as one workspace resource rather than a team collection.
DELETE /timesv0_delete_times · deprecated-aliasadaptation-requiredDELETE /time-entries/{id}archiveTimeEntry
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /timesv0_get_times · supportedequivalentGET /time-entrieslistTimeEntries
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
POST /timesv0_post_times · supportedequivalentPOST /time-entriescreateTimeEntry
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /timesv0_put_times · deprecated-aliasadaptation-requiredPATCH /time-entries/{id}updateTimeEntry
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
DELETE /times/{_id}v0_delete_times_id · supportedadaptation-requiredDELETE /time-entries/{id}archiveTimeEntry
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • The v1 operation archives the resource; it does not promise physical deletion.
GET /times/{_id}v0_get_times_id · supportedequivalentGET /time-entries/{id}getTimeEntry
2 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
PUT /times/{_id}v0_put_times_id · supportedadaptation-requiredPATCH /time-entries/{id}updateTimeEntry
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Use PATCH and send only declared mutable attributes; follow the target operation concurrency contract.
  • Consume the documented API v1 resource envelope and error model.
GET /usersv0_get_users · supportedequivalentGET /userslistUsers
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
DELETE /webhooksv0_delete_webhooks · deprecated-aliasadaptation-requiredDELETE /webhooks/{id}removeWebhook
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Move the resource id from the legacy body alias into the v1 resource path.
  • Consume the documented API v1 resource envelope and error model.
  • Treat legacy unsigned v0 and signed v2 webhook subscriptions as separate resources during migration.
GET /webhooksv0_get_webhooks · supportedadaptation-requiredGET /webhookslistWebhooks
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Follow cursor pagination and persist the returned continuation cursor when present.
  • Treat legacy unsigned v0 and signed v2 webhook subscriptions as separate resources during migration.
POST /webhooksv0_post_webhooks · supportedadaptation-requiredPOST /webhookscreateWebhook
4 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Create a signed webhook v2 subscription and persist the one-time signing secret.
  • Consume the documented API v1 resource envelope and error model.
  • Treat legacy unsigned v0 and signed v2 webhook subscriptions as separate resources during migration.
DELETE /webhooks/{_id}v0_delete_webhooks_id · supportedadaptation-requiredDELETE /webhooks/{id}removeWebhook
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Treat legacy unsigned v0 and signed v2 webhook subscriptions as separate resources during migration.
GET /webhooks/{_id}v0_get_webhooks_id · supportedadaptation-requiredGET /webhooks/{id}getWebhook
3 documented changes
  • Use a scoped API v1 bearer credential and the credential-derived regional endpoint.
  • Consume the documented API v1 resource envelope and error model.
  • Treat legacy unsigned v0 and signed v2 webhook subscriptions as separate resources during migration.

How to use the result

  1. Inventory the v0 method and path actually called by the integration.
  2. Open its v1 operation and implement the documented scopes, request, response, and errors.
  3. Apply every route-specific request, response, and semantic change from this matrix.
  4. Compare bounded reads before enabling writes.
  5. Keep the v0 credential active until the migrated workflow and rollback path are verified.
  6. Revoke and remove the v0 credential after the observation window passes.

Read the migration guide for the platform-wide sequence and the production checklist before switching traffic.

Stable documentation · Developer Platform · Reviewed 2026-08-10Edit this page ↗
Documentation feedbackWas this page useful?
Esc

Search TeamGrid Developer

Find guides, concepts and every API operation.
↑↓ Navigate↵ Open