UnitLook and ERP: Connecting Ticketing with Your Business System

Every company using an ERP system alongside a separate ticketing or project management tool faces the same problem: data lives in two places, and someone has to manually move it between them.

Finance asks: “How many hours did the team log for client XY in April?” — and the search begins across spreadsheets, the ticketing system, and calendars. Invoicing happens from memory, or doesn’t happen at all.

UnitLook solves this with a REST API that enables automatic synchronization with ERP systems, CRMs, and any other business application.

Why integrate ticketing and ERP?

Ticketing and ERP cover complementary parts of the business process:

UnitLook	ERP (Pantheon, Minimax, SAP…)
Client requests and tickets	Purchase orders and invoices
Time tracking per project	Project costs and revenue
Team and capacity planning	Payroll and labor accounting
Project status	Financial project status

Without integration: hours live in the ticketing system, invoicing is in the ERP, and accounting waits for someone to send them a spreadsheet.

With integration: work hours are automatically transferred to the ERP, invoices are generated from actual data, no manual entry required.

What the UnitLook API offers today

UnitLook has a REST API with an OpenAPI 3.1 specification. All endpoints are documented and interactively testable at api.unitlook.com/api/reference.

Available data

Tickets

• List tickets with filters (client, status, period, project)
• Ticket details including the full communication thread
• Create and update tickets from an external system

Work logs (time tracking)

• List of hours logged per user and period
• Daily aggregate (for invoicing)
• Time entries per ticket

Projects

• Project list with team members
• Status and timeline

Planning

• Planned work blocks per employee
• Planned vs. actual comparison

Typical integration scenarios

1. Automatic time export to ERP

The most common scenario: at the end of the month, the ERP needs hours per client for invoicing.

UnitLook API → hours by client for period → ERP → invoice

Instead of the manager exporting data from UnitLook and manually entering it into the ERP, the integration does this automatically. By end of month, the ERP already has all logged hours, broken down by client and project.

Endpoint: GET /api/v1/work-logs?dateFrom=2026-04-01&dateTo=2026-04-30

2. ERP event becomes a ticket

The ERP detects a situation requiring action (failure, complaint, change request) and automatically creates a ticket in UnitLook:

ERP event → POST /api/v1/tickets → ticket with assigned person and deadline

The ticket is immediately assigned to the right person, the client receives confirmation, and the team has a deadline.

3. Project status from ERP

The ERP can track delivery status, and UnitLook tracks work status. Integration merges these two views:

GET /api/v1/projects → status, hours, team → ERP project card

How it works technically

Authentication: HTTP Basic Auth — UnitLook user email and password. Every API call includes an Authorization: Basic base64(email:password) header.

Format: JSON. All responses use lowercase keys. Errors always return { "error": "..." }.

Documentation: OpenAPI 3.1 spec available at https://api.unitlook.com/openapi.yaml — import directly into Postman or use with code generators.

Example — fetch work logs:

curl https://api.unitlook.com/api/v1/work-logs?dateFrom=2026-04-01&dateTo=2026-04-30 \
  -H "Authorization: Basic $(echo -n '[email protected]:password' | base64)"

Integration with Pantheon and Minimax

Pantheon and Minimax don’t have a built-in connector for UnitLook — but they have their own APIs. This means integration is possible through a middleware that reads from one and writes to the other:

UnitLook API → middleware (Node.js / Python / .NET) → Pantheon API

This middleware can be:

• A simple cron job that exports hours on the first of every month
• An event-driven service that reacts to ticket closure
• A custom dashboard that combines data from both systems

For companies that want a ready-made integration without custom development — contact us, we’re happy to discuss a custom solution.

Webhooks (coming soon)

In addition to the REST API, webhooks are in development — UnitLook will send a POST notification to your URL when:

• ticket.created — new ticket opened
• ticket.closed — ticket resolved
• ticket.assigned — responsible person changed
• time.logged — work hours entered

This eliminates polling and enables real-time reactions in ERP or CRM.

Next steps

• Interactive documentation: api.unitlook.com/api/reference — test endpoints directly in your browser
• OpenAPI spec: api.unitlook.com/openapi.yaml — for Postman or code generation
• In the app: Administration → Integrations → API / Webhook

If you need help with integration or have a specific requirement for connecting with your ERP, contact us — we’d love to talk.