Send leads to your CRM with the API
Make an API key in your account settings so your website, Zapier, Make or your own code can add people to the CRM of one or more of your startups, hear about changes, or let Claude and Cursor use it.
Your CRM can take leads from other tools without a connected app: your website, Zapier, Make, n8n, a script, or an AI tool such as Claude. They all use an API key, which is part of Plus: keys, webhooks and connected apps work while you are on Plus (on Free, API & webhooks shows Part of Plus and New key and Add webhook are off), and the ones you have work again as soon as you go Plus. A key is yours, not a startup's: one key can reach the CRM of every startup you tick. You can tick a startup where you are an owner or admin; other members ask one of them. For a plain contact form on your website, you need no key: see Add a form to your website.
Make a key
- Open Account settings from your name at the bottom of the menu, then API & webhooks, and stay on the API keys tab.
- Choose New key.
- Give it a Name, like Website form or Zapier.
- Under Startups it can reach, tick the startups it is for, or All my startups, including ones I add later.
- Tick what It may do. Reading and changing people, companies and deals is ticked already. Tick Add to pipelines and move stages too so your leads land in a pipeline (see below). Tick Manage fields and pipelines only for a tool that sets up your CRM: it lets the key add fields and pipelines. Read tables in Files and Change tables in Files: rows and columns let it use the startup's tables. Read tasks and Create and change tasks let it use the startup's tasks.
- Choose Make key, copy the key, then choose I copied it. It only shows once.
The list shows each key's startups and when it was last used. Keep the key on a server or in your tool's secrets, never in a web page's code: anyone with it can change those CRMs as you. A key stops working when you Revoke it, and while your account is suspended. It stops reaching a startup when you are no longer an owner or admin there, or leave it.
Add or update a person
Send one request per lead. If someone with that email is already in the CRM, they are updated instead of added twice, and their company is found by its domain, or made.
curl -X PUT "https://startupcorners.com/api/v1/objects/people/records?matching_attribute=email&entity=your-startup" \
-H "Authorization: Bearer $STARTUPCORNERS_KEY" \
-H "Content-Type: application/json" \
-d '{"values": {"name": "Jane Doe", "email": "jane@acme.com",
"company": {"domain": "acme.com", "name": "Acme"}}}'
The answer is the record, with 201 when it was added and 200 when it was updated. The API keys tab shows this example in curl and JavaScript, with your startup's name in it.
Fields are named by their key, like name, email or job_title, which the CRM settings show as each field's API name. The field's name as people see it works too ("Check size": 250000). GET /api/v1/objects/people/attributes lists them with their types and choices. A renamed field gets a new key from its new name when no key or webhook reached your CRM, or when an admin chose it; the old key keeps working for what you send (see Rename a field). A choice is written as its label ("stage": "Intro sent"), an amount as {"amount": 250000, "currency": "USD"}, a date as 2026-10-28.
When you have several startups
Every request names its startup with ?entity= and the startup's address name (the part after /s/ in its link) or its id. A key that reaches one startup can leave it out.
GET /api/v1/entitieslists the startups your key reaches, with their address names.- Without
?entity=, a key that reaches several answers400entity_required, with that list. - A startup the key does not reach answers
403entity_not_allowed.
Put someone in a pipeline
The CRM's home shows what is in your pipelines. A person or company added without one is saved, but you find it only under People or Companies, so send leads into a pipeline.
GET /api/v1/listslists your pipelines, like Fundraising and Customers, with their stages and what each holds: Fundraising holds companies, Network people, Customers deals.- Add
"list"and"stage"next to"values"when you add or update a record, and it goes in that pipeline in the same request:{"values": {"name": "Acme", "domain": "acme.com"}, "list": "fundraising", "stage": "Intro sent"}. Without a stage it goes in the first one. The key needs Add to pipelines and move stages ticked too (lists:write): a new key starts without it, so tick it when you make the key, or make a new one. - For Customers, add a deal for the company and send the deal with
"list": "customers":POST /api/v1/objects/deals/recordswith{"values": {"name": "Acme", "company": {"domain": "acme.com"}}, "list": "customers", "stage": "Lead"}. - A record already in the CRM goes in with
POST /api/v1/lists/fundraising/entriesand{"record_id": "...", "stage": "Intro sent"}. PATCH /api/v1/entries/{id}with{"stage": "Term sheet"}moves it.DELETE /api/v1/entries/{id}takes it out of the pipeline. The contact and its notes stay in the CRM.
Notes go in with POST /api/v1/records/{id}/notes and {"text": "Met at the demo day."}. Every change made with a key shows on the record's history like any other. Every endpoint is in the API reference.
When something goes wrong
Errors come back as {"error": {"code": "...", "message": "..."}}. The ones you will meet:
401: the key is missing, wrong or revoked, reaches no startup any more, or belongs to a suspended account.403plus_required: the key's maker is not on Plus. It works again once they are.403: the key may not do this, or does not reach that startup. Make a key with the right ticks.409duplicate: that email or domain is already on a record; the answer gives its id. Use the update request above instead.413: the request body is over 5 MB. Send fewer rows at a time.422invalid_value: a field or a choice does not exist, or a value is not valid. The message names the field.429: more than 100 requests in 10 seconds. Wait the seconds inRetry-After.
Hear about changes: webhooks
A webhook posts to your URL when something changes in a startup, for example to start a Zap: its CRM (records, pipelines, notes, website forms), its tasks (created, changed, done, deleted) or its tables in Files (rows added, changed, deleted).
- In API & webhooks, choose the Webhooks tab, then Add webhook.
- Paste the URL (it must start with https and lead to a public address, not one on a private or local network), tick the Startups it can reach, tick when to post under Post when, and choose Add webhook.
- Copy the signing secret, then choose I copied it.
Each post holds the event, the startup it is about (entity, with its slug), and the ids of what changed (record_id, list_id, entry_id, task_id, table_id, row_id, form_id); read the rest with your key. Tasks and tables post for the startup's own, not personal ones, and a row only to webhooks whose maker can open its table. Step by step for Zapier and Make: Connect Zapier or Make. The tab shows code to check the StartupCorners-Signature header with the secret. When your URL does not answer, or no longer leads to a public address, we try again for about a day. After 3 days of failures the webhook is paused and you get an email; choose Turn on once it works again.
Use your CRM from Claude or Cursor
Your CRM is also an MCP server, so an AI tool can look up people and deals, list the contacts a saved view shows, add leads, move stages, take someone out of a pipeline, write and delete notes and, with Manage fields and pipelines, add fields, choices and pipelines, as far as its key allows. With the tables boxes ticked it also works in any table of your Files: read it, sorted by a column or searched across the whole table or through one of its saved views, add and change rows, add columns, add, change or delete its views (a board, a calendar, a gallery), rename or move it, and move it to the trash.
- Make a key. For questions only, tick just the reading ones.
- In API & webhooks, choose the AI tools tab and pick your tool: Claude Code, Cursor, Claude Desktop, Codex, ChatGPT or n8n (see Connect n8n and Connect ChatGPT or Codex).
- Copy the setup shown, put your key in place of
sc_live_..., and add it to your tool.
Then ask, for example, which investors in Fundraising have not moved in two weeks. A key that reaches several startups lets the tool ask which one, or you name it: "add Jane to Kumo's Customers".
In claude.ai and the Claude apps you need no key: add StartupCorners as a connector and sign in, as Connect Claude to your CRM and tables shows. The AI tools tab links to Connected apps for it.
