Overview
clarife’s REST API and webhooks work with any automation platform that supports HTTP requests. Below are step-by-step guides for the three most popular tools.n8n
Fetch Documents (HTTP Request Node)
Configure the request
- Method: GET
- URL:
https://my.clarife.app/api/v1/documents - Authentication: Header Auth
- Header Name:
Authorization - Header Value:
Bearer clrf_your_key
Receive Webhook Events
Register in clarife
Go to Settings > API > Webhooks and create a new subscription. Paste the n8n webhook URL and select the events you want.
Make (formerly Integromat)
Fetch Documents (HTTP Module)
Configure the module
- URL:
https://my.clarife.app/api/v1/documents - Method: GET
- Headers:
Authorization:Bearer clrf_your_key
- Parse response: Yes
Receive Webhook Events
Add a Webhooks module
Add Webhooks > Custom webhook as the scenario trigger. Copy the URL that Make generates.
Send a test event
Click Send test event in clarife, then click Redetermine data structure in Make to auto-detect the payload fields.
Zapier
Trigger on Webhook Events
Choose Webhooks by Zapier
For the trigger, select Webhooks by Zapier > Catch Hook. Copy the webhook URL.
Register in clarife
Go to Settings > API > Webhooks and create a subscription with the Zapier webhook URL. Select the events you want.
Send a test event
Click Send test event in clarife, then click Test trigger in Zapier to pick up the sample payload.
Fetch Documents via API Request
Configure the request
- Method: GET
- URL:
https://my.clarife.app/api/v1/documents - Headers:
Authorization:Bearer clrf_your_key
Tips for All Platforms
Use webhooks over polling
Webhooks deliver events in real time and reduce API calls. Only poll when you need an immediate snapshot.
Verify signatures
Always verify the
X-Clarife-Signature header in production. See the Webhooks guide for code examples.Handle pagination
List endpoints return max 100 items. Use
limit and offset to iterate through large datasets.Secure your keys
Store API keys in environment variables or your platform’s secret manager. Never hardcode them in workflows.