Get your API credentials
Before you can make API requests, you need to obtain your API Key and Client Secret from the COR dashboard.API environments
COR provides three API services that work together to manage your projects, resources, and external integrations.COR API
Base URL:
https://api.projectcor.com/v1Main API for projects, tasks, clients, users, time tracking, and transactions.Resource Allocation API
Base URL:
https://planner.svc.v2.projectcor.comDedicated service for managing user capacity and project allocations.Integrations API
Base URL:
https://integrations.projectcor.com/Service for external system integrations with external ID mapping and bidirectional sync.All three APIs share the same authentication. Use your access token from the main COR API to authenticate requests to the Resource Allocation API and Integrations API.
Development tools
Import the OpenAPI specification
Import the COR OpenAPI specification into your preferred API client for easy testing:- Postman
- Insomnia
- VS Code
- Open Postman and click Import
- Select Link and paste the OpenAPI URL:
- Click Import to generate a complete collection with all endpoints
Recommended libraries
Use these HTTP libraries for your integrations:Best practices
Secure token management
Implement automatic token refresh
Access tokens expire after a period of time. Implement automatic refresh to maintain uninterrupted access:Handle pagination
All list endpoints return paginated responses by default with the following structure:page and perPage parameters to navigate through results:
Error handling
HTTP status codes
The COR API uses standard HTTP status codes:| Code | Description | Action |
|---|---|---|
200 | Success | Process the response |
204 | Success (No Content) | Request succeeded, no body returned |
400 | Bad Request | Check request parameters and body |
401 | Unauthorized | Refresh or re-obtain access token |
404 | Not Found | Verify the resource ID exists |
429 | Too Many Requests | Implement backoff and retry |
500 | Server Error | Retry with exponential backoff |
Implement retry logic
Handle transient errors with exponential backoff:Troubleshooting
401 Unauthorized - Invalid or expired token
401 Unauthorized - Invalid or expired token
400 Bad Request - Invalid request format
400 Bad Request - Invalid request format
Causes:
- Missing required fields in the request body
- Invalid data types or formats
- Malformed JSON
- Check the API reference for required parameters
- Validate JSON syntax before sending
- Ensure dates are in the correct format (
YYYY-MM-DD)
403 Forbidden - Insufficient permissions
403 Forbidden - Insufficient permissions
Causes:
- User lacks permission for the requested action
- API key scope is limited
- Verify your user has the required permissions in COR
- Contact your COR administrator to adjust permissions
503 Service Unavailable - Temporary outage
503 Service Unavailable - Temporary outage
Next steps
Quickstart
Make your first API call and authenticate with COR.
API Reference
Explore all available endpoints and parameters.
Resource Allocation
Manage user capacity and project assignments.
AI Tools
Use AI-powered tools to accelerate your integration development.
Need help? Contact our support team at help@projectcor.com or visit COR Support.


