AI AgentPlatform
PricingSign inBook a demo
Personyze
Pricing
REST API integration

Everything the panel does, over HTTP

One authenticated API covering profiles, lists, catalogs, campaigns, decisions and reporting — plus server-side SDKs for Node, PHP and Python, and native SDKs for Android and iOS.

{;} + P

REST API  ·  PERSONYZE

HTTP Basic with your account keyServer-side decisions in one callNode, PHP, Python, Android, iOS
The problem

Some pages are rendered before a browser is involved.

Server-rendered frameworks, native apps, kiosk screens, and anything behind a login all need the decision before the markup exists. The same audiences and the same campaigns are reachable from your own code, in one call, without waiting for a tag to load.

What it unlocks

Four ways in.

The REST API

Visitor profiles and custom columns, user lists and membership, ranked interests, product and content catalogs, campaigns, actions, placeholders, goals, events, forms and aggregated results.

Server-side SDKs

Node, PHP and Python ports of one endpoint, with a shared written contract so all three behave identically — sessions, decisions, events and purchases in a single call.

Mobile SDKs

Android and iOS handle the session lifecycle, report navigation and interactions, and render returned content into a view you position.

How it works

It fails in the right direction.

01

A budget, not a hope

The whole decision, retries included, is bounded at 1000 ms. It does not get to hold your page open.

02

Fail open on reads

A timeout, a connection error, a 5xx or simply no matching campaign all resolve to an empty decision set. Your page renders either way.

03

Fail loud on configuration

A 400 or 401 raises, even from the decision call — because a bad key is a bug, not weather.

Questions

Before you connect it.

How is it authenticated?
HTTP Basic: the username is the literal api and the password is your account API key. The same key the MCP server, Zapier and the community nodes use.
What happens if Personyze is slow?
Nothing, on your side. The read path is fail-open with a one-second ceiling on the whole operation, so a slow or unreachable service produces an empty result rather than a blocked render.
Can I run an A/B test server-side?
Yes, but the decision endpoint only returns actions built for it. Assemble a server-side test from the server-side decision action type rather than from ordinary browser actions, or it will return nothing.
Do I need the JavaScript tag as well?
Not for decisions. The tag is what collects behaviour automatically; if you are server-side only, you report what matters through the same API.
Ready when you are

Read the reference, or just try it.

The API key is in your account settings on every plan, including the free one.

FREE PLAN · NO CARD NEEDED · NOTHING TO INSTALL ON REST API