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.
| Scope | Allows |
|---|---|
evals:read | Read companies and their scores. |
evals:write | Submit companies for scoring. |
webhooks:manage | Create, change and delete webhooks. |
deals:read | Read deals you can see in the app. |
deals:write | Create and change deals. |
notes:read | Read deal notes. |
notes:write | Add notes to deals. |
outcomes:write | Record what happened to a company later (raised, failed, exited). |
reports:read | Read LP reports, memos and fund reports. |
usage:read | Read usage and credit balance. |
members:read | Read the fund's member list. |
diligence:run | Start diligence runs. This spends credits. |
decisions:write | Record Pass, Meet or Invest decisions. |
memos:write | Write and generate memos. Generating spends credits. |