Developer Portal

Build on RealtorDock without the guesswork.

Use the RealtorDock API to authenticate agents, sync CRM data, manage deals, automate Dock AI workflows, and connect Zapier to the events that matter.

API Reference

Interactive Swagger Docs

Explore endpoints, schemas, and try authenticated requests in-browser.

API Reference

ReDoc Reference

Readable API reference for teams who want a clean documentation view.

API Reference

OpenAPI JSON

Raw OpenAPI schema for SDK generation, Postman imports, and internal tooling.

Authentication

RealtorDock uses bearer tokens for protected endpoints. CallPOST /api/v1/auth/loginorPOST /api/v1/auth/signupto obtain an access token and refresh token.

Authorization: Bearer YOUR_ACCESS_TOKEN

• Access tokens authorize normal API requests.
• Refresh tokens can be exchanged at POST /api/v1/auth/refresh.
• Keep tokens server-side when possible and rotate them if compromised.

Example requests

Start with the five most common integration flows below, then expand in the interactive docs for full schemas.

Log in and get a bearer token

POST /api/v1/auth/login

bash

curl -X POST https://api.realtordock.com/api/v1/auth/login \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "agent@example.com",
    "password": "StrongPassword123!"
  }'

Create a contact

POST /api/v1/contacts/

bash

curl -X POST https://api.realtordock.com/api/v1/contacts/ \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "first_name": "Ava",
    "last_name": "Stone",
    "email": "ava@example.com",
    "phone": "+15125550001",
    "contact_type": "lead",
    "lead_source": "website"
  }'

Create a deal

POST /api/v1/deals/

bash

curl -X POST https://api.realtordock.com/api/v1/deals/ \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "property_address": "123 Main St",
    "property_city": "Austin",
    "property_state": "TX",
    "property_zip": "78701",
    "side": "buyer",
    "price": 450000,
    "stage": "lead"
  }'

Talk to Dock AI

POST /api/v1/dock/chat

bash

curl -X POST https://api.realtordock.com/api/v1/dock/chat \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "text": "Summarize my active pipeline and tell me what needs attention today."
  }'

Subscribe Zapier to RealtorDock events

POST /api/v1/zapier/subscribe

bash

curl -X POST https://api.realtordock.com/api/v1/zapier/subscribe \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "target_url": "https://hooks.zapier.com/hooks/catch/123456/abcdef/",
    "event_types": ["contact.created", "deal.closed"]
  }'

Rate limits

RealtorDock applies per-route limits and returns standard rate-limit headers on successful requests.

Auth endpoints10 requests / minute / IP

AI endpoints30 requests / minute / user

Webhook-style endpoints60 requests / minute / IP

General API routes120 requests / minute / user

Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers.

Zapier triggers

RealtorDock can push real-time events to Zapier so you can route updates into CRMs, spreadsheets, alerts, and task systems.

contact.created
contact.updated
deal.created
deal.stage_changed
deal.closed
document.uploaded
notification.created

Need more?

Start in Swagger for live exploration, jump to ReDoc for a cleaner read-through, or import the OpenAPI schema into your own tooling.

Open Swagger Docs Open ReDoc