Pult Docs

Changelog

Every change to the Pult API, newest first.

Every change to the API and the MCP server, newest first. Each change is labelled Breaking, New, Changed or Deprecated. A breaking change is announced here at least 30 days before it takes effect (see Versioning and the beta).

2026-11-17

  • New: confidential apps. An app that registers dynamically with client_secret_basic or client_secret_post gets a client secret, shown once, and authenticates with it at the token and revocation endpoints. Microsoft 365 Copilot connects this way (see Confidential apps and Connect an AI tool). The server metadata lists none, client_secret_basic and client_secret_post.
  • Changed: a public app that sends a client_secret is refused with invalid_client. Before, the secret was ignored.
  • Changed: an authorization request Pult refuses before the person signs in and decides shows Pult's error page. Before, the error went to the app's redirect URI.
  • Changed: an app gets the grant types authorization_code and refresh_token only. A dynamic registration that asks for another is refused with invalid_client_metadata, and a client metadata document that lists others keeps only these two.
  • Changed: a client metadata document must include client_name.
  • Changed: a confidential app that revokes another app's token is refused with invalid_request.
  • New: the protected resource metadata names its resource in resource_name.

2026-11-10

  • New: connect with OAuth. An admin connects an app, such as Claude or ChatGPT, to their Pult account through Pult's authorization server at https://auth.pult.com, and the app reads with that person's rights. The REST API and the MCP server accept these access tokens next to API keys, and each connection has the rate limit of a key (see Connect with OAuth and Rate limits).
  • New: the protected resource metadata of the MCP server, at https://api.pult.com/.well-known/oauth-protected-resource/v1beta/mcp, and of the REST API, at https://api.pult.com/.well-known/oauth-protected-resource.
  • Changed: on the MCP server, a 401's WWW-Authenticate header is Bearer resource_metadata="<the metadata URL>", followed by , error="invalid_token" only when a bearer token was sent and refused. A client that follows resource_metadata, or ignores the header, is unaffected. The REST API's 401 header is unchanged.
  • New: the error codes 401 invalid_token and 403 connection_paused, for OAuth access tokens (see the error catalogue).
  • Changed: a bearer value that doesn't start with pult_ is checked as an OAuth access token, so it gets 401 invalid_token instead of 401 invalid_api_key. This includes a key sent without its prefix or with quotes around it.
  • New: the OpenAPI document lists an OAuth 2.0 security scheme (oauth2, the authorization code flow) next to the API key's, and either one authenticates a request.

2026-11-05

  • New: visits, at GET /visits and GET /visits/{visitId}, with the MCP tools list_visits and get_visit: the visits of a window of at most 31 days, in every status, with the visitor, the visitor type, the host and the form answers. They need Pult Visitors and the new scope visitors:read, which keys created from 2026-11-05 have.
  • Changed: GET /offices and GET /offices/{officeId} also answer organizations that have Pult Visitors but not Pult Workplace. An organization with neither still gets 403 feature_not_enabled with data.feature set to workplace.

2026-11-04

  • Changed: a 429 rate_limited error also carries the seconds to wait in data.retryAfterSeconds (data was null), the same value as the Retry-After header that every HTTP 429 still sends.
  • New: a 403 insufficient_scope error carries a WWW-Authenticate header with the missing scope.
  • Changed: on the MCP server, a tool call refused with organization_disabled, api_not_enabled, api_key_paused, feature_not_enabled or rate_limited gets the error as the tool's result instead of an HTTP error, so the assistant can act on it (see MCP Server).
  • New: the MCP server names the tools it leaves out for a key, and why.
  • Changed: MCP tool results no longer contain characters that hide or reorder text. The REST API returns text exactly as stored.
  • Changed: the OpenAPI document names the answer of each get endpoint (UserResponse, GroupResponse, OfficeResponse, BookingResponse, PresenceLocationResponse), the error item (ProblemIssue) and the response headers, so generated clients get these type names.

2026-10-31

  • New: the Pult API beta, read-only, at https://api.pult.com/v1beta: users, groups, offices, bookings, presence locations, presence days and presence counts per location and day.
  • New: the MCP server at https://api.pult.com/v1beta/mcp, with one tool for each endpoint.

Last updated on

On this page