X-HTTP-Method-Override

Posts about the simPRO API. Help/support/how-to etc.
Forum rules
  • Check the documentation first. Before posting questions, please check the documentation to ensure it doesn't already cover what you need.
  • No spam. All automated messages, advertisements, and links to competitor websites will be deleted immediately.
  • Post in relevant sub-forums only. Messages posted in the wrong topic area will be removed and placed in the correct sub-forum by moderators.
  • Respect other users. No flaming or abusing fellow forum members. Users who continue to post inflammatory, abusive comments will be deleted from the forum after two warnings are issued by moderators.
  • Harassment. No threats or harassment of other users will be tolerated. Any instance of threatening or harassing behavior is grounds for deletion from the forums.
  • Adult content. No profanity or pornography is allowed. Posts containing adult material will be deleted.
  • Bandwidth. All images and signatures must be 500 x 500 pixels or smaller. Posts containing over-sized images and signatures will be removed.
  • Illegal content. No re-posting of copyrighted materials or other illegal content is allowed. Any posts containing illegal content or copyrighted materials will be deleted.
Post Reply
jmc2408
Posts: 100
Joined: Thu Jul 09, 2020 3:41 pm
Location: Glasgow, Scotland
Contact:

X-HTTP-Method-Override

Post by jmc2408 » Thu Jun 11, 2026 10:42 am

Has usage/support of using X-HTTP-Method-Override HTTP Headers been removed?
I use to use a connector in one of my services which only allows GET/POST so i was making use of this HTTP header to change that to PATCH when i required that type, but maybe 6-8 weeks back this seems to have stopped and all indications are simPRO has made a change? Any info would be helpful. Thanks.
SimproAPITeam
Posts: 831
Joined: Wed May 01, 2024 2:31 am

Re: X-HTTP-Method-Override

Post by SimproAPITeam » Mon Jun 22, 2026 1:39 am

This is a deliberate security-conscious configuration change aligned with the direction of our framework itself, which has also begun deprecating this feature, out of our control.

What this means for you:
Any requests relying on X-HTTP-Method-Override: PATCH to tunnel a PATCH request over a POST will now be treated as a plain POST request, which would explain the failure you're experiencing.

What we recommend:
To continue using endpoints that require PATCH, PUT, or DELETE HTTP methods, you'll need a connector or integration middleware that supports sending native HTTP methods directly. Options to explore:

1. Upgrade your connector — check whether the service has updated versions or settings that allow native PATCH/PUT/DELETE support.
2. Use a middleware/proxy — an intermediary service (e.g. a lightweight API gateway or serverless function) could translate your POST + header into a proper PATCH before forwarding to simPRO.
3. Contact your connector vendor — if you're using a third-party iPaaS tool (e.g. Zapier, Make/Integromat, Boomi), raise a support request with them to add native PATCH support.

Regards,
Simpro API Team | Simpro Software Group
Post Reply