Netlify
Keep a Netlify site's environment variables in sync with a MeowPass vault — automatically on change, or pull fresh at build time.
Connect
Create a Netlify personal access token (User settings → Applications → New access token), then connect it. Find your account_id (team) and site_id in Netlify site settings.
Connect (authenticated)
curl -X POST https://api.meowpass.dev/integrations/netlify/connect \
-H "Authorization: Bearer $MEOWPASS_TOKEN" \
-d '{"token":"nfp_...","account_id":"your-team"}'
Auto-sync (on change)
Map a vault environment to a Netlify site once. Every secret change is then pushed to Netlify automatically — create/update on write, delete on remove.
Map a vault env → a Netlify site
curl -X PATCH https://api.meowpass.dev/integrations/<integration-id>/mappings \
-H "Authorization: Bearer $MEOWPASS_TOKEN" \
-d '{"project_mappings":[
{"vault_id":"<vault>","env":"production","account_id":"your-team","site_id":"<site>","context":"all"}
]}'
# After that, writes auto-sync:
mp set STRIPE_KEY sk_live_... --env production # → appears in Netlify
context is the Netlify deploy context: all (default), production, deploy-preview, branch-deploy, or dev.
Build-time pull
Prefer secrets never live in Netlify? Pull them fresh during the build. Add a read-only API key as a Netlify env var and pull in your build command.
netlify.toml build command
# Netlify site env: MEOWPASS_TOKEN = mp_... · MEOWPASS_VAULT_ID = <vault>
[build]
command = "curl -fsSL https://meowpass.dev/install.sh | bash && mp pull --vault $MEOWPASS_VAULT_ID && npm run build"