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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fforce24.co.uk%2Fforce24" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fforce24.co.uk%2Fforce24" | 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

Send SMS campaigns through the SMS endpoints

Add and remove contacts from marketing lists

GET STARTED

Start building with Force24 API

Explore with Jentic One

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

GET

/api/email/clicks

Read email click events

GET

/api/email/bounces

Read email bounce events

GET

/api/email/unsubscribes

Read email unsubscribe events

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Force24 API by hand means running its OAuth 2.0 client-credentials flow, refreshing the access token between calls yourself, and building your own retry and error handling across contact and campaign endpoints. Through Jentic you install once, import Force24 from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

Force24 carries the contact and campaign targets in the request body rather than the URL path, so scoping is operations-only: you limit the agent to the operations it needs, such as upserting or finding a contact, and leave out the email and SMS reporting endpoints unless you add them. Every operation the agent can run is one you chose.

Credential isolation

Your Force24 OAuth client credentials are stored once, encrypted, by your own Jentic One instance, which handles the token refresh and injects the access token at execution time. The client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as '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 the reference docs.

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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Force24 API?

Yes. Because you run Jentic One yourself, your own rules decide which Force24 operations and credentials the agent may use. Force24 passes the contact and campaign targets in the request body rather than the URL, so scoping is operations-only: you allow just the operations the agent needs, such as /api/contacts/upsert or /api/contacts/find, and leave out the email and SMS reporting endpoints unless you add them. Every operation the agent can call is one you chose.

Force24 API

AI ReadinessFoundational (C)53/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMarketingMarketing Automationoauth240 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to upsert a contact in Force24 with the latest CRM data, I want to list all email opens for a recent campaign, Find a Force24 contact by email address, Get all bounces from the last campaign send

Not supported: Does not handle ad campaigns, CRM deal management, or web analytics dashboards - use for Force24 contacts, email and SMS campaigns, marketing lists, and subscription preferences only.

Jentic publishes the only available OpenAPI specification for Force24 API, keeping it validated and agent-ready. Force24 is a UK marketing automation platform that combines email, SMS, and behavioural tracking. The API exposes endpoints for managing contacts, sending email and SMS campaigns, maintaining marketing lists and list memberships, reading web activity tracking data, and adjusting subscription preferences. Authentication is OAuth 2.0.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

79%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

35%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

30%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Force24 API to your agent

Capabilities

Start building with Force24 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Force24 API

Jentic AI Readiness Score

Force24 API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness