Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Payments / Newie Public API
Newie Public API logo

Newie Public API

★ Only Publicly Available OpenAPI DocumentPaymentsBilling SubscriptionsapiKey3 EndpointsREST

For Agents

Subscribe to Newie purchase, subscription, payment, and payout webhook events so an agent reacts to creator-economy revenue activity without polling.

Use for: Subscribe to Newie purchase events via webhook, Create a REST hook for new Newie subscriptions, I need to receive Newie payment events on my server, Set up a payout event webhook for Newie

Not supported: Does not handle payment processing, payout disbursement, or creator account management — use for REST hook subscription lifecycle against Newie events only.

Jentic publishes the only available OpenAPI specification for Newie Public API, keeping it validated and agent-ready. The Newie Public API offers a REST hooks implementation for provider integrations with the Newie creator-payments platform. Providers can verify their API token and create or destroy webhook subscriptions for purchase, subscription, payment, and payout events. Authentication uses an X-API-TOKEN header generated inside the Newie app.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Newie Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Newie Public 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.

1

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
2

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 Newie Public API.

Verify a Newie API token before establishing webhook subscriptions

Create REST hook subscriptions for purchase, subscription, payment, and payout events

Destroy an existing REST hook subscription to stop receiving events

Authenticate every request with an X-API-TOKEN header retrieved from the Newie provider app

Use a single subscription pattern across the four event types Newie supports

Use Cases

Patterns agents use Newie Public API for, with concrete tasks.

★ Real-Time Creator Revenue Webhooks

Creator platforms and revenue dashboards subscribe to Newie purchase, subscription, payment, and payout events so transactions appear instantly in their tooling. POST /restHooks_create registers a callback URL for the chosen event type and Newie pushes payloads to that URL as events occur, eliminating polling and matching the REST hooks pattern.

Call POST /restHooks_create with the desired event type ('purchase' or 'subscription' or 'payment' or 'payout') and the receiver URL; record the returned subscription id for later teardown.

Provider Token Validation

Before a provider integration goes live, GET /api_testAuth confirms the X-API-TOKEN issued in the Newie app is accepted. This catches misconfigured environment variables or rotated tokens during deployment instead of failing silently when real revenue events would be missed.

Send GET /api_testAuth with the configured X-API-TOKEN; block deployment if the response is not 200 so misconfigured credentials never reach production.

Webhook Lifecycle Management

Operations teams wire DELETE /restHooks_destroy into deprovisioning flows so when a customer cancels their integration the corresponding Newie subscription is torn down cleanly. This avoids stale receivers continuing to ingest payload they no longer have permission to handle.

On a customer cancellation event, call DELETE /restHooks_destroy with the stored subscription id and remove the subscription record from your own database.

AI Agent Revenue Event Reactor

An AI agent powering a creator's business operations uses Jentic to discover Newie operations, registers webhooks for the events it cares about, and reacts to each payload — for example sending a thank-you message on purchase events or reconciling payouts in the creator's accounting system, all without hand-coding the Newie client.

Use Jentic to search 'subscribe to newie purchase events', load POST /restHooks_create, execute it with the agent's ingestion endpoint, and route incoming purchase payloads to the thank-you message workflow.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/api_testAuth

Verify the X-API-TOKEN is valid

POST

/restHooks_create

Create a REST hook subscription for a specific event type

DELETE

/restHooks_destroy

Destroy an existing REST hook subscription

GET

/api_testAuth

Verify the X-API-TOKEN is valid

POST

/restHooks_create

Create a REST hook subscription for a specific event type

DELETE

/restHooks_destroy

Destroy an existing REST hook subscription

Why Jentic?

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

Credential management

Credential isolation

Newie X-API-TOKEN values are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw API tokens never enter the agent's context.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'subscribe to creator payment events') and Jentic returns the Newie REST hook operations with their input schemas, so the agent can call the right endpoint without browsing docs.

Time to first call

Time to first call

Direct Newie integration: 1-2 days for token setup, REST hook lifecycle, and webhook handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

General payments platform with webhook events for charges, subscriptions, and payouts

Choose Stripe when the agent operates on a self-managed creator product with full payment processing; choose Newie when integrating with the Newie creator economy platform specifically.

Complementary

Zapier Natural Language Actions

→

Webhook router that fans Newie events out to thousands of downstream apps

Pair Zapier with Newie when an agent needs to forward Newie events into many tools without writing per-tool integrations.

Complementary

HubSpot Marketing Events

→

CRM destination for Newie purchase and subscription events

Pair HubSpot with Newie when purchase events should create or update CRM contacts, deals, and marketing automations.

FAQs

Specific to using Newie Public API through Jentic.

Why is there no official OpenAPI spec for Newie Public API?

Newie does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Newie Public 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 Newie Public API use?

Newie uses an X-API-TOKEN header carrying the API token retrieved inside the Newie app under Provider settings. Through Jentic, the token is stored in the encrypted MAXsystem vault and injected at request time so it never reaches the agent's context.

Can I subscribe to Newie purchase events through the Public API?

Yes. POST /restHooks_create accepts an event type and a target URL and registers a REST hook so Newie pushes purchase, subscription, payment, or payout payloads to that URL as events occur. DELETE /restHooks_destroy removes the subscription when no longer needed.

What are the rate limits for the Newie Public API?

Rate limits are not declared in the spec. Because the API is webhook-driven rather than polled, normal usage is small — one or two subscribe calls per integration plus periodic auth checks — so limits rarely become a concern.

How do I test a Newie webhook integration through Jentic?

Use Jentic to search 'verify newie api token', load GET /api_testAuth, and execute it. Then search 'subscribe to newie purchase events' and execute POST /restHooks_create with a temporary endpoint URL to confirm Newie pushes events as expected.

Is the Newie Public API free?

API access is included with a Newie provider account. Tokens are issued inside the Newie app once the provider account is approved — there is no separate API tier to purchase.

GET STARTED

Start building with Newie Public API

Explore with Jentic
View OpenAPI Document