Fiken API · unofficial, by Cotlet
Create your own Fiken API
Fiken's API is an add-on at 99 kr a month for a company registered in Brønnøysundregistrene (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Fiken account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Fiken session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Fiken. Fiken is a trademark of its owner. If Fiken's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/overdue-invoices" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"min_days_overdue": 1}' const url = "https://cotlet.dev/api/v1/custom/overdue-invoices";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ min_days_overdue: 1 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/overdue-invoices",
headers={"Authorization": f"Bearer {key}"},
json={"min_days_overdue": 1},
)
data = res.json()["data"] {
"data": [
{
"invoice": 10231,
"customer": "Fjell Bygg AS",
"amount": 12500,
"due": "2026-11-15",
"days_overdue": 5
},
{
"invoice": 10236,
"customer": "Kafé Lyng",
"amount": 4375,
"due": "2026-11-12",
"days_overdue": 8
}
]
} 01 Build
How do you build a Fiken endpoint with Cotlet?
-
Sign in to Fiken in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List overdue invoices with the customer, amount, due date and days overdue."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a number of days or a customer, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Fiken session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Fiken
Cotlet ships no fixed list of Fiken endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/overdue-invoices Overdue invoices
Invoice, customer, amount, due date and days overdue
-
POST
/api/v1/custom/purchases-due Purchases due
Supplier, amount and due date of unpaid purchases
-
POST
/api/v1/custom/inbox-documents Unused inbox documents
Documents in the inbox not yet booked
-
POST
/api/v1/custom/sales-by-customer Sales by customer
Invoiced totals per customer for a period
-
POST
/api/v1/custom/writesadd-contact Add a contact
A new customer or supplier with name, email and organization number
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/overdue-invoices" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"min_days_overdue": 1}' The answer is JSON, with your fields under data:
{
"data": [
{
"invoice": 10231,
"customer": "Fjell Bygg AS",
"amount": 12500,
"due": "2026-11-15",
"days_overdue": 5
},
{
"invoice": 10236,
"customer": "Kafé Lyng",
"amount": 4375,
"due": "2026-11-12",
"days_overdue": 8
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Fiken endpoints for?
- Schedule Cotlet endpoint Slack or email
A Monday overdue list.
Overdue invoices and purchases due soon, sent to Slack or email.
- Your CRM endpoint contact added
Contacts from your CRM.
New customers added to Fiken with their organization number.
- Schedule endpoint Google Sheets
Sales in a sheet.
Invoiced totals by customer pulled into Google Sheets each month.
- Chat agent endpoint open invoices
An assistant for customer questions.
A chat agent that reads what a customer owes before it answers.
04 Access
What can an endpoint see and change?
An endpoint works in your own Fiken session, so it can read and change only what your Fiken login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as adding a contact, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Fiken have an official API?
Fiken's API is an add-on you activate under Foretak, Tilleggstjenester: "Hvis du ønsker å bruke API'et for et reelt foretak som er registrert i Brønnøysundregisteret koster det 99 kroner pr. måned" (for a real company registered in the Brønnøysund register it costs 99 kroner a month). Apps for other businesses use OAuth2 and need Fiken's approval for production (checked 20 Nov 2026). The full picture with sources: Does Fiken have an API or MCP server?
Want ChatGPT or Claude to work in Fiken instead of code? See the Fiken MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Fiken API with Cotlet: questions
Is this an official Fiken API?
No. Cotlet is independent and not affiliated with Fiken. The endpoints you build run in your own signed-in Fiken account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Fiken changes its screens?
An endpoint works while Fiken works the way it did when you built it. If Fiken changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Fiken endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.