Ordrestyring API and MCP server Let your AI agent run your Ordrestyring paperwork.

ToolWhat it doesAccess

• list_orders Orders with customer, status and responsible employee, newest first. read

  Lists the orders in the Orders menu (ordrer). Each row has the order number, customer and status. The default statuses are open, in progress, closed, posted and cancelled; your firm may have renamed or added labels. Basis users only see the orders they are assigned to and the statuses their group may see. Use get_order for hours and materials.

  MCP callordrestyring_read → list_orders

  REST endpointGET https://cotlet.dev/api/v1/ordrestyring/orders

  Parameters

  Parameters: list_orders

  Name	Type	Description
  status string	string	open, in_progress, closed, posted or cancelled. Omit for all you may see.
  query string	string	Order number, customer name or text in the order.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "orders": [
      {
        "order_id": "10482",
        "customer": "Nørregaard Ejendomme",
        "title": "Badeværelse Nørrebro",
        "status": "in_progress",
        "responsible": "Jonas H."
      },
      {
        "order_id": "10477",
        "customer": "Birgit Lund",
        "title": "Varmepumpe service",
        "status": "open",
        "responsible": "Mikkel S."
      },
      {
        "order_id": "10469",
        "customer": "Fjordvej Boligforening",
        "title": "Tagrende udskiftning",
        "status": "in_progress",
        "responsible": "Jonas H."
      }
    ],
    "next_cursor": null
  }

• get_order One order with its customer, status and the economy totals. read

  Returns what the order page shows: customer, status, responsible employee and the Economy tab (Økonomi): hours, materials and other costs booked so far, plus the offer total when the order came from an offer. Use list_time_entries and list_material_lines for the lines behind the totals.

  MCP callordrestyring_read → get_order

  REST endpointGET https://cotlet.dev/api/v1/ordrestyring/orders/{order_id}

  Parameters

  Parameters: get_order

  Name	Type	Description
  order_id string required	string	Order number from list_orders.

  Example input

  {
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "10482",
    "customer": "Nørregaard Ejendomme",
    "title": "Badeværelse Nørrebro",
    "status": "in_progress",
    "responsible": "Jonas H.",
    "economy": {
      "hours": 42.5,
      "materials_cost": 18240,
      "other_costs": 0,
      "offer_total": 96000,
      "currency": "DKK"
    }
  }

• list_customers Customers from the customer list, searchable by name. read

  Lists the customer list (kunder). An order cannot be created without a customer, so create_order takes a customer_id from here. The user needs the right to see the customer list; basis users may not have it.

  MCP callordrestyring_read → list_customers

  REST endpointGET https://cotlet.dev/api/v1/ordrestyring/customers

  Parameters

  Parameters: list_customers

  Name	Type	Description
  query string	string	Part of the customer name.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "customers": [
      {
        "customer_id": "3021",
        "name": "Nørregaard Ejendomme",
        "city": "København N"
      },
      {
        "customer_id": "3035",
        "name": "Birgit Lund",
        "city": "Frederiksberg"
      }
    ],
    "next_cursor": null
  }

• create_order Create an order for an existing customer. write

  Does what Create > Order does. An order needs a customer, so pass a customer_id from list_customers. A new order gets the default status and type set in your system settings, and an order template can fill in materials, forms and sub-orders. It reaches nobody until someone is planned on it, so it needs no approval. Cancel the order in Ordrestyring to undo it.

  MCP callordrestyring_write → create_order

  REST endpointPOST https://cotlet.dev/api/v1/ordrestyring/customers/{customer_id}/orders

  Parameters

  Parameters: create_order

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  title string required	string	Short title of the job.
  description string	string	What the job is.
  template string	string	Name of an order template. Omit for none.

  Example input

  {
    "customer_id": "customer_8c41d2",
    "title": "title"
  }

  Example response

  {
    "order_id": "10491",
    "customer": "Birgit Lund",
    "title": "Utæt vandhane køkken",
    "status": "open"
  }

ToolWhat it doesAccess

• list_time_entries Hours registered on an order or by an employee for a week or period. read

  Does what My hours (Mine timer) and an order's Time spent (Timeforbrug) show: date, time type, order number, from and to, description, and the approval status when the Time approval add-on is on. Billable and non-billable hours are both returned. Pass order_id for one order or employee for one person.

  MCP callordrestyring_read → list_time_entries

  REST endpointGET https://cotlet.dev/api/v1/ordrestyring/time-entries

  Parameters

  Parameters: list_time_entries

  Name	Type	Description
  order_id string	string	Only hours on this order.
  employee string	string	Employee name. Omit for yourself.
  from date	date	First day of the period.
  to date	date	Last day of the period.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "entries": [
      {
        "entry_id": "h_88120",
        "date": "2026-10-28",
        "employee": "Jonas H.",
        "time_type": "Svendetime",
        "order_id": "10482",
        "from": "07:00",
        "to": "15:30",
        "hours": 8,
        "description": "Fliser i bad",
        "approval": "pending"
      },
      {
        "entry_id": "h_88131",
        "date": "2026-10-29",
        "employee": "Jonas H.",
        "time_type": "Svendetime",
        "order_id": "10482",
        "from": "07:00",
        "to": "14:30",
        "hours": 7,
        "description": "Fuger og armatur",
        "approval": "pending"
      }
    ],
    "next_cursor": null
  }

• log_time Register hours on an order for the signed-in employee. write

  Does what My hours (Mine timer) does: date, time type, order number, from and to and a description. Some time types, such as sickness, need no order. Hours that are already approved cannot be changed, by anyone. The entry reaches nobody and can be edited or deleted in Time spent on the order, so it needs no approval.

  MCP callordrestyring_write → log_time

  REST endpointPOST https://cotlet.dev/api/v1/ordrestyring/times

  Parameters

  Parameters: log_time

  Name	Type	Description
  date date required	date	Day the work was done.
  time_type string required	string	Time type as named in your firm, for example Svendetime.
  order_id string	string	Order number. Omit for time types that need none.
  from time required	time	Start time, HH:MM.
  to time required	time	End time, HH:MM.
  description string	string	Short text on the registration.

  Example input

  {
    "date": "2026-10-30",
    "time_type": "Svendetime",
    "order_id": "10482",
    "from": "07:00",
    "to": "15:00",
    "description": "Fliser i bad"
  }

  Example response

  {
    "entry_id": "h_88140",
    "date": "2026-10-30",
    "time_type": "Svendetime",
    "order_id": "10482",
    "from": "07:00",
    "to": "15:00",
    "hours": 8,
    "approval": "not_sent"
  }

• approve_hours Approve or reject hours that employees sent for approval. writeasks first

  Does what the administrator's Time approval menu (Timegodkendelse) does, so it needs the Time approval add-on switched on and an Admin user. Approved hours can no longer be edited by anyone and are what the payroll integration picks up. A rejected entry goes back to the employee. By default you confirm each call; you can switch that off for this tool.

  MCP callordrestyring_write → approve_hours

  REST endpointPOST https://cotlet.dev/api/v1/ordrestyring/hours/approve

  Parameters

  Parameters: approve_hours

  Name	Type	Description
  entry_ids array required	array	Entry IDs from list_time_entries with approval pending.
  decision string required	string	approve or reject.

  Example input

  {
    "entry_ids": "entry ids",
    "decision": "decision"
  }

  Example response

  {
    "decision": "approve",
    "approved": [
      "h_88120",
      "h_88131"
    ],
    "status": "approved"
  }

• list_material_lines Materials booked on an order, with cost and sales price. read

  Does what Material usage (Materialeforbrug) on an order shows: each line with item number, quantity, cost price and sales price. A line is marked manual when it was typed in the app or on the PC, and edi when it came from a supplier invoice in the Inbox. A line whose cost and list price are equal is flagged, because it often means your price agreement was not read in.

  MCP callordrestyring_read → list_material_lines

  REST endpointGET https://cotlet.dev/api/v1/ordrestyring/orders/{order_id}/material-lines

  Parameters

  Parameters: list_material_lines

  Name	Type	Description
  order_id string required	string	Order number from list_orders.

  Example input

  {
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "10482",
    "lines": [
      {
        "item_number": "FL-3030-HV",
        "description": "Gulvflise 30x30 hvid",
        "quantity": 14,
        "cost_price": 118,
        "sales_price": 189,
        "source": "edi"
      },
      {
        "item_number": "FUGE-5",
        "description": "Fugemørtel 5 kg",
        "quantity": 3,
        "cost_price": 96,
        "sales_price": 96,
        "source": "manual",
        "flagged": true
      }
    ],
    "currency": "DKK"
  }

• add_material_line Book a material on an order. write

  Does what adding in Material usage (Materialeforbrug) does: search by item number or name in your wholesale catalogs and internal items, or type a line by hand with a price. From a catalog the cheapest supplier is the default. The line reaches nobody and can be edited or moved to another order in the app, so it needs no approval.

  MCP callordrestyring_write → add_material_line

  REST endpointPOST https://cotlet.dev/api/v1/ordrestyring/orders/{order_id}/material-lines

  Parameters

  Parameters: add_material_line

  Name	Type	Description
  order_id string required	string	Order number from list_orders.
  item string required	string	Item number or name to search for, or a free text line.
  quantity number required	number	Quantity.
  cost_price number	number	Only for a hand-typed line.
  sales_price number	number	Only for a hand-typed line.

  Example input

  {
    "order_id": "order_8c41d2",
    "item": "item",
    "quantity": 1
  }

  Example response

  {
    "order_id": "10482",
    "item_number": "FL-3030-HV",
    "description": "Gulvflise 30x30 hvid",
    "quantity": 4,
    "cost_price": 118,
    "sales_price": 189,
    "source": "manual"
  }

ToolWhat it doesAccess

• list_planned_tasks The day overview: who is planned on which order, day by day. read

  Does what the Day overview (Dagsoversigt) shows for a day or a week: planned time per employee with order, start and end. Planned time with an order is what the fitter sees in the app. Personal and other events are returned too, without customer data.

  MCP callordrestyring_read → list_planned_tasks

  REST endpointGET https://cotlet.dev/api/v1/ordrestyring/planned-tasks

  Parameters

  Parameters: list_planned_tasks

  Name	Type	Description
  from date required	date	First day.
  to date	date	Last day. Default is the same day.
  employee string	string	Employee name. Omit for everyone you may see.

  Example input

  {
    "from": "2026-10-01"
  }

  Example response

  {
    "tasks": [
      {
        "task_id": "p_5521",
        "date": "2026-11-03",
        "employee": "Jonas H.",
        "kind": "planned_time",
        "order_id": "10482",
        "from": "07:00",
        "to": "15:00"
      },
      {
        "task_id": "p_5524",
        "date": "2026-11-03",
        "employee": "Mikkel S.",
        "kind": "planned_time",
        "order_id": "10477",
        "from": "08:00",
        "to": "12:00"
      }
    ]
  }

• plan_task Plan an employee on an order for a start and end time. writeasks first

  Does what clicking a day in the Day overview (Dagsoversigt) does for planned time. It needs an order, because the fitter's app shows the order and customer details with it, so the employee sees it at once. Pass several employees to put them on the same order. Planned time is not worked time: it books no hours. Delete it in the Day overview to undo it. By default you confirm each call; you can switch that off for this tool.

  MCP callordrestyring_write → plan_task

  REST endpointPOST https://cotlet.dev/api/v1/ordrestyring/orders/{order_id}/task/plan

  Parameters

  Parameters: plan_task

  Name	Type	Description
  order_id string required	string	Order number from list_orders.
  employees array required	array	Employee names.
  date date required	date	Day to plan.
  from time	time	Start time, HH:MM. Default is the firm's opening hours.
  to time	time	End time, HH:MM.

  Example input

  {
    "order_id": "order_8c41d2",
    "employees": "employees",
    "date": "2026-10-01"
  }

  Example response

  {
    "order_id": "10477",
    "date": "2026-11-04",
    "planned": [
      {
        "employee": "Mikkel S.",
        "from": "08:00",
        "to": "12:00"
      }
    ],
    "status": "planned"
  }

• create_invoice_draft Start an invoice draft from the hours and materials of an order. write

  Does what fetching lines into an invoice draft (fakturakladde) does: the fitters' registered hours and materials on the order become lines. Nothing is sent to the customer or the accounting system. The draft stays in Ordrestyring until the owner reviews it, approves it and sends it, so the tool needs no approval.

  MCP callordrestyring_write → create_invoice_draft

  REST endpointPOST https://cotlet.dev/api/v1/ordrestyring/orders/{order_id}/invoice-drafts

  Parameters

  Parameters: create_invoice_draft

  Name	Type	Description
  order_id string required	string	Order number from list_orders.
  include string	string	hours, materials or both. Default both.

  Example input

  {
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "10482",
    "draft_id": "d_2207",
    "lines": 11,
    "hours": 42.5,
    "materials_total": 26110,
    "currency": "DKK",
    "status": "draft"
  }