: GraphQL replacement for REST order authorization transactions?

Hi all,

We currently authorise orders programmatically by creating an authorization transaction using make.com’s Shopify module: Create a Transaction (that uses the now depreciated REST Admin API).

We wanted to recreate this using your new GraphQL but it seems Admin GraphQL does not currently provide a mutation to create authorization transactions, and only supports actions like capture or mark-as-paid, which doesn’t help us.

Could you please confirm:

  1. That using the REST Transaction endpoint for creating authorization transactions is still supported for now
  2. Whether there is any planned GraphQL replacement or roadmap for this functionality
  3. If possible, any guidance on future deprecation timelines for this REST endpoint

Thanks in advance.

Hey @charlie_s - Good questions! To answer them directly:

  1. Yes, the REST Transaction endpoint is still supported. It’s been marked as “legacy” since October 2024, but there’s no announced sunset date for this specific endpoint. You can continue using it.

  2. There’s currently no GraphQL mutation to create authorization transactions. The available mutations are orderCapture (captures an existing authorization) and orderMarkAsPaid (creates a SALE transaction for the outstanding balance). Neither lets you create an authorization from scratch.

  3. No public roadmap or deprecation timeline has been announced for this specific endpoint.

For now, REST is your only option for programmatically creating authorization transactions. The legacy status means it’s in maintenance mode (no new features), but it’s not going away imminently. Keep an eye on the developer changelog for any updates on deprecation timelines.

Out of curiosity, what’s the workflow you’re using these authorization transactions for? Depending on your use case, there might be alternative approaches worth considering.