# Property Finder API and MCP server

> Property Finder has an API, but only for software partners it approves through the PF Developer Network, not for brokers directly (checked 11 Oct 2026). Partners pass a business review and a security and compliance audit, and each PF Expert client then chooses to authorize them.

Property portal for the UAE and the wider Middle East, where agencies and agents publish listings and receive leads through PF Expert.

## What is the Property Finder API?

Cotlet's Property Finder API exposes 11 endpoints for your own Property Finder account: list listings, get listing, get listing stats, list leads, list agents, get credits, create listing, update listing, publish listing, unpublish listing and upgrade listing. The list_listings endpoint returns listings in your agency with status, agent, price, quality score and active upgrade. Each endpoint takes simple JSON inputs like listing_id, agent_id or purpose and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Real estate](https://cotlet.dev/integrations/category/real-estate)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-11

Property Finder has an API, but only for software partners it approves through the PF Developer Network, not for brokers directly (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Property Finder with 11 endpoints (6 read, 5 write): your AI agent signs in as you and does the work.

## Does Property Finder have an official API?

Property Finder has an API, but only for software partners it approves through the PF Developer Network, not for brokers directly (checked 11 Oct 2026). Partners pass a business review and a security and compliance audit, and each PF Expert client then chooses to authorize them.

| Task | Property Finder official | Cotlet |
|---|---|---|
| List listings with status and quality score | Partly: Approved partners only | Yes |
| Create and publish a listing | Partly: Approved partners only | Yes |
| Unpublish a listing | Partly: Approved partners only | Yes |
| Read new leads | Partly: Approved partners only; their docs list lead webhook events | Yes |
| Upgrade a listing to Featured or Premium | No: Not described on the public PFDN pages; Credit Optimizer suggests upgrades inside PF Expert | Yes |
| Credit balance | No: Not described on the public PFDN pages | Yes |
| Do any of this from your own script or agent | No | Yes |

Sources: [PF Developer Network: integration guide](https://pfdn.propertyfinder.com/integration-guide), [PF Developer Network](https://pfdn.propertyfinder.com/), [Property Finder Enterprise API reference (password protected)](https://api-docs.propertyfinder.net/enterprise-api/index.html), [Property Finder Help: What is Spotlight?](https://support.propertyfinder.ae/hc/en-us/articles/24591893552018-What-is-Spotlight), [Property Finder Partner Hub: Credit Optimizer](https://www.propertyfinder.ae/partnerhub/credit-optimizer/), [Property Finder Partner Hub: Exposure Products](https://www.propertyfinder.ae/partnerhub/exposure-products/)

## For AI agents

```text
Property Finder has an API, but only for software partners it approves through the PF Developer Network, not for brokers directly (checked 11 Oct 2026). Partners pass a business review and a security and compliance audit, and each PF Expert client then chooses to authorize them.
Cotlet provides a hosted MCP server and REST API for Property Finder: 11 tools (6 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=property-finder; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/property-finder
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_listings, get_listing, get_listing_stats, list_leads, list_agents, get_credits, create_listing, update_listing, publish_listing, unpublish_listing, upgrade_listing
Confirm      update_listing, publish_listing, unpublish_listing, upgrade_listing (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/property-finder-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=property-finder (Property Finder is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Property Finder once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Property Finder server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Property Finder in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Property Finder's terms; Cotlet is not affiliated with Property Finder.
```

## What can an AI agent do in Property Finder?

Cotlet is best for brokerages and agents on Property Finder who want listings published, leads read and credits spent from their own agent or script without running or fixing a server.

- **[Weekly listing performance report](https://cotlet.dev/integrations/property-finder-api-mcp-server/weekly-listing-performance-report)** (runs: weekly): "Every Monday, list my live rentals with the most views and no leads since last Monday, grouped by agent, and tell me which upgrades expire this week." → `list_listings`, `get_listing_stats`
- **[Bulk upload listings from a spreadsheet](https://cotlet.dev/integrations/property-finder-api-mcp-server/bulk-upload-listings-from-spreadsheet)**: "Create a draft for each row in units.csv, assign it to the agent in the last column, and publish the rows marked ready as standard listings." → `list_agents`, `create_listing`, `publish_listing`
- **[Daily new leads digest](https://cotlet.dev/integrations/property-finder-api-mcp-server/daily-new-leads-digest)** (runs: daily): "Every morning at 8, send me yesterday's Property Finder leads grouped by agent, with the listing each lead asked about." → `list_agents`, `list_leads`
- **[Fix low quality score listings](https://cotlet.dev/integrations/property-finder-api-mcp-server/fix-low-quality-score-listings)**: "Find my live listings with a quality score under 85, tell me what each one is missing, and fix the descriptions; unpublish the ones I mark as gone." → `list_listings`, `get_listing`, `update_listing`, `unpublish_listing`
- **Upgrade best listings to Featured** (runs: weekly): "Make my three best-performing rentals Featured for 15 days if I have the credits." → `get_credits`, `list_listings`, `get_listing_stats`, `upgrade_listing`

## Can Property Finder automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Property Finder connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to weekly listing performance report, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/property-finder/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/property-finder/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/property-finder/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/property-finder/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Property Finder.

### list_listings

Listings in your agency with status, agent, price, quality score and active upgrade. Access: read. REST: `POST /api/v1/property-finder/list_listings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | live, draft or unpublished. Default: live. |
| `agent_id` | string | no | Only listings assigned to this agent, from list_agents. |
| `purpose` | enum | no | sale or rent. |
| `max_quality_score` | integer | no | Only listings at or under this quality score, 0 to 100. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns listings of your agency, newest first. Quality score is the percentage PF Expert shows for a published listing. Pages hold up to 100 listings; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "listings": [
    {
      "listing_id": "01JA7K3M9Q",
      "title": "Furnished 2BR with marina view",
      "purpose": "rent",
      "status": "live",
      "agent_id": "ag_3d91",
      "price": 145000,
      "quality_score": 88,
      "upgrade": "featured"
    },
    {
      "listing_id": "01JA8B2N4R",
      "title": "Studio near the metro",
      "purpose": "rent",
      "status": "live",
      "agent_id": "ag_77c2",
      "price": 62000,
      "quality_score": 64,
      "upgrade": null
    }
  ],
  "next_cursor": null
}
```

### get_listing

Full listing: title, description, location, specs, price, images, permit number and quality score. Access: read. REST: `POST /api/v1/property-finder/get_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |

Returns everything PF Expert holds for one listing, including the permit number if you entered one. Use it to see why a quality score is low before you change anything. A draft has no quality score yet.

Example response:

```json
{
  "listing_id": "01JA8B2N4R",
  "title": "Studio near the metro",
  "purpose": "rent",
  "status": "live",
  "property_type": "Apartment",
  "location": "Business Bay",
  "price": 62000,
  "bedrooms": 0,
  "size_sqft": 410,
  "description": "Bright studio, close to the metro.",
  "image_urls": [
    "https://example.com/photos/studio-1.jpg"
  ],
  "permit_number": null,
  "agent_id": "ag_77c2",
  "quality_score": 64
}
```

### get_listing_stats

Views and leads for one listing since a date. Access: read. REST: `POST /api/v1/property-finder/get_listing_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `since` | date | no | Count from this date. Default: 30 days ago. |

Returns the performance numbers PF Expert shows for one listing, from the start date to now. Call it once per listing, so keep the set small and filter with list_listings first. A listing that went live after the start date counts from its publish date.

Example response:

```json
{
  "listing_id": "01JA7K3M9Q",
  "since": "2026-09-11",
  "views": 1840,
  "leads": 0
}
```

### list_leads

Leads from your listings, newest first, with contact, listing, agent and time received. Access: read. REST: `POST /api/v1/property-finder/list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `since` | datetime | no | Only leads received after this time. |
| `listing_id` | string | no | Only leads for this listing. |
| `agent_id` | string | no | Only leads for this agent. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns leads that came in through your listings, newest first. Each lead names the listing and the agent it belongs to. Pages hold up to 100 leads; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "leads": [
    {
      "lead_id": "ld_90f1",
      "name": "Jamie Hart",
      "phone": "+971500000000",
      "listing_id": "01JA7K3M9Q",
      "agent_id": "ag_3d91",
      "received_at": "2026-10-10T16:42:00+04:00"
    }
  ],
  "next_cursor": null
}
```

### list_agents

Agents in your agency with their IDs and number of listings. Access: read. REST: `POST /api/v1/property-finder/list_agents`.

No parameters.

Returns the agents of your agency. Use agent_id from here to assign a listing or to filter listings and leads. You see the agents your own role can see in PF Expert.

Example response:

```json
{
  "agents": [
    {
      "agent_id": "ag_3d91",
      "name": "Sara Khan",
      "listings": 24
    },
    {
      "agent_id": "ag_77c2",
      "name": "Omar Haddad",
      "listings": 11
    }
  ]
}
```

### get_credits

The credit balance PF Expert shows for your agency. Access: read. REST: `POST /api/v1/property-finder/get_credits`.

No parameters.

Returns the credits available for upgrades. Check it before upgrade_listing so the agent does not plan a spend you cannot cover. It reads the balance only and spends nothing.

Example response:

```json
{
  "credits": 2500
}
```

### create_listing

New draft listing in PF Expert. Nothing goes live until you publish it. Access: write. REST: `POST /api/v1/property-finder/create_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Listing title. |
| `purpose` | enum | yes | sale or rent. |
| `property_type` | string | yes | As in PF Expert, e.g. Apartment or Villa. |
| `location` | string | yes | Community or building, matched to the Property Finder location list. |
| `price` | integer | yes | Price as you enter it in PF Expert. |
| `bedrooms` | integer | no | Number of bedrooms, 0 for a studio. |
| `bathrooms` | integer | no | Number of bathrooms. |
| `size_sqft` | integer | no | Built-up area in square feet. |
| `description` | string | no | Listing description. |
| `image_urls` | string[] | no | Image URLs, first one is the cover. |
| `permit_number` | string | no | Permit number, where PF Expert asks for one. |
| `agent_id` | string | no | Assigned agent, from list_agents. |

Saves a draft in PF Expert and returns its listing_id. The draft is visible only to you and your agency. It reaches no one and you can delete it in PF Expert, so it does not ask for confirmation. Run publish_listing to put it live.

Example response:

```json
{
  "listing_id": "01JA9C5P7T",
  "status": "draft",
  "agent_id": "ag_3d91"
}
```

### update_listing

Change the price, description, images, permit or agent of a listing. Access: write, asks the user first. REST: `POST /api/v1/property-finder/update_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `fields` | object | yes | Any of the create_listing fields. |

Applies the fields you pass and leaves the rest as they are. Changes to a live listing are visible to buyers and renters, and PF Expert may recalculate the quality score. Returns the updated fields. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "01JA8B2N4R",
  "updated": [
    "description",
    "image_urls"
  ],
  "quality_score": 72
}
```

### publish_listing

Put a draft or unpublished listing live on Property Finder. Access: write, asks the user first. REST: `POST /api/v1/property-finder/publish_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `listing_type` | enum | yes | standard, featured or premium. |
| `duration` | enum | no | 15_days or 1_month for featured and premium. Standard runs 1 month. |

Publishes the listing with the listing type you choose on the Publish screen of PF Expert: standard, featured or premium. Featured and premium run for 15 days or 1 month; the options your market shows may differ. It returns the live status and the portal URL. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "01JA7K3M9Q",
  "status": "live",
  "listing_type": "standard",
  "url": "https://www.propertyfinder.ae/en/plp/rent/apartment-for-rent-dubai-dubai-marina-01JA7K3M9Q.html"
}
```

### unpublish_listing

Take a live listing off the portal. It stays in PF Expert. Access: write, asks the user first. REST: `POST /api/v1/property-finder/unpublish_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |

Removes the listing from Property Finder search and keeps it in PF Expert with status unpublished, so you can publish it again later. Leads already received stay in your leads. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "01JA8B2N4R",
  "status": "unpublished"
}
```

### upgrade_listing

Apply Featured or Premium to a live listing. Uses credits. Access: write, asks the user first. REST: `POST /api/v1/property-finder/upgrade_listing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | string | yes | Listing ID from list_listings. |
| `listing_type` | enum | yes | featured or premium. |
| `duration` | enum | yes | 15_days or 1_month. |

Upgrades a live listing to featured or premium for 15 days or 1 month and pays with credits. It returns the expiry date and the credits left. Spotlight is a bidding product and is not covered by this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": "01JA7K3M9Q",
  "status": "live",
  "listing_type": "featured",
  "expires_at": "2026-10-26T12:00:00+04:00",
  "credits_left": 2380
}
```

## How do I connect Property Finder to Claude Code, Codex or Cursor?

Connecting Property Finder takes three steps: request access, sign in to Property Finder once, then add one MCP server or call the REST API with the same key.

### Connect Property Finder to your agent.

1. **Create an account** Sign up and add Property Finder in the console. Your API key is there too.

2. **Sign in to Property Finder once** Open the connect page from the console and sign in to Property Finder the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Property Finder tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Every Monday, list my live rentals with the most views and no leads since last Monday, grouped by agent, and tell me which upgrades expire this week.
```

### Call Property Finder from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/property-finder/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/property-finder/upgrade_listing \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"listing_id":"01JA7K3M9Q","listing_type":"featured","duration":"15_days"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "listing_id": "01JA7K3M9Q",
  "status": "live",
  "listing_type": "featured",
  "expires_at": "2026-10-26T12:00:00+04:00",
  "credits_left": 2380
}
```

## Why use Cotlet for Property Finder?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Property Finder yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Property Finder changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Property Finder MCP server on GitHub?

Brokers reach PF Expert from code through a partner CRM that PFDN has approved. Hosted scrapers only read public listings. For your own agent or script there is no direct route.

|  | Partner CRM | Cotlet |
|---|---|---|
| Setup | Move to an approved CRM, ask Property Finder to authorize it for your agency, map your listings | Request access, sign in to PF Expert once in your browser |
| Where it runs | Inside the CRM screens | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Write actions | Whatever the CRM vendor built for you | Publish, unpublish, upgrade and edit from a prompt or a script, each confirmed by you by default |
| When the session expires | The CRM keeps its own authorization | If PF Expert logs you out, your agent gets a link to sign in again |
| When Property Finder changes | The CRM vendor adapts | Our team tests it daily and fixes it; failed calls are free |
| Upkeep | You depend on the vendor roadmap | Nothing to host or update |
| Price | CRM subscription, set by the vendor | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Property Finder changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Property Finder API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Property Finder API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Property Finder account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Property Finder yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Property Finder tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Property Finder in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Property Finder's terms:** You use your own Property Finder account and stay responsible for following Property Finder's terms. Cotlet is independent and not affiliated with Property Finder. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Property Finder. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Property Finder once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Property Finder session would leave my computer.**

Cotlet keeps your Property Finder session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need to be a PF Developer Network partner to use Cotlet?**

No. PFDN is a program for software vendors who build integrations for many clients. Cotlet signs in to your own PF Expert account, the way you do, and you can revoke it at any time (checked 11 Oct 2026).

**Can it bid for Spotlight?**

Not in these tools. Property Finder describes Spotlight as a bid for the top three search positions for one week. A listing must be published less than 60 days ago, have a quality score of at least 90%, be Premium and have enough credits (Property Finder Help, checked 11 Oct 2026).

**Can my agent post or send messages in Property Finder without asking me?**

No. Every call to update_listing, publish_listing, unpublish_listing or upgrade_listing waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_listing runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Property Finder API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/property-finder/{tool} from the HTTP Request node.