Skip to content

Conversation

@gogl92
Copy link

@gogl92 gogl92 commented Sep 30, 2025

1️⃣ This feature was directly requested to add support for PrintNode Integrator accounts and child account management.

2️⃣ No, all changes are focused on adding Integrator/child account support.

3️⃣ Yes, new tests have been added for AccountService and RequestOptions to cover the new functionality.

4️⃣ This PR introduces comprehensive support for PrintNode Integrator accounts, enabling the management and impersonation of child accounts. This is crucial for applications that need to provision and control printing for multiple end-users or customers through a single Integrator account.

Key improvements include:

  • Child Account Impersonation: Added child_account_by_id, child_account_by_email, and child_account_by_creator_ref options to RequestOptions, which translate to X-Child-Account-* headers. This allows any API request to be made on behalf of a specific child account.
  • Account Management Service: A new AccountService has been implemented, providing methods for create, update, setState (e.g., suspend/activate), and delete child accounts.
  • API Requestor Enhancements: The PrintNodeApiRequestor now supports PUT and PATCH HTTP methods, handles raw string bodies (specifically for setState), and correctly processes 204 No Content responses.
  • Documentation: Updated docs/printnode/api.md with detailed usage examples for both impersonation and account management.

This functionality is essential for developers building platforms that integrate deeply with PrintNode and manage multiple client accounts.

5️⃣ Thanks for contributing! 🙌


Open in Cursor Open in Web

@cursor
Copy link

cursor bot commented Sep 30, 2025

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants