Issue and activate an Apple Wallet or physical card credential for a user via the Verkada Access Control API
domain: apidocs.verkada.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Ensure Mobile NFC is enabled on the Command organization if issuing a mobile/Apple Wallet Pass type credential rather than a physical card
POST https://api.verkada.com/access/v1/credentials/card scoped to a user_id or external_id, with a body containing type (e.g. 'Apple Wallet Pass', 'HID iClass', 'Standard 26-bit Wiegand', etc.) plus facility_code and card_number or card_number_hex
Leave active as false on creation if you want to stage the credential before enabling it
Call the activate endpoint (PUT to the card's activate route) once the credential should start granting access
Confirm the doors the user needs also have NFC Card Unlock enabled if the credential type is mobile/wallet-based, or Apple Wallet unlock will fail even with an active credential
Known gotchas
Card creation requires either a facility_code and one of card_number/card_number_hex — omitting both fails validation
A credential can exist but be inactive (active=false) — issuing it is not the same call as activating it
Apple Wallet/NFC unlock also depends on org-level Mobile NFC being enabled and the specific door having NFC Card Unlock turned on, independent of the credential itself being active
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?