Force24 API

Name: Force24 API
Brand: Force24 API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationoauth240 EndpointsREST

For Agents

Manage contacts, send email and SMS campaigns, read web activity, and adjust subscription preferences across Force24 marketing automation from agent code.

Install Jentic One Beta

Connect the Force24 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Force24 API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Force24 API.

Create, update, find, and erase contacts in the Force24 database

Look up recently changed and deleted contacts for incremental sync

Pull email campaign sent items, opens, clicks, unsubscribes, and bounces

GET STARTED

Start building with Force24 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Force24 API for, with concrete tasks.

★ CRM-to-Force24 Contact Sync

Mirror your CRM's contacts into Force24 by calling /api/contacts/upsert on every change, then read /api/contacts/recents and /api/contacts/deleted on a schedule for reverse sync. This keeps marketing automation aligned with the source-of-truth contact data without dual entry. Initial setup takes a few days including field mapping and consent handling.

Upsert a contact via /api/contacts/upsert with email 'lead@example.com' and the latest first name, last name, and lead source from the CRM.

Campaign Engagement Reporting

Pull engagement events from /api/email/opens, /api/email/clicks, /api/email/unsubscribes, and /api/email/bounces to feed an attribution dashboard or a lead-scoring model. Each endpoint returns event records keyed by campaign and contact, ready to join with your warehouse contact records. Useful for marketing ops teams that want raw event-level data outside the Force24 UI.

List email opens via /api/email/opens for campaign ID '4521' since yesterday and return the count of unique contacts who opened.

List Membership Management

Add and remove contacts from marketing lists through the marketing-list and marketing-list-contacts endpoints to drive segmentation. Suits agents that respond to events such as 'webinar registered' or 'lead became MQL' by moving the contact into the right nurture list. Each list supports dynamic membership updates without re-uploading the whole audience.

Add the contact with GUID '7f2b...' to the Force24 marketing list named 'Spring Webinar Registrants'.

Subscription Preference Updates

Use the subscription-preferences endpoints to record opt-outs, consent updates, and channel preferences as customers change their minds. Critical for UK GDPR and PECR compliance — the API lets your downstream systems push preference changes back into Force24 immediately. Each preference is keyed to the contact and a channel.

Update the subscription preference for contact GUID '9c10...' to opt out of SMS while keeping email opted in.

AI Agent Marketing Integration via Jentic

Agents use Jentic's intent search to find Force24 operations, load the schema for contact upsert or campaign reporting endpoints, and execute calls under a scoped OAuth credential. This is the recommended pattern for AI assistants embedded in CRMs that need to push or pull marketing data without a custom backend. Jentic keeps the OAuth tokens isolated.

Use Jentic to search 'upsert a Force24 contact', load the /api/contacts/upsert schema, and synchronise the contact record the user named with the latest CRM values.

Key Endpoints

40 endpoints — jentic publishes the only available openapi specification for force24 api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/contacts/upsert

Upsert a contact

POST

/api/contacts/find

Find a contact by email or other field

GET

/api/contacts/recents

List recently changed contacts

GET

/api/contacts/deleted

List recently deleted contacts

GET

/api/email/opens

Read email open events

GET

/api/email/clicks

Read email click events

GET

/api/email/bounces

Read email bounce events

GET

/api/email/unsubscribes

Read email unsubscribe events

POST

/api/contacts/upsert

Upsert a contact

POST

/api/contacts/find

Find a contact by email or other field

GET

/api/contacts/recents

List recently changed contacts

GET

/api/contacts/deleted

List recently deleted contacts

GET

/api/email/opens

Read email open events

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Force24 OAuth 2.0 client credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token and never see the raw client secret, and Jentic refreshes the access token transparently between calls.

Intent-based discovery

Agents search by intent (e.g. 'upsert a Force24 contact') and Jentic returns the /api/contacts/upsert operation with its input schema, so the agent supplies the right contact fields without browsing Force24 docs.

Time to first call

Direct Force24 integration: 3-5 days for OAuth wiring, contact sync logic, engagement reporting, and consent handling. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using Force24 API through Jentic.

Why is there no official OpenAPI spec for Force24 API?

Force24 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Force24 API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Force24 API use?

The Force24 API uses OAuth 2.0. Generate client credentials in the Force24 portal and exchange them for an access token. Jentic stores the client credentials encrypted in the MAXsystem vault and refreshes tokens automatically.

Can I sync contacts in both directions with the Force24 API?

Yes. Push changes via /api/contacts/upsert and pull recent changes via /api/contacts/recents and deletions via /api/contacts/deleted. Together these endpoints support a bidirectional sync between Force24 and an external CRM.

What are the rate limits for the Force24 API?

The OpenAPI spec does not declare explicit rate limits. Force24 enforces account-level throughput in production — back off on 429 responses and stagger bulk contact uploads.

How do I pull email engagement events through Jentic?

Search Jentic for 'list Force24 email opens', load the /api/email/opens schema, and execute with the campaign and date range. Repeat with /api/email/clicks, /api/email/bounces, and /api/email/unsubscribes for the full engagement picture.

Does the Force24 API support GDPR-style consent updates?

Yes, the subscription-preferences endpoints record opt-in and opt-out state per contact and channel. Use these to push consent changes from a preference centre or unsubscribe handler back into Force24.

Force24 API

Connect the Force24 API to your agent

Capabilities

Start building with Force24 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs