How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Allegion Mobile Credentials API

Upload, delete, and list BLE Mobile Credentials for end users

Allegion Mobile Credentials API is one of 5 APIs that Allegion publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Mobile Credentials. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, best-practice docs, an engineering blog, authentication docs, and 6 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.allegion.com/engage.

4 operations 2 paths 3 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.allegion.com/schlage-home
Authentication
API Key, HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 2

Allegion Mobile Credentials API declares 2 security schemes for authenticating requests. An API key is passed in the header as alle-subscription-key (SubscriptionKey). It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

  • SubscriptionKey — Azure API Management subscription key issued via the Allegion Developer Portal.
  • BasicAuth — Basic Auth token generated from ENGAGE credentials.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Mobile Credentials 4

Upload, delete, and list BLE Mobile Credentials for end users

GET
/credentials
List Active Mobile Credentials
listCredentials 2 params → 200401
POST
/credentials
Upload Mobile Credential
uploadCredential body → 201400401
GET
/credentials/{credentialId}
Get Mobile Credential
getCredential 1 param → 200404
DELETE
/credentials/{credentialId}
Delete Mobile Credential
deleteCredential 1 param → 204404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are MobileCredential (10 properties), MobileCredentialCreate (6 properties), Error (2 properties). Each schema is shown below with its type and property counts.

MobileCredential
object
10 properties
MobileCredentialCreate
object
6 properties 2 required
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

allegion-mobile-credentials-api-openapi.yml Raw ↑

Other APIs Allegion publishes across the network.

Allegion Access Codes API
Allegion Commands API
Allegion Devices API
Allegion Webhook Subscriptions API
Where this information came from

This is an independent, third-party profile of Allegion Mobile Credentials API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.