Integrations API

The Integrations API is a dedicated service that acts as an intermediary between external systems and COR. It enables you to map external IDs from third-party services to COR entities, facilitating seamless data synchronization and workflow automation.

Overview

The Integrations API provides a standardized way to:

Map external IDs — Link entities from external systems (Salesforce, Jira, SAP, etc.) to their corresponding COR entities
Sync data bidirectionally — Keep data consistent between COR and external platforms
Handle webhooks — Process incoming events from external services and route updates accordingly
Track integration state — Maintain a record of which entities are integrated and their sync status

Architecture

Base URL

All integration endpoints use the following base URL:

https://integrations.projectcor.com/

Integration Flows

The Integrations API supports three types of data flows depending on your integration requirements:

External → COR

Unidirectional inboundData flows from an external service into COR. Example: Creating projects in COR when opportunities are won in Salesforce.

COR → External

Unidirectional outboundData flows from COR to an external service. Example: Syncing time entries to an external billing system.

Bidirectional

Two-way syncFull synchronization where changes in either system are reflected in the other. Example: Project updates synced between COR and Jira.

Flow Selection

Choose your integration flow based on:

Flow Type	Use Case	Example
External → COR	External system is the source of truth	CRM creates projects in COR
COR → External	COR is the source of truth	Time tracking synced to payroll
Bidirectional	Both systems need real-time updates	Project management across platforms

Authentication

The Integrations API uses the same authentication as the main COR API. You can use the same Bearer token obtained from the COR authentication endpoints.

All requests require a Bearer token in the Authorization header:

Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json
Accept: application/json

Obtain your access token using one of the authentication methods from the main API:

Required Fields

All integration endpoints require the metadata.source field to identify the external system:

{
  "metadata": {
    "source": "SALESFORCE"
  },
  "id": "external-entity-id-123",
  "name": "Entity Name",
  // ... other entity fields
}

The metadata.source field is required in all integration requests. It identifies which external system the data originates from and is used to route webhooks and maintain integration mappings.

Supported Integration Sources

The API supports the following integration sources:

View all supported sources

Source	Description
`JIRA`	Atlassian Jira project management
`SALESFORCE`	Salesforce CRM
`ADVERTMIND`	Advertmind platform
`QUICKBOOKS`	QuickBooks accounting
`ZAPIER`	Zapier automation
`OKTA`	Okta identity management
`MICROSOFT_DYNAMICS`	Microsoft Dynamics 365
`GITHUB`	GitHub repository management
`MICROSOFT_TEAMS`	Microsoft Teams
`VBS`	VBS system
`SAP`	SAP enterprise system
`GLOBANT`	Globant platform

Need a custom integration source? Contact the COR development team to request support for additional platforms.

Available Entities

The Integrations API provides endpoints for managing the following entities:

Entity	Operations	Description
Brands	CREATE, UPDATE, DELETE	Manage brand associations
Clients	CREATE, UPDATE, DELETE	Sync client/account data
Contracts	CREATE, UPDATE, DELETE, Attach/Detach Users	Manage contract integrations
Positions	CREATE, UPDATE, DELETE	Manage user positions
Position Categories	CREATE, UPDATE, DELETE	Manage position categories
Projects	CREATE, UPDATE, DELETE	Manage project synchronization
Teams	CREATE, UPDATE, Attach/Detach Users	Sync team data within workspaces
Users	CREATE, UPDATE, DELETE, Assign Position	Manage user provisioning
User Leaves	CREATE	Manage leave types
Workspaces	CREATE, UPDATE	Sync workspace/team data
Working Time	CREATE, DELETE	Sync time tracking data

External ID Mapping

The core feature of the Integrations API is external ID mapping. When you create an entity through the integration endpoints:

You provide the external ID (from your system)
COR creates the entity and stores the mapping
Future operations can reference either the external ID or the COR ID

This allows you to:

Update or delete entities using their external IDs
Query integration status to determine if an entity is already synced
Route webhook events to the correct external endpoint

Example Flow

Response Codes

All integration endpoints use standard HTTP status codes:

Code	Description
`200 OK`	Operation successful
`201 Created`	Resource created successfully
`400 Bad Request`	Invalid data or missing required fields
`401 Unauthorized`	Invalid or expired token
`403 Forbidden`	Insufficient permissions
`404 Not Found`	Resource not found
`422 Unprocessable Entity`	Validation error
`500 Internal Server Error`	Server error

Error Codes

The API returns specific error codes for better error handling:

Code	Description
`ZC001`	Generic Error
`ZC002`	Validation Error
`ZC003`	API Request Exception
`ZC004`	Query Exception
`ZC005`	External Request Exception

Quick Start

1. Create an integrated project

curl --location 'https://integrations.projectcor.com/v2/integrations/projects' \
--header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "metadata": {
    "source": "SALESFORCE"
  },
  "id": "SF-OPP-12345",
  "name": "Website Redesign Project",
  "client_id": "SF-ACC-67890",
  "start": "2025-01-15",
  "end": "2025-03-31"
}'

import requests

response = requests.post(
    'https://integrations.projectcor.com/v2/integrations/projects',
    headers={
        'Authorization': f'Bearer {access_token}',
        'Content-Type': 'application/json'
    },
    json={
        'metadata': {
            'source': 'SALESFORCE'
        },
        'id': 'SF-OPP-12345',
        'name': 'Website Redesign Project',
        'client_id': 'SF-ACC-67890',
        'start': '2025-01-15',
        'end': '2025-03-31'
    }
)

project = response.json()
print(f"Created project with COR ID: {project['id']}")

const response = await fetch(
  'https://integrations.projectcor.com/v2/integrations/projects',
  {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${accessToken}`,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      metadata: {
        source: 'SALESFORCE'
      },
      id: 'SF-OPP-12345',
      name: 'Website Redesign Project',
      client_id: 'SF-ACC-67890',
      start: '2025-01-15',
      end: '2025-03-31'
    })
  }
);

const project = await response.json();
console.log(`Created project with COR ID: ${project.id}`);

2. Update using external ID

curl --location --request PUT 'https://integrations.projectcor.com/v2/integrations/projects/SF-OPP-12345' \
--header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json' \
--data '{
  "metadata": {
    "source": "SALESFORCE"
  },
  "name": "Website Redesign Project - Phase 2"
}'

Next Steps

Projects

Integrate project data between COR and external systems

Clients

Sync client and account information

Users

Manage user provisioning and assignments

Contracts

Handle contract integrations with user associations

Need help? Contact our support team at help@projectcor.com or visit COR Support.

Introduction

Brands

Clients

Contracts

Currency Exchanges

Products

Positions

Position Categories

Seniority

Projects

Teams

Users

User Leaves

Working Time

Workspaces

Overview

Architecture

Base URL

Integration Flows

External → COR

COR → External

Bidirectional

Flow Selection

Authentication

Required Fields

Supported Integration Sources

Available Entities

External ID Mapping

Example Flow

Response Codes

Error Codes

Quick Start

1. Create an integrated project

2. Update using external ID

Next Steps

Projects

Clients

Users

Contracts

​Overview

​Architecture

​Base URL

​Integration Flows

External → COR

COR → External

Bidirectional

​Flow Selection

​Authentication

​Required Fields

​Supported Integration Sources

​Available Entities

​External ID Mapping

​Example Flow

​Response Codes

​Error Codes

​Quick Start

​1. Create an integrated project

​2. Update using external ID

​Next Steps

Projects

Clients

Users

Contracts

Overview

Architecture

Base URL

Integration Flows

Flow Selection

Authentication

Required Fields

Supported Integration Sources

Available Entities

External ID Mapping

Example Flow

Response Codes

Error Codes

Quick Start

1. Create an integrated project

2. Update using external ID

Next Steps