Before You Start
Access to Knak Admin settings
A translation tool that supports API workflows
Basic knowledge of API authentication
For complete endpoint details, request examples, and response schemas, see the Knak API documentation.
Set Up API Access
Create an API Role
Open Knak Builder
Click Admin (top left)
Click Company > Roles > + Create Role
Add Role Name: API User
Add Role Description (optional)
Add permissions:
Request Translations
Can Manage API Tokens
(Optional) Request Translations for Unapproved Email
Click Create
Create an API User
Click Company > Users > Invite User
Enter user details:
Email
First name
Last name
Select the API role you created
Click Save User and Send Invite
💡 Tip: Use an email alias when setting up integrations (for example, youremail+api@domain.com).
This keeps all integrations tied to one dedicated account. It also prevents disruptions if a team member leaves.
Create an API Token
Use a permanent API token to authenticate requests from your platform.
Sign in as the API user you created.
Open the API Access page.
Click +Create New Token to generate a permanent API token.
Name the API token.
Copy and store the token securely.
For authentication details, see the API Authentication documentation.
⚠️ Important: The Personal Access Token is only displayed once. After you close this window, you cannot view it again. Store the token in a secure location before leaving the page. You will use this token to authenticate API requests to Knak.
Create a Webhook
A webhook sends an HTTP request whenever an event occurs in Knak.
For a custom MAP integration, subscribe to the syncRequested event. This event tells your platform when to retrieve asset content.
Note: You must have permission to manage integrations.
Configure the Webhook
Open Knak Builder.
Click Admin.
Go to Integrations > Webhooks.
Click Create Webhook.
Enter the following:
Name
Payload URL
Secret
Subscribed Events:
syncRequested
Click Create new webhook.
About the Webhook Secret
The webhook secret verifies that requests came from Knak.
Knak signs each payload using the HMAC SHA256 algorithm.
Compare the generated hash with the value in the Knak-Signature request header.
Process the webhook only if both values match.
You can:
Use the automatically generated secret.
Generate a new secret with the refresh icon.
Click the Eye icon to reveal the webhook secret. Copy the value and store it securely for use when validating webhook requests.
Note: Keep this secret safe. You will use it when validating webhook requests.
Create a Custom MAP Integration
Create a platform connection so users can publish assets from Knak.
Open Knak Builder.
Click Admin.
Go to Integrations > Platforms.
Navigate to the Custom Marketing Automation Platform tile under the Marketing Automation Platforms section.
Click the Connect button.
Enter:
Integration Name
Asset Sync Types
Email
Landing Page
Both
Merge Tag Platform Format
Click Create New Integration.
Manage Your Integration
After setup, view your integration in the My Platform Connection list on the Integrations page.
From here, you can:
To connect a new integration or re-add a deleted one:
Scroll to All Platforms.
Find the Custom Marketing Automation Platform tile.
Click Connect or Add Another Connection.
Sync an Asset
After your integration is configured, you can sync assets from Knak to your custom platform.
Start the Sync
Open the asset you want to sync.
Click the Actions menu.
Select Sync.
Choose your Custom Marketing Automation Platform integration.
Click Sync.
Knak starts the sync process and sends a
syncRequestedwebhook to your configured endpoint.
The sync process includes these steps:
Receive the
syncRequestedwebhook.Validate the webhook signature.
Retrieve the asset content.
Create or update the asset in your platform.
Update the sync status in Knak.
Receive the syncRequested Webhook
When you start a sync, Knak sends a syncRequested webhook to your configured endpoint.
The payload includes information such as:
Asset identifiers
Sync status identifier
Content URL (
content_link)Platform information
See the API documentation for the complete webhook payload schema:
Verify the Webhook
Before processing the request:
Calculate the HMAC SHA256 hash using your webhook secret.
Compare the result with the Knak-Signature header.
Continue only if both values match.
This confirms the payload has not been modified.
Retrieve Asset Content
Send a GET request to the content_link included in the webhook.
The response contains:
Asset metadata
HTML
Plain text
Optional Platform Conversion
You can include the optional platform parameter. When provided, Knak converts merge tags into the syntax required by your platform.
Parameter | Required | Description |
| No | Converts merge tags to your platform's syntax. Example: |
Sample Request
GET https://enterprise.knak.io/api/published/v1/assets/609d7ce223411/content
For request parameters, response fields, and additional examples, see the Get Asset Content API documentation:
Update the Sync Status
After processing the asset, update the sync status by sending a PATCH request to the Sync Status endpoint.
Sample Request
PATCH https://enterprise.knak.io/api/published/v1/sync-status/609d7ce223411
When the Sync Succeeds
Set the status to completed.
Property | Required | Purpose |
| Yes | Unique identifier of the asset in your platform. |
| Optional | Link to the asset in your platform. |
Knak stores the map_id for future syncs. If you include a map_url, users can open the synced asset directly from Knak.
When the Sync Fails
Set the status to failed.
Property | Recommended | Purpose |
| Yes | Displays the error to users. Stores the error for troubleshooting. |
For the complete request body, supported status values, and response examples, see the Update Sync Status API documentation:
Related API Documentation
Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com.















