[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own Procore API

> Procore: an app on its API reaches production only after Procore verifies the developer. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/procore

Procore: public API docs, with production access only after Procore verifies the developer (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Procore account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Procore session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=procore)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Procore. Procore is a trademark of its owner. If Procore's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/open-rfis" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"project": "Harbor Tower", "older_than_days": 10}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/open-rfis";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ project: "Harbor Tower", older_than_days: 10 }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/open-rfis",
headers={"Authorization": f"Bearer {key}"},
json={"project": "Harbor Tower", "older_than_days": 10},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"number": "RFI 041",
"subject": "Beam clash at grid C4",
"assignee": "Architect",
"due_date": "2026-11-18",
"days_open": 12
},
{
"number": "RFI 044",
"subject": "Door hardware spec",
"assignee": "Owner",
"due_date": "2026-11-20",
"days_open": 11
}
]
}
```

01 Build

## How do you build a Procore endpoint with Cotlet?

1. 01  
login.procore.com  
Signed in  
### Sign in to Procore in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the open RFIs on the project older than the given number of days, with the assignee and due date.  
### Do the job once with your agent.  
For example: "List the open RFIs on the project older than the given number of days, with the assignee and due date."
3. 03  
Save endpoint  
Name  
open-rfis  
Input  
project, older\_than\_days  
Returns  
number, subject, assignee, due\_date, days\_open  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a project or a number of days, and the fields it returns.
4. 04  
$ POST /api/v1/custom/open-rfis  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Procore session.

02 Endpoints

## Example endpoints you could build for Procore

Cotlet ships no fixed list of Procore endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/open-rfis`  
### Open RFIs  
Number, subject, assignee, due date and days open for each RFI
- POST `/api/v1/custom/overdue-submittals`  
### Overdue submittals  
Submittal, spec section, due date and ball in court
- POST `/api/v1/custom/punch-items-by-location`  
### Punch items by location  
Open items on a level or room, with trade and assignee
- POST `/api/v1/custom/latest-drawing`  
### Latest drawing revision  
The current revision of a drawing, with its date
- POST `/api/v1/custom/assign-punch-item` writes  
### Assign a punch item  
A punch item set to a subcontractor with a due date
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/open-rfis" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"project": "Harbor Tower", "older_than_days": 10}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"number": "RFI 041",
"subject": "Beam clash at grid C4",
"assignee": "Architect",
"due_date": "2026-11-18",
"days_open": 12
},
{
"number": "RFI 044",
"subject": "Door hardware spec",
"assignee": "Owner",
"due_date": "2026-11-20",
"days_open": 11
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your Procore endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A Monday project report.  
Open RFIs and overdue submittals, sent to the team in Slack or email.
- Schedule endpoint Google Sheets  
### Punch items in a sheet.  
Open items by level and trade, pulled into Google Sheets for the walk.
- Field form endpoint punch item  
### A field form that files items.  
A form on site that assigns a punch item in Procore after your OK.
- Chat agent endpoint latest drawing  
### Your own project assistant.  
A chat agent that reads the latest drawing revision before it answers the team.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Procore session, so it can read and change only what your Procore login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as assigning a punch item, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/assign-punch-item

would POST login.procore.com/... assign "Patch hole by door 214" to the drywall sub

`assign-punch-item`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Procore have an official API?

Procore: public API docs and a free sandbox; "Verification gates production only", and a customer building for its own company is verified by a Procore reviewer (checked 20 Nov 2026). A company admin can create webhooks, and Procore has a Zapier app. The full picture with sources: [Does Procore have an API or MCP server?](https://cotlet.dev/api-status/procore.md)

Want ChatGPT or Claude to work in Procore instead of code? See the [Procore MCP server](https://cotlet.dev/integrations/procore-api-mcp-server.md).

1/3

Official API

After verification

[Full API & MCP report](https://cotlet.dev/api-status/procore.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## Procore API with Cotlet: questions

### Is this an official Procore API?

No. Cotlet is independent and not affiliated with Procore. The endpoints you build run in your own signed-in Procore account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when Procore changes its screens?

An endpoint works while Procore works the way it did when you built it. If Procore changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first Procore endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=procore)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
