GenPage External API Documentation

Name: GenPage External API Documentation API
Brand: GenPage External API Documentation
Availability: InStock

✓ Official Vendor SpecMarketingMarketing AutomationapiKey14 EndpointsREST

For Agents

Push leads, list campaigns and audiences, and manage API tokens for AI-personalised B2B landing pages on GenPage.

Connect the GenPage External API Documentation to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 GenPage External API Documentation API.

Upsert leads in bulk and poll the resulting job until each personalised page is generated

Push individual leads from Zapier into a target campaign without writing integration code

List campaigns and audiences to keep external CRMs and dashboards in sync

Retrieve workspace merge variables to build template-aware lead payloads

GET STARTED

Start building with GenPage External API Documentation API

Explore with Jentic

View OpenAPI Document

GenPage generates AI-personalised landing pages for B2B sales outreach, with each page tailored to a single lead, audience segment, or campaign. The API exposes 14 external endpoints for upserting leads, listing campaigns and audiences, retrieving workspace variables used in page templates, and managing API tokens. A Zapier integration path lets ops teams push leads from existing CRMs without custom plumbing. Outbound teams use GenPage to attach a personalised page link to every cold email or LinkedIn message.

Use Cases

Patterns agents use GenPage External API Documentation API for, with concrete tasks.

★ Cold Outbound Personalisation

Sales teams running cold email or LinkedIn outreach attach a GenPage personalised landing page link to every message. The API accepts batches of leads via /api/external/v1/leads/upsert-leads with company and persona variables, and GenPage generates a unique URL per lead. The link reflects the prospect's company, role, and any custom workspace variables, lifting reply rates compared to a generic landing page.

Upsert 50 leads to campaign {campaign_id} via /api/external/v1/leads/upsert-leads, then poll /api/external/v1/leads/get-status until the job completes.

Zapier-Driven Lead Sync

Teams already using Zapier can wire their CRM, form provider, or enrichment tool directly into GenPage via /api/external/v1/zapier/upsert-lead. Each new lead in the source system triggers a personalised page creation without engineering effort. Authentication is verified via /api/external/v1/zapier/test before the Zap goes live.

Create a Zapier-style lead via POST /api/external/v1/zapier/upsert-lead with the lead's email, company, and campaign reference.

Campaign and Audience Reporting

Marketing ops pulls the campaign and audience lists, plus workspace variables, to keep external dashboards or BI tools in sync with GenPage. /api/external/v1/campaigns/get-list and /api/external/v1/audiences/get-list return the current entities, and /api/external/v1/workspaces/get-variable-list returns the merge tags available in templates.

Fetch all campaigns and audiences via the get-list endpoints and write the data to a Google Sheet for the weekly outbound review.

AI Agent Integration via Jentic

An agent built on Jentic can take a list of target accounts from a research pass, push them as leads into a GenPage campaign, and return personalised URLs to the email-drafting step. Jentic isolates the API token in the vault so the agent never sees the raw credential.

Search Jentic for 'upsert leads to genpage', load the upsert-leads schema, and execute it with a list of 10 prospect emails and company names.

Key Endpoints

14 endpoints — genpage generates ai-personalised landing pages for b2b sales outreach, with each page tailored to a single lead, audience segment, or campaign.

METHOD

PATH

DESCRIPTION

POST

/api/external/v1/leads/upsert-leads

Upsert multiple leads in one call

POST

/api/external/v1/leads/upsert-lead

Upsert a single lead

GET

/api/external/v1/leads/get-status

Check status of a lead-upsert job

GET

/api/external/v1/campaigns/get-list

List all campaigns

GET

/api/external/v1/audiences/get-list

List all audiences

POST

/api/external/v1/zapier/upsert-lead

Create a lead through the Zapier endpoint

POST

/api/external/v1/generate-api-token

Generate a new API token

POST

/api/external/v1/leads/upsert-leads

Upsert multiple leads in one call

POST

/api/external/v1/leads/upsert-lead

Upsert a single lead

GET

/api/external/v1/leads/get-status

Check status of a lead-upsert job

GET

/api/external/v1/campaigns/get-list

List all campaigns

GET

/api/external/v1/audiences/get-list

List all audiences

Why though Jentic?

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

Credential isolation

GenPage bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped operation handles, never raw tokens, so the credential never enters agent context or logs.

Intent-based discovery

Agents search Jentic with intents like 'create a personalised landing page for a lead' and Jentic returns the matching upsert-lead operation with its input schema, so the agent calls the correct path without crawling docs.

Time to first call

Direct GenPage integration: half a day for token management, batch upserts, and job polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Expertease apis

Another AI-driven backend, focused on chatbots rather than landing pages

Choose ExpertEase for conversational chatbot deployment; choose GenPage when the goal is per-lead personalised landing pages.

Complementary

Bandsintown

Event data API that could feed niche outreach personalisation

Use Bandsintown when running events-industry outbound and pair it with GenPage to render personalised event-themed pages.

Complementary

Bacon Ipsum

Filler text generator for testing GenPage templates before production lead loads

Use during template development to dry-run page rendering without burning real lead records.

FAQs

Specific to using GenPage External API Documentation API through Jentic.

What authentication does the GenPage API use?

The API uses API key authentication via an Authorization header containing a bearer token. Tokens are generated through POST /api/external/v1/generate-api-token and listed via GET /api/external/v1/get-api-tokens. When called through Jentic, the token is held in the encrypted vault and never exposed to the agent's runtime.

Can I upsert leads in bulk through the GenPage API?

Yes. POST /api/external/v1/leads/upsert-leads accepts a batch of leads. The endpoint returns a job ID, and you poll /api/external/v1/leads/get-status until processing finishes. Use /api/external/v1/leads/get-leads to retrieve the leads attached to that job.

What are the rate limits for the GenPage API?

Rate limits are not declared in the OpenAPI spec. Limits are enforced per API token at the GenPage backend; check the GenPage docs at https://backend.genpage.ai/docs/openapi.yaml or contact GenPage support before high-volume bulk upserts.

How do I push leads from my existing tooling without writing custom code?

Use the Zapier-specific endpoint POST /api/external/v1/zapier/upsert-lead. Test the connection first with GET /api/external/v1/zapier/test to confirm your token authenticates. Through Jentic, you can search 'create a genpage lead via zapier' to load the schema directly.

How do I find which merge variables I can use in a campaign?

Call GET /api/external/v1/workspaces/get-variable-list to retrieve the merge tags available in your workspace. These are the variables the page template will substitute when generating the personalised landing page for each lead.

How do I revoke an API token if it leaks?

List your tokens via GET /api/external/v1/get-api-tokens, identify the compromised token, then call DELETE /api/external/v1/delete-api-token to revoke it. Generate a replacement with /api/external/v1/generate-api-token and rotate it in your integrations.