v0.1.7

Available on npm:

• notifkit@0.1.7 (npm i notifkit@0.1.7)
• @notifkit/mcp@0.1.3

What changed

• client.addUser(id, contacts, options): addUser now accepts the user ID first, followed by a contacts array and profile options. The previous object signature (addUser({ id, ... })) still works.
• Added client.identify() as an alias for addUser().
• Added support for a contacts array across AddUserSchema, UpdateUserSchema, and inline notification targets. You can now pass contacts for any supported channel (email, sms, push, webhook, in-app, telegram, discord, whatsapp, slack) along with label, isPrimary, and per-contact preferences.
• Added client.addContacts(userId, contacts) for adding multiple contacts in one call.
• The POST /v1/users/:id/contacts endpoint now accepts either a single contact object or an array of contacts.
• Fixed unencoded URL parameters in client.ts (deleteContact, getUserContacts, etc.) so targets containing + (like email aliases) or / (like webhook URLs) no longer break route matching.
• Replaced loose any return types across NotifkitClient methods with typed response interfaces (UserResponse, UserContactResponse, UserDetailResponse, WorkflowDefinitionRecord, and others).
• Updated the MCP server's upsert_user and update_user tools to accept the contacts array.