# SwiftConnect

> SwiftConnect operates a "connected access network" that unifies digital identity, physical access
> credentials and building infrastructure, so an employee badge can live in Apple, Google or Samsung
> Wallet and open the doors an employer has authorized. Founded 2020, headquartered in Stamford,
> Connecticut. It sits between access-control systems (LenelS2, Software House C-CURE 9000, Genetec),
> credential providers (HID, LEGIC, Wavelynx), identity providers and workplace platforms, and
> automates credential issuance, permission change and revocation across all of them.

Generated by API Evangelist (https://apievangelist.com) from SwiftConnect's public surface on
2026-08-29. This is a third-party profile, not a SwiftConnect document.

## What an agent needs to know first

- The API is real and live at `https://api.swiftconnect.io`. It is NOT on the corporate domain:
  the website moved from swiftconnect.io to www.swiftconnect.com, but the API host did not move.
- Authentication is a bearer JWT: `Authorization: Bearer <token>`. An unauthenticated call returns
  HTTP 401 `{"code":401,"message":"Invalid JWT","client_error_code":""}`.
- Version is negotiated by media type, not path: `Accept: application/vnd.swiftconnect.v2+json`.
- There is NO public machine-readable contract. No OpenAPI, no GraphQL SDL, no AsyncAPI, no MCP
  server, no A2A agent card. The API reference is on a password-protected ReadMe hub.
- Do not confuse this company with: `SwiftConnect` on CocoaPods (different owner), `utmapp/SwiftConnect`
  on GitHub (a networking library), SWIFT the financial messaging network, or Swift the language.

## API

- [SwiftConnect Developer API](https://swiftconnect.readme.io/): credentials, permissions and
  provisioning across the connected access network. Base URL `https://api.swiftconnect.io`.
  Reference is password-protected.

## Resource routes observed live (unauthenticated probe, 2026-08-29)

These paths returned 401 with the JSON error envelope, meaning the route is registered and requires
authentication. Paths not listed returned a plain-text 404 (no such route). This is probed
evidence of the resource surface, not a specification.

- /credentials
- /persons
- /meetings
- /organizations
- /buildings
- /readers
- /devices

## Artifacts (API Evangelist)

- [Authentication](authentication/swiftconnect-authentication.yml)
- [Conventions](conventions/swiftconnect-conventions.yml)
- [Error catalog](errors/swiftconnect-problem-types.yml)
- [Rate limits](rate-limits/swiftconnect-rate-limits.yml)
- [Lifecycle](lifecycle/swiftconnect-lifecycle.yml)
- [Conformance](conformance/swiftconnect-conformance.yml)
- [Packages](packages/swiftconnect-packages.yml)
- [Plans and pricing](plans/swiftconnect-plans-pricing.yml)
- [Well-known probe](well-known/swiftconnect-well-known.yml)
- [MCP](mcp/swiftconnect-mcp.yml)

## Company

- [Website](https://www.swiftconnect.com/)
- [Blog](https://swiftconnect.com/blog/)
- [Newsroom](https://www.swiftconnect.com/newsroom/)
- [Partners](https://www.swiftconnect.com/partners/)
- [Contact](https://www.swiftconnect.com/contact-us/)
- [Status page](https://swiftconnect.statuspage.io/)
- [Sign in](https://accounts-v2.swiftconnect.io/)
- [Terms and conditions](https://www.swiftconnect.com/terms-conditions/)
- [Privacy policy](https://www.swiftconnect.com/privacy-policy/)

## Not available

- No pricing page — enterprise, contact sales.
- No public SDK on any package registry; the mobile provisioning SDK is customer-only.
- No GitHub organization.
- No webhooks or event surface documented publicly; `/webhooks` and `/events` are not routes.