Skip to content

API - Changelog ​

September 17th 2026 ​

  • New ✨
    • REST: Export floor as PDF (POST /floor/{floorId}/pdf) now accepts spaceLabelMapping. Space labels follow the organisation's space usage mapping by default; pass an object to replace it, or {} to render plain usage labels.

September 9th 2026 ​

  • New ✨
    • REST: Export floor as SVG (POST /floor/{floorId}/svg) renders the floor's default layout, and Export layout as SVG (POST /layout/{layoutId}/svg) renders any layout of a floor. Both use the layout's latest published revision, accept theme, visibility, units, shapeLayers and spaceLabelMapping, and return a download URL valid for 30 minutes. Space labels follow the organisation's space usage mapping unless spaceLabelMapping is given ({} renders plain usage labels).
    • REST: Export floor as PDF (POST /floor/{floorId}/pdf) is exposed.

June 25th 2026 ​

  • New ✨
    • GraphQL: Products now expose a type field (for example product:static).
    • GraphQL: Products can be filtered by type through the Product filter, applied at every nesting level.

June 18th 2026 ​

  • New ✨
    • GraphQL: getFloors now accepts an archived argument (default: false).
    • GraphQL: getFloorById and getLayoutById now resolve archived floors with base properties.
    • GraphQL: The isArchived field is now available on the Floor object.
    • GraphQL: For archived floors, SpaceGraph-derived fields (spaces, elements, adjacentSpaces, customAttributes) return empty arrays and count/metric fields (spaceCount, elementCount, seatCapacity, elementSurfaceArea) return null. See Archived floors for details.

June 8th 2026 ​

  • New ✨

    • Webhooks now support the layout resource with the updated and published actions
  • Changes

    • GraphQL: query batching has been disabled. Each request must contain a single operation; batched arrays of queries are no longer accepted.

April 29th 2026 ​

  • New ✨
    • Added webhook scopes: webhook:read, webhook:create, webhook:query, webhook:update, webhook:delete
    • The above scopes were added to the existing secret access tokens to maintain previous behaviour.

April 28th 2026 ​

February 10th 2026 ​

  • Changes

Feburary 5th 2026 ​

  • New ✨

  • Changes

    • Floor GeoJSON export now applies floor transform
    • Floor GET, POST, PATCH now expose level property
    • GraphQL Floor resource and filters exposes level property

January 21st 2026 ​

  • New ✨
    • Added MCP Server documentation for accessing Archilogic resources through the Model Context Protocol, supporting AI assistants and agents

January 20th 2026 ​

September 17th 2025 ​

  • Fixes
    • Proper webhook trigger if layout is updated through operations
    • Fix asset query performance regression

September 9th 2025 ​

September 1st 2025 ​

July 22nd 2025 ​

  • Changes

    • Increase limit for custom attributes to 25 per resource
    • Support buildings in IMDF export
  • Fixes

    • Use floor id instead of layout id in IMDF levels and GeoJSON
    • Always send all registered webhooks

July 15th 2025 ​

  • Fixes
    • Properly export IMDF desk fixtures

July 8th 2025 ​

June 20th 2025 ​

  • New ✨

April 4th 2025 ​

  • Changes
    • Access tokens use Bearer token type, deprecating custom AL-Secret-Token and AL-Temp-Token

March 4th 2025 ​

  • New ✨

  • Fixes

    • Custom attribute values of type boolean and number are no longer stringified in GeoJSON export
  • Changes

    • The DXF export now exports standard AIA Layers

January 30th 2025 ​

  • New ✨

  • Fixes

    • Properly chain concurrent updates via the operations endpoint.
    • Better handling of large updates with large amount of operations.
  • Changes

    • The layout operations endpoint is out of beta.
  • Deprecation

    • The custom attribute value endpoints are deprecated, use the layout operations endpoint instead.

January 16th 2025 ​

December 11th 2024 ​

November 8th 2024 ​

October 3rd 2024 ​

May 23rd 2024 ​

April 22nd 2024 ​

April 2nd 2024 ​

  • New ✨
    • OpenAPI powered REST endpoint documentation. Example

February 15th 2024 ​

  • New ✨
    • Coordinates: Address enhanced with bearing
    • Floor's source

November 14th 2023 ​

  • New ✨
    • Webhooks support

September 21st 2023 ​

  • New ✨
    • customAttributes:read and customAttributeValues:readPublic scopes can now be added to publishable tokens

August 25th 2023 ​

  • New ✨

    • GeoJSON export for floors has now a new parameter includeAllElements. When set, the response includes the geometry of all elements on the floor to create a detailed floor plan drawing with style information included.
    • teamId is returned for floor responses if the User Teams feature is enabled for an organization
  • Deprecation

    • Custom fields scopes have been removed, API endpoints are deprecated. Please use custom attributes instead

April 21st 2023 ​

  • New ✨
    • Custom Attributes for Product resources

February 15th 2023 ​

  • New ✨
    • Custom Attributes for Floor, Space, Asset resources

July 26th 2022 ​

  • New ✨
    • new property labels in Floor object
    • Floors can be queried by label param

June 15th 2022 ​

  • New ✨
    • DXF file of floors now available through downloadable URL
    • new property seatCapacity in Asset object

November 22th 2021 ​

  • New ✨
    • new properties createdAt and floorNumber in Floor object

October 28th 2021 ​

  • New ✨
    • Archived floors can be queried with includeArchived param

October 6th 2021 ​

  • Deprecation
    • Space API v1 is no longer available.

August 25th 2021 ​

  • New ✨
    • new properties customId and name in Space object

July 7th 2021 ​

  • Fixes
    • svg exports for some floor plans in portrait mode had incorrect lat long bounding boxes

March 25th 2021 ​

Space API v2 release ​

  • New ✨

  • BREAKING Changes

    • New methods of providing publishable access tokens or secret access tokens in requests.
      It is not possible to create v1 tokens anymore.
    • By default, resource reads return only type, resourceType, id, properties, resourceRelations. Use /v2/<resource-type>/<resource-id/geo-json to return the above properties plus geometry and geometryOpenings (latter only for space resources).
    • By default querying resources will not return the geometry and geometryOpenings attributes. To include these in the response the additional geometry=true query parameter must be provided. Check query params for floors, spaces or assets
    • In contrast to Space API v1, resource reads and queries don't return the custom fields associated with the resources by default anymore. To include custom fields, the includeCustomFields=true query parameter must be supplied.
    • In Space API v1, resource queries returned both private and public resources if the floor:read scope was present. Since the floor:read scope has been deprecated, resource queries in Space API v2 only return both private and public resources if both floor:queryPublic and floor:queryPrivate scopes are provided. If just one of the scopes is provided, then Space API v2 only returns resources that fall into that category.
    • In contrast to Space API v1, in v2, access tokens only allow reading the same organization's public resources.