Changelog

IMPORTANT: Timeline for deprecation of legacy API key authentication

• Effective immediately: Legacy API keys are disabled for organizations that were not already using them. The “API keys” tab in the admin panel is no longer visible. Organization administrators may still contact support@akiles.app to request legacy API keys to be enabled in their organization, to use integrations that haven’t upgraded to OAuth yet.
• On May 20th, 2025: Enabling legacy API keys for more organizations will not be possible. Existing API keys will continue working.
• On November 25th, 2025: Legacy API keys will stop working.

July 2025

• Launched the Developer Center! You can use it to manage your OAuth applications and view API call and webhook delivery logs.
• Added fields client, ip_address, access_method to event.subject.

May 2025

• Added endpoints /cards.
• Added access_methods field to member_group.permissions.
• Added endpoints /members/:id/tokens.

February 2025

• Added endpoints /schedules.

October 2024

• API key authentication is now deprecated. We recommend migrating your integration to OAuth. API keys will stop working in a future date.
• Expanded “Integration examples” section.
• Expanded documentation of endpoint POST /members/:id/pins.

September 2024

Added device to the API. One highlight is this now allows obtaining the online/offline status and battery level of devices via the API.

• Added endpoints /devices
• Added endpoints /products
• Added device_id to /gadgets.
• Added webhook signatures.
• Expanded documentation for events.
• Expanded documentation for webhook filters.

June 2024

• Added /members/:id/cards endpoints.

April 2023

• Added support for creating, editing, deleting member_groups.

October 2021

• Added /members/:id/pins endpoints.

July 2020: Version 2.0

• Members can now have multiple email addresses.
• Members can now have multiple magic links.
• A member can have email addresses and magic links at the same time.
• A member can now be associated to multiple groups, with each association having its own start and end date/times.

Having multiple email addresses is useful for hotel room reserves where you have multiple guests in the same room. Now you can create the reserve as a single member that grants access to all guests.

Per-group start/end times is useful for room reservations: the same member can have multiple reservations for different rooms at different times, and he’ll only be able to enter each room during the allowed time.

API changes

• Removed member fields: type, email, member_group_ids
• Removed endpoints /members/{member_id}/magic_link
• Added endpoints /members/{member_id}/emails
• Added endpoints /members/{member_id}/magic_links
• Added endpoints /members/{member_id}/group_associations

Version 1.0

Initial API release