Pennylane v1 deprecation – impact on “Make an API call” modules using Pennylane connection?

Questions
1

:bullseye: What is your goal?

Hi,

I have a question regarding the announced deprecation of Pennylane v1 modules before January 31, 2026.

In several scenarios, I’m using “Make an API call” modules inside the official Pennylane connector (not the new Pennylane v2 API call module).

Concretely:
• The API calls target Pennylane v2 endpoints (e.g. /v2/…)
• Authentication is handled via the Pennylane connector
• The module itself is not marked as deprecated in Make

The deprecation notice mentions replacing all Pennylane v1 modules, so I’m unsure whether:
• “Make an API call” modules relying on the Pennylane v1 connector will stop working after the deadline
• Or if only the higher-level Pennylane v1 business modules are concerned

Do you know if these API call modules will fail after the deprecation date?

And if migration is required:

  • Do you have any best practice to migrate quickly from Pennylane v1 → v2 for “Make an API call” modules?
  • Replacing the module would break all downstream mappings because the output structure (module number / bundle references) changes, even though the API response itself stays identical. Any tips to handle this efficiently would be very helpful.

Thanks in advance!

:thinking: What is the problem & what have you tried?

:clipboard: Error messages or input/output bundles

Input / configuration
• Module: Pennylane – Make an API call (v1 connector)
• Endpoint called: /v2/suppliers
• Method: GET
• Authentication: via official Pennylane connector (no manual API key)

:link: Create public scenario page

3

If this is exactly what you are inserting into the URL field of the “Make an API call” module, then you should not be affected by the v1 depcrecation, as you are directly calling the v2 endpoint.

Hope this helps! If you are still having trouble, please provide more details.

— @samliew

4 Likes