Allowed pages
/pagesRequired scope:pages:read
Sync contacts, handle direct messages and comments, and read existing flow analytics. Flow creation and editing are outside this API.
Create an integration with selected pages and permissions in API integrations. Send the token in the Authorization header as Bearer. Tokens expire after one year and can be rotated or revoked in the dashboard.
Use the API from your application server. Keep the token out of browser code and public repositories. Bearer requests need no cookies or CSRF initialization. Only pages you own and explicitly select are accessible; shared team pages cannot be delegated. Messages and comments currently support Instagram only.
API base URL
https://highfollower.com/api/v1curl 'https://highfollower.com/api/v1/pages' \
-H 'Authorization: Bearer YOUR_API_TOKEN' \
-H 'Accept: application/json'/pagesRequired scope:pages:read
{
"status": "ok",
"message": "",
"data": [],
"meta": {
"per_page": 50,
"next_cursor": null,
"has_more": false
}
}The page parameter is the internal page ID, distinct from the Instagram page_id. Read conversation_key from the conversations list and URL-encode it in paths.
Lists except /pages and /tags use cursor pagination. Set per_page from 1 to 100 (default 50), then send meta.next_cursor as cursor with the original filters until meta.has_more is false. Treat cursors as opaque. Contacts sort by updated_at then id ascending; messages return newest first. Use overlapping updated_since windows and upsert contacts by ID. Dates use ISO 8601 and are converted to UTC.
done and updated_since; comments accept media_id and parent_id. Analytics accepts period=7
Both reply endpoints require a UUID Idempotency-Key header and nonblank message text up to 1,000 characters. Generate a new UUID for each new logical reply. Repeating the same key with the same page, target and text replays the recorded outcome; changing the content returns 409. A 503 with status=uncertain means delivery is in progress or unknown: reconcile the inbox before sending again, and never automatically retry with a new key.
curl -X POST 'https://highfollower.com/api/v1/pages/12/conversations/CONVERSATION_KEY/replies' \
-H 'Authorization: Bearer YOUR_API_TOKEN' \
-H 'Accept: application/json' \
-H 'Idempotency-Key: 7d598e78-eaf7-4eb4-9c48-7e57ef887902' \
-H 'Content-Type: application/json' \
-d '{"message":"Hello! How can we help?"}'To change conversation status, send status as open or done. To replace contact tags, send a tag_ids array; an empty array removes all tags.
Configure the URL and events and send a test webhook. Payloads contain id, type, api_version, occurred_at, platform_page_id, platform and data. Message and comment events include inbound and outbound items. A synced event signals that the application should reload the list.
Use a public HTTPS domain on port 443 that resolves to public IPv4, without URL credentials or fragments. Redirects are not followed. Enable each event and its associated read scope. Accept events durably before returning 2xx. Delivery can be duplicated or out of order; periodically reconcile your data through the API.
message.createdconversations:readmessage.deletedconversations:readconversation.updatedconversations:readdirects.syncedconversations:readcomment.createdcomments:readcomment.deletedcomments:readcomment.updatedcomments:readcomments.syncedcomments:readcontact.updatedcontacts:readlead.createdleads:readwebhook.test—{
"id": "f5e0c74f-364c-44ae-bc5b-486a2afba3b5",
"type": "message.created",
"api_version": "v1",
"occurred_at": "2026-10-02T10:00:00.000000Z",
"platform_page_id": 12,
"platform": "instagram",
"data": {
"id": "provider-message-id",
"message_id": "provider-message-id",
"conversation_key": "existing-conversation-key",
"sender": {
"id": "provider-user-id"
},
"message": {
"text": "Hello"
}
}
}X-HighFollower-Event-Id: f5e0c74f-364c-44ae-bc5b-486a2afba3b5
X-HighFollower-Timestamp: <Unix seconds>
X-HighFollower-Signature: sha256=<hex HMAC-SHA256>lead.created is emitted after a new Flow-collected data record commits and requires leads:read. Each saved field is a separate record; updating an existing record or replaying the same persistence operation does not create a new event. Data includes lead, page, Flow and execution IDs, sender ID, field name and value, source and creation time. This event is independent of contact.updated and does not require saving the same value to the contact profile.
{
"id": "591396d6-5561-52a5-9506-14e23f4e5c25",
"type": "lead.created",
"api_version": "v1",
"occurred_at": "2026-10-31T10:00:00.000000Z",
"platform_page_id": 12,
"platform": "instagram",
"data": {
"id": 42,
"platform_page_id": 12,
"automation_flow_id": 7,
"execution_id": 103,
"flow_node_id": "collect-phone",
"sender_id": "provider-user-id",
"field_name": "phone",
"value": "+989120000000",
"source_type": "direct",
"source_id": "provider-message-id",
"created_at": "2026-10-31T10:00:00.000000Z"
}
}Verify HMAC-SHA256(secret, timestamp + "." + raw_body) before parsing JSON. X-HighFollower-Signature starts with sha256=. Validate X-HighFollower-Timestamp within five minutes and persist the event id to deduplicate processing.
import hashlib, hmac, json, time
def verify_webhook(raw_body, headers, secret):
timestamp = headers["X-HighFollower-Timestamp"]
if abs(time.time() - int(timestamp)) > 300:
raise ValueError("Expired webhook")
digest = hmac.new(
secret.encode(), timestamp.encode() + b"." + raw_body,
hashlib.sha256,
).hexdigest()
if not hmac.compare_digest(
"sha256=" + digest, headers["X-HighFollower-Signature"]
):
raise ValueError("Invalid signature")
return json.loads(raw_body)
# Deduplicate the verified payload["id"] in your database.
# Return 2xx after durably accepting the event.2xx acknowledges receipt. Network errors, 408, 425, 429 and 5xx retry up to eight attempts; other responses, including redirects, fail. Retry delays are 1, 5, 15, 60, 180, 360 and 720 minutes plus queue delay. Event IDs stay stable. History lasts 30 days. Changing the URL or secret cancels pending deliveries from the previous configuration.
API and webhooks require an active paid Pro subscription (10 active integrations by default; see your subscription allowance). Trials do not include API access. Limits are 120 requests per minute per integration and 240 per source IP. On 429, wait for Retry-After seconds. Replies require an active page, valid provider credentials and sufficient credit. Subscription expiry stops requests and webhooks but retains keys.
401: invalid, revoked or expired token. 403: missing scope or inactive sending page. 404: missing or out-of-scope resource. 409: Idempotency-Key reused for different content. 422: invalid input or plan_limit_reached. 429: rate limit exceeded. 503 with status=uncertain: reply delivery is unknown or in progress; check the inbox before another send.