Authenticate all requests to the Surveys API securely when linking with Fortnox. Use API keys, OAuth tokens, and store secrets in a secure vault.
Fortnox uses token-based authentication with API keys and access tokens. Keep credentials secure and rotate them regularly.
Key endpoints you may use: POST /social-media-posting/:locationId/posts; PUT /social-media-posting/:locationId/posts/:id; DELETE /social-media-posting/:locationId/posts/:id; PATCH /social-media-posting/:locationId/posts/:id. The above endpoints illustrate typical create and manage actions; adjust mappings to Fortnox as needed.
Trigger: when a new survey submission occurs in Surveys API, create or update a Fortnox contact.
Actions: map key fields (name, email, survey score) to Fortnox contact records and keep data aligned.
Path: Fortnox Contacts endpoint (example: POST /fortnox/contacts)
Key fields: survey_id, fortnox_customer_id, email, update_date
Trigger: end-of-day export or scheduled synchronization of new surveys.
Actions: batch create or update Fortnox records such as customers or ledger entries based on survey data.
Path: Fortnox batch/import endpoints
Key fields: batch_id, timestamp, status
Trigger: survey submission triggers Fortnox workflow.
Actions: start Fortnox workflows, create tasks or accounts, sync notes.
Path: Fortnox workflow endpoints
Key fields: workflow_id, survey_id, account_id
Benefit: build powerful automation without custom code.
Benefit: accelerate onboarding with ready-to-use templates and mappings.
Benefit: ensure consistent data across Surveys API and Fortnox.
This glossary clarifies data elements and processes used in the Fortnox and Surveys API integration.
API: a set of rules that lets software communicate and share data.
OAuth 2.0 is a standard for secure delegated access to APIs.
Authentication verifies identity and grants access to resources.
An API endpoint is a URL where you access a specific function.
Automatically push notable survey insights to Fortnox contacts or accounts to keep records current.
Create financial records in Fortnox based on survey data when appropriate.
Set up automated exports to Fortnox on a cadence that matches billing or reporting cycles.
Obtain API keys from Fortnox and generate access tokens for the Surveys API connection.
Create field mappings to align survey data with Fortnox records.
Run tests, enable automated triggers, and monitor for errors.
The Surveys API provides programmatic access to survey data, enabling you to collect, update, and analyze responses. It acts as a bridge to Fortnox data and workflows. You can trigger actions in Fortnox based on survey events, without manual data entry.
No code is not always possible; you can use middleware to map fields and set up triggers. If coding is required, use lightweight scripts and the GHL connector to handle authentication and routing.
You can sync contact data, customer records, invoices, and notes from Surveys API to Fortnox, depending on your mappings and triggers.
Use API keys and OAuth tokens, store credentials securely, rotate keys, and apply least privilege access.
Yes. You can automate posting, status updates, and data sync using event triggers and scheduled tasks.
Endpoint rate limits vary by plan. Plan for retries and backoff in your integration.
Endpoint documentation is available in your developer portal and the Fortnox API docs; use the mapping guides in this page for quick references.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
