authenticate to boulevard's admin graphql api using a developer portal application (businessId + application api key + application secret)
domain: developers.joinblvd.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
log into developers.joinblvd.com (same credentials as your Boulevard dashboard; this flow is gated to Enterprise/Premier accounts) and create a new application in the Developer Portal to get an Application ID and Application API key
install that application onto the specific business you want to query, via the business's Manage Business settings → Apps & Integrations → Custom Apps → Install, entering the Application ID — installation binds the app to that business and reveals the Application secret, which is shown once, right after installation completes
record the three values every admin api request needs: BUSINESS_ID (the business you installed into), the Application API key, and the Application secret
send admin graphql requests to boulevard's admin api using businessId + Application API key + Application secret, following the exact credential/header format shown on developers.joinblvd.com/2020-01/admin-api/authentication for your account (Boulevard doesn't publish this as a static, copy-pasteable spec outside the logged-in portal)
confirm a successful response on a simple query before building further graphql calls
if the Application secret is ever exposed, reinstall or reissue the application on that business to rotate it — Boulevard does not offer a separate secret-rotation action independent of (re)installation
Known gotchas
this app-install model (businessId + Application API key + Application secret) is boulevard's current admin api auth scheme — some older integration guides and cached docs instead describe a legacy scheme: an HMAC-SHA256-signed token prefixed "blvd-admin-v1", base64-wrapped into a single Authorization: Basic header. If you see that pattern, treat it as legacy/deprecated, not current
the Application secret is only ever displayed once, immediately after installation — store it right away, since there's no "reveal secret" option later; losing it means reinstalling
creating an application in the Developer Portal and installing it on a business are two separate steps — you don't have working credentials until you've done both, and installation is what's gated to Enterprise/Premier admin users
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?