RoomPlanning for developers
Last updated: 11 November 2026
Build floor plans into your own products: property listings, furniture shops, moving planners, customer portals or AI agents. The RoomPlanning Platform creates plans, places rooms, doors, windows and furniture in real sizes, exports them and embeds them on your website. Every plan lives in your RoomPlanning account and can be edited further in the editor.
The Platform is open to everyone with a RoomPlanning account, for your own projects as well as for businesses. The Platform terms apply.
Pricing
You pay with credits: no subscription, no base fee. Every account gets 50 credits per month free. Purchased credits never expire. Prices are final prices including VAT; the seller is Dodo Payments.
| Pack | Credits | Price (incl. VAT) | per credit |
|---|---|---|---|
| Starter | 500 | €19 | 3.8 ct |
| Growth | 2,500 | €79 | 3.2 ct |
| Scale | 10,000 | €249 | 2.5 ct |
| Call | Credits |
|---|---|
| Reading (plans, describing a plan, balance) | 0 |
| Create a plan, rooms, openings, furnishing, storeys, stairs, terrain, excavations, ramps, floor build-ups | 1 |
| Export SVG or PNG | 1 |
| Export DXF | 2 |
| Export GLB (3D model) | 5 |
| Place devices (network, smart home, electrical) | 1 |
| Propose the network | 2 |
| Check the installation; with Wi-Fi coverage (Premium) | 0; 1 |
| Bill of materials, bill of materials as CSV (Premium), network plan as PDF | 1 |
| Embed with "Made with RoomPlanning" | 0 (up to 50,000 views/month) |
| Embed without the note | 1 per 100 views |
A failed call costs nothing. Without credits the API answers 402 credits_exhausted.
Quick start
- Sign in and open the developer console.
- Create an API key. It is shown only once.
- Create a plan and give it rooms:
curl -X POST https://roomplanning.app/platform/v1/plans \
-H "Authorization: Bearer rp_live_…" -H "Content-Type: application/json" \
-d '{"title": "Flat 1 Example Street"}'
curl -X POST https://roomplanning.app/platform/v1/plans/PLAN_ID/rooms \
-H "Authorization: Bearer rp_live_…" -H "Content-Type: application/json" \
-d '{"rooms": [
{"name": "Hall", "width_m": 1.5, "depth_m": 6},
{"name": "Living room", "width_m": 5, "depth_m": 4, "next_to": {"room": "Hall", "side": "east"}}
]}'
curl -o floorplan.png "https://roomplanning.app/platform/v1/plans/PLAN_ID/export.png?width=1600" \
-H "Authorization: Bearer rp_live_…"
Every paid answer reports in X-Credits-Charged, X-Free-Credits-Remaining and X-Credits-Remaining what it cost and what is left.
API reference
Base: https://roomplanning.app/platform/v1. Authentication: Authorization: Bearer <API key>. JSON answers, sizes in metres. Up to 60 calls per minute and key.
| Method and path | What |
|---|---|
GET /me | Account, free allowance and balance |
GET /plans?q= | The account's plans |
POST /plans | Create a plan: {title, units?} |
GET /plans/{id} | Describe a plan: levels, rooms with area and inner sizes |
POST /plans/{id}/rooms | Rooms: {rooms: [{name, width_m, depth_m, next_to?, at?}], level?} |
POST /plans/{id}/openings | Doors, windows: {openings: [{room, side, kind, width_m?, offset_m?, style?, light_well?}], level?} |
POST /plans/{id}/furnish | Furnish a room: {room, room_type?, density?} |
POST /plans/{id}/levels | A storey on top or a basement below: {position: "above"|"below", name?, height_m?, slab_m?, copy_exterior_walls?} |
POST /plans/{id}/stairs | Stair: {from?, to?, position: {x_m, y_m}, direction_deg?, kind?, width_m?}; to: "terrain" for an outside stair |
POST /plans/{id}/terrain | Terrain: {ground_level_m?, spot_heights?: [{x_m, y_m, height_m}], clear_spot_heights?} |
POST /plans/{id}/excavations | Excavation in front of a basement: {outline: [{x_m, y_m}], level?, floor_m?, edge?, railing?} |
POST /plans/{id}/ramps | Ramp down to a garage: {points: [{x_m, y_m}], level?, from?, width_m?, top_m?, bottom_m?, transitions_m?, sides?} |
POST /plans/{id}/floors | Floor build-up of a storey or a room: {level?, room?, preset?, layers?: [{kind, material?, thickness_mm, existing?, removed?, heating_pipe_mm?}], none?, name?, keep?: "heights"/"structure"}; answers with finished and raw floor and clear heights |
GET /plans/{id}/export.{svg,png,dxf,glb} | Export; ?level= (name or number), ?width= (PNG, up to 4096) |
POST /plans/{id}/network | Propose the network: {equipment_level?, levels?, access_points?, sat?, fiber?, smoke_detectors?, region?} |
POST /plans/{id}/devices | Devices by room and wall or ceiling: {devices: [{slug, room, side?, offset_m?, on?, label?, protocol?, supply?, watts?}], level?} |
GET /plans/{id}/installation-check | Equipment per room, smoke detectors, smart-home hints, cameras; ?level=, ?region=DE-BE, ?wifi=true (Wi-Fi coverage per room, Premium) |
GET /plans/{id}/bill-of-materials | Bill of materials as tables (Premium); ?patch_list=true |
GET /plans/{id}/export.{network-pdf,bom-csv} | Network plan of a storey as PDF (?level=), bill of materials as CSV (Premium) |
POST /plans/{id}/embeds | Create an embed: {branding?, domains?} |
GET /embeds, DELETE /embeds/{id} | List and remove embeds |
level is a storey's name (Ground floor, Basement, Kellergeschoss), a short form (EG, OG, KG, UG) or a number (1 = lowest); without level the ground floor. Garage doors are doors with style sectional, roller, up-and-over or garage-side; light_well: {} puts a light well in front of a basement window.
next_to places a room next to another: {"room": "Hall", "side": "east", "align": "start"}. side is north, east, south or west; align lines it up at the start, centre or end of that side. Shared walls are drawn once.
Network and smart home: network places double sockets per room after the equipment value (1 to 3), the media distributor, access points (none, count or coverage) and one Cat 7 cable per socket in a star, optionally SAT, fibre and the smoke detectors of the German state. Lists and calculations (bill of materials, Wi-Fi coverage) come with Premium as in the editor; otherwise the API answers 403 pro_reports_required. Guideline values; the installation is a job for a qualified electrician.
Errors come as {"error": "…", "message": "…"}, for example 400 invalid_request, 401 unauthorized, 402 credits_exhausted, 404 not_found, 429 rate_limited (with Retry-After).
Embedding
An embed shows a plan on your website and stays up to date automatically:
<iframe
src="https://roomplanning.app/embed/EMBED_ID"
width="800"
height="600"
loading="lazy"
style="border:0;max-width:100%"
title="Floor plan"
></iframe>
As an image: https://roomplanning.app/embed/EMBED_ID.png or .svg. For content management systems there is oEmbed at https://roomplanning.app/oembed?url=…. With domains you decide which websites may show the embed.
With AI assistants
You reach the same plans from Claude, ChatGPT and other assistants through the MCP server https://roomplanning.app/mcp: create and furnish plans, show them as a picture, export and embed them, plan network and smart home and fetch the bill of materials, in the chat.
Notes
API keys belong on your server, not in code that runs in a browser. You can revoke a key in the console at any time; it stops working within a minute.