PULT API & MCP (Beta): Connect PULT to AI tools and your own systems
Last updated: November 20, 2026
With the PULT API (beta), you can read your organization’s PULT data in your own tools – for example in a BI dashboard, your HR system or your own reports. With the PULT MCP server, AI assistants like Claude can access the same data directly, so you can simply ask questions such as “How many people were in the office last week?”. This article shows admins which data is available and how to connect – either by signing in with your PULT account (OAuth) or with an API key.
📌 Before you start: You need admin rights in PULT. The API is switched on per organization by PULT – if you don’t see API keys under Settings → Security, contact us at support@pult.com and we’ll activate it for you.
📘 Technical documentation: All endpoints, parameters, authentication details and rate limits for developers: docs.pult.dev
What you can do with the API and MCP
The API is read-only: you can read data, but not create or change anything in PULT. These data are available:
Data | What you get | Requires |
|---|---|---|
Users | List and single users, filter by status (active, archived), group or email | any PULT product |
Groups | List and single groups | any PULT product |
Offices | List and single offices, filter by status | Workplace |
Bookings | Bookings for a period of up to 31 days, filter by type, office, group or up to 50 users | Workplace |
Presence locations | List and single locations | Presence |
Presence days | Per person, day and location: how the person was detected (WiFi or desktop agent) plus first and last seen time – for up to 31 days | Presence |
Presence location counts | Number of people per location and day – for up to 31 days | Presence |
Visits | List and single visits | Visitor Management |
The API follows the same privacy rules as your PULT dashboard:
Every API key and connection only ever sees the data of its own organization.
Keys and connections read with the rights of their owner – they see what an admin sees in the dashboard reports.
Guests are not included.
Bookings and presence data only include people with an active seat.
Past bookings and presence data of archived users stay available – they appear in the user list with the status archived.
If your organization hides sensitive presence data, first and last seen times are left out.
Presence data follows your organization’s retention period.
1. Connect an AI tool with your PULT account (OAuth)
This is the easiest way: you don’t need an API key – you sign in with your PULT account and approve the connection.
In your AI tool, add PULT as a custom connector. In Claude, for example, go to Settings → Connectors and add a custom connector.
Name: PULT, Server URL:
https://api.pult.com/v1beta/mcpIf your tool asks how to authenticate, choose OAuth. If it offers to send the resource parameter, leave that on.
Click Connect. PULT opens in your browser – sign in and approve the connection.
After connecting, your AI tool sees all PULT data from the table above as read-only tools. Try questions like:
“Which offices do we have in PULT?”
“Who has booked a desk in our Hamburg office next Monday?”
“How many people were in the office per day last week?”
“Who was in the office fewer than three days per week this month?”
📌 Shared AI workspaces (e.g. Claude Team or Enterprise, ChatGPT workspaces): A workspace owner adds the PULT connector once for the whole workspace. Each person then connects it with their own PULT account. Every connection reads with the rights of the person who connected – nobody has to share an API key.
📌 Which AI tools work? OAuth is tested with Claude and ChatGPT and should also work with Claude Code, Cursor, VS Code and Langdock. Microsoft 365 Copilot also connects via OAuth. Gemini Enterprise isn’t supported yet. Tools without OAuth support (e.g. Copilot Studio, n8n or Le Chat) connect with an API key – see steps 2 to 4. You find the list per tool in the MCP documentation.
2. Open the API keys page
In the PULT dashboard, go to Settings → Security → API keys. If the Connect box is collapsed, click Show.

Create API key: Creates a new key (see step 3).
REST API: The base URL for your own integrations:
https://api.pult.com/v1betaOpenAPI document: The technical description of all endpoints. It is public, no key needed – your developers can use it to generate client code.
MCP server: The address for AI tools:
https://api.pult.com/v1beta/mcpAuthentication: How the key is sent – for REST and MCP in the header
Authorization: Bearer <your API key>. Keys are never accepted in a URL.
3. Create an API key
Click Create API key.

Name: Give the key a name that shows where you use it, e.g. “Claude” or “Power BI”.
Expires after: Choose 30 days, 90 days, 1 year or a custom date. Shorter lifetimes limit the damage if a key leaks.
Click Create key.
Your new key is shown:

Copy copies the key only, Copy as header copies it ready to use as
Authorization: Bearer ….Click Done.
⚠ Copy the key right away. You won’t be able to see it again. Treat it like a password: anyone who has it can read your organization’s data with your admin rights – also in shared AI workspaces and workflow tools.
4. Connect an AI tool with an API key
Use this if your AI tool doesn’t support OAuth or for automations. Add PULT as a custom connector or MCP server:
Server URL:
https://api.pult.com/v1beta/mcp(Streamable HTTP)Authentication: Send your API key in the
Authorizationheader asBearer <your API key>. The easiest way is Copy as header from step 3. Some tools addBearerthemselves – then paste only the key.
⚠ Create a separate key for each tool, so you can revoke one without affecting the others. In a shared AI workspace, everyone uses the same key with your admin rights – use OAuth there instead (step 1).
5. Use the REST API
For your own integrations, send requests to the base URL with your key in the Authorization header, for example:
curl -H "Authorization: Bearer YOUR_API_KEY" https://api.pult.com/v1beta/officesDocumentation: All endpoints and parameters are described at docs.pult.dev/api and in the OpenAPI document (number 3 in step 2).
Paging: Lists are returned page by page with a cursor, 1 to 500 entries per page (default 100).
Rate limit: During the beta, up to 600 requests per minute per key or connection and 1,200 per organization (REST and MCP together). If you exceed it, you get the status
429and aRetry-Afterheader.Errors: Every response has a
Request-Id. Please include it when you contact support about an error.
6. Manage keys and connections
All keys of your organization are listed below the Connect box.

Status: Shows whether the key is active or revoked.
Last used: Shows when the key was last used – this helps you find keys nobody needs anymore.
Revoke: Deactivates the key.

Confirm with Revoke key. Every tool using this key loses access immediately. This can’t be undone.
A key also stops working automatically when it expires, when the API is switched off for your organization, or when its owner is archived or no longer an admin.
OAuth connections: You see and revoke your own connections in the PULT web app under Settings → Connections. Admins see all connections of the organization in the dashboard under Settings → Security → Connections. A connection ends automatically after 90 days without use or when its owner is archived, and it is paused while its owner isn’t an admin.
Frequently asked questions
Can I create or change bookings via the API?
Not yet. The beta is read-only – you can’t create or change bookings, users or other data. Actions like booking or releasing a desk are planned for a later version.
Who can connect, and which data do they see?
Only admins can create API keys and connect AI tools. Keys and connections read with the rights of their owner, subject to your organization’s privacy settings. With OAuth, every admin uses their own connection – so you don’t need to share a key. Limiting access to certain data isn’t possible yet.
I lost my API key. Can I see it again?
No, a key is only shown once. Create a new key and revoke the old one.
Our integration stopped working. What happened?
Check the status and expiry date of the key on the API keys page. Keys also stop working when the owner is archived or no longer an admin – in that case, another admin creates a new key. For OAuth connections, reconnect in your AI tool.
Can I connect ChatGPT?
Yes. ChatGPT connects via OAuth: add PULT as a custom connector with the server URL and sign in with your PULT account (step 1). Whether you can add custom connectors depends on your ChatGPT plan.
Will the API change?
Possibly. The beta version v1beta may still change before the stable version is released. We’re adding new data and features regularly – let us know at support@pult.com what you’re missing.
Related articles
If you have any questions, feel free to contact our support team at support@pult.com.