How to Find Your API Key in OnPipeline

OnPipeline calls its credential an API token, and an admin creates it in Settings. There is a second step that most guides omit and that OnPipeline enforces strictly: every token has its own IP allow-list, and requests from an address that is not on it are rejected outright. A perfectly valid token with an empty allow-list cannot make a single successful call.

You need to be an admin on the OnPipeline account.

Steps to create an OnPipeline API token

1. Open the API settings In OnPipeline, go to Settings, then API — or go straight to app.onpipeline.com/settings/?api.

2. Create a token Click Create a Token. In the New Token panel, give it a name that identifies the tool you are connecting and leave the type as Read and Write (this is the default, and a read-only token cannot add or update contacts). Click Save.

3. Copy the Secret Token The token appears next to the Secret Token label. Copy it — this is the value the integration asks for, even if the field is labelled "API token".

4. Whitelist the IP addresses — do not skip this Click Whitelisted IP sources on the token, and add the addresses allowed to use it. To allow any address, enter 0.0.0.0. Save, and confirm the token row now shows the allow-list you set.

Why the allow-list matters so much

If the calling address is not whitelisted, OnPipeline answers with a 403 and a message about an invalid IP — not an authentication error. That mismatch is what makes this hard to diagnose: the token is fine, so people assume they copied it wrong and generate another one, which fails in exactly the same way.

Cloud integrations are the common case here. A hosted tool does not call from your office and its outbound address can change without notice, so unless the vendor publishes a fixed IP to whitelist, 0.0.0.0 is the setting that works. If you do have a fixed address to allow, use it — a narrower allow-list is genuinely safer.

Keeping the token safe

Create one token per integration so you can suspend or delete a single tool's access without disturbing the others. Both actions live on the same Settings → API page, alongside the allow-list you set when you created it.

Connecting OnPipeline to LinkedIn with Add to CRM

Add to CRM uses your OnPipeline token to add contacts straight from LinkedIn, Gmail and Outlook, with verified email addresses and phone numbers already filled in. Paste the Secret Token once on the connect screen — with the IP allow-list set — and every profile you open is one click from OnPipeline.