IdeaPulleyDocs
GuidesAPI referenceOpenAPI
Open app
  • Introduction
Get started
  • Authentication
  • API basics
  • Errors
  • Rate limits
Endpoints
  • Fund
  • Deals
  • Memos
  • Notes
  • Decisions and outcomes
  • Contacts and reports
  • Evaluations
  • Webhooks
  • More endpoints
Guides
  • Application form
  • Webhook events
  • Claude and ChatGPT (MCP)
  • Zapier, n8n and Polytomic
Authentication

Authentication

Each request needs an API key. A key acts as the person who made it, in one fund, and its scopes say what it can do.

API keys

Make a key in IdeaPulley under Settings → Developer. Send it in the Authorization header of each request as a Bearer token.

Authorization: Bearer sk-ip-…

You see a key one time only, when you make it. Keep it on your server. Do not put it in browser code.

What a key can do

A key can do only what its creator can do in the app today. If the creator's role changes, the key changes with it. If the creator leaves the fund, or you revoke the key, it stops at once. Each call goes into the fund's audit log with the key ID.

Scopes

A key with no scopes is read-only: it gets evals:read, deals:read, notes:read, reports:read, usage:read, members:read. Writes, spending and decisions need the scope set on the key by name.

ScopeAllows
evals:readRead companies and their scores.
evals:writeSubmit companies for scoring.
webhooks:manageCreate, change and delete webhooks.
deals:readRead deals you can see in the app.
deals:writeCreate and change deals.
notes:readRead deal notes.
notes:writeAdd notes to deals.
outcomes:writeRecord what happened to a company later (raised, failed, exited).
reports:readRead LP reports, memos and fund reports.
usage:readRead usage and credit balance.
members:readRead the fund's member list.
diligence:runStart diligence runs. This spends credits.
decisions:writeRecord Pass, Meet or Invest decisions.
memos:writeWrite and generate memos. Generating spends credits.
IdeaPulleyDocs
GuidesAPI referenceOpenAPI
Open app
  • Introduction
Get started
  • Authentication
  • API basics
  • Errors
  • Rate limits
Endpoints
  • Fund
  • Deals
  • Memos
  • Notes
  • Decisions and outcomes
  • Contacts and reports
  • Evaluations
  • Webhooks
  • More endpoints
Guides
  • Application form
  • Webhook events
  • Claude and ChatGPT (MCP)
  • Zapier, n8n and Polytomic
Authentication

Authentication

Each request needs an API key. A key acts as the person who made it, in one fund, and its scopes say what it can do.

API keys

Make a key in IdeaPulley under Settings → Developer. Send it in the Authorization header of each request as a Bearer token.

Authorization: Bearer sk-ip-…

You see a key one time only, when you make it. Keep it on your server. Do not put it in browser code.

What a key can do

A key can do only what its creator can do in the app today. If the creator's role changes, the key changes with it. If the creator leaves the fund, or you revoke the key, it stops at once. Each call goes into the fund's audit log with the key ID.

Scopes

A key with no scopes is read-only: it gets evals:read, deals:read, notes:read, reports:read, usage:read, members:read. Writes, spending and decisions need the scope set on the key by name.

ScopeAllows
evals:readRead companies and their scores.
evals:writeSubmit companies for scoring.
webhooks:manageCreate, change and delete webhooks.
deals:readRead deals you can see in the app.
deals:writeCreate and change deals.
notes:readRead deal notes.
notes:writeAdd notes to deals.
outcomes:writeRecord what happened to a company later (raised, failed, exited).
reports:readRead LP reports, memos and fund reports.
usage:readRead usage and credit balance.
members:readRead the fund's member list.
diligence:runStart diligence runs. This spends credits.
decisions:writeRecord Pass, Meet or Invest decisions.
memos:writeWrite and generate memos. Generating spends credits.