I received the attached notice from ShipStation this morning. The notice informs me that with the next billing cycle, I’ll need to upgrade to a plan that includes access to ShipStation’s Companion API endpoints.
I have a zap that only connects to ShipStation and as far as I’m aware does not utilize ShipStation’s Companion API. Is this change managed by Zapier and will there be any changes needed on my end?
Looking forward to your response!
Best answer by JimF
Hi @SamB ,
Glad to share some details here for the community.
I reached out to Adil but never heard back. I had also reached out to ShipStation support and they recommended that I upgrade to a ShipStation plan that included API access. The most basic of which is the ShipStation Scale plan. I have since upgraded to the Scale plan and have not received a notice since.
This is the solution that resolved the issue for me, but upgrading my ShipStation plan shouldn’t be the fix for all issues. I would like to know going forward if this could’ve been managed by Zapier entirely.
Thanks!
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
Hey, from what you've described, it sounds like your current Zap doesn’t use ShipStation’s Companion API endpoints. Zapier typically handles the API integrations on the backend, so unless your Zap explicitly relies on those specific endpoints, you likely won’t need to make any changes.
That said, if any adjustments are needed, we can review and update the Zap accordingly to ensure it stays functional without requiring the upgraded plan.
Let me know if you'd like us to take a quick look to confirm.
Glad to share some details here for the community.
I reached out to Adil but never heard back. I had also reached out to ShipStation support and they recommended that I upgrade to a ShipStation plan that included API access. The most basic of which is the ShipStation Scale plan. I have since upgraded to the Scale plan and have not received a notice since.
This is the solution that resolved the issue for me, but upgrading my ShipStation plan shouldn’t be the fix for all issues. I would like to know going forward if this could’ve been managed by Zapier entirely.
Upgrading to the ShipStation Scale plan resolved the issue by providing necessary API access, though concerns about requiring an upgrade are understandable. Some integrations, like ShipStation, have API limitations based on subscription levels, restricting Zapier's capabilities. Sometimes, alternative solutions using different triggers or actions may work, but this depends on the app's API permissions. Since Zapier functions as an intermediary, it's constrained by the integration limits of connected services. Feedback like this helps improve future integration options.
Feel free to ask if you need further assistance or have more questions. We're here to help.
Thanks for getting back to me, @JimF. Really appreciate you following up here to share that upgrading your ShipStation account sorted it. 🤗
As Jammer mentioned, we don’t have control over the API access limits that apps like ShipStation may put in place for certain plans, so we’d be unable to force API access regardless of a person’s plan type. Looking at their API documentation here it seems that they’re now only allowing access to their API if you’re on a Scale-Gold, Accelerate or higher plan:
I noticed we don’t have any documentation on our side that states these requirements so I’ve put in an internal request to get this information added to our Help Center to make things clearer going forward.
Thanks again for sharing what the solution was and for bringing this to our attention. Do let us know if there’s anything else we can help with. In the meantime, happy Zapping! ⚡