The Problem (Q-score 6, ranked #19th of 67 in the Access VBA archive)
The scenario as originally posted in 2013
I have an API for my application which allows me to make cURL requests to it.
I need to implement this into VBA so my desktop database can fire CURL requests to my web app.
curl -i --user [email protected]:password -X PUT -d "test=testing" https://mywebsite.com/api
How can i implement this in Access VBA? Can i use WinHttp.WinHttpRequest.5.1 ?
Any examples?
Thanks
Adam,
Why community consensus is tight on this one
Across 67 Access VBA entries in the archive, the accepted answer here holds strong answer (top 25 %%) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — strong answer (top 25 %%) (+14)
9-line Access VBA pattern (copy-ready)
Solved it now guys, works well.
For other peoples convenience.
TargetURL = "https://www.mysite.co.uk/app/api/v1/test"
Set HTTPReq = CreateObject("WinHttp.WinHttpRequest.5.1")
HTTPReq.Option(4) = 13056 '
HTTPReq.Open "PUT", TargetURL, False
HTTPReq.SetCredentials "user", "password", 0
HTTPReq.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
HTTPReq.send ("test[status]=" & Forms!curl!Text0.Value & "&test2[status]=" & Text2.Value)
MsgBox (HTTPReq.responseText)
Error-handling details to lift with the snippet
This answer wires error flow through MsgBox / Err.Description. Keep that intact: stripping it to “make it cleaner” removes the signal you’ll need when the macro fails silently on a user machine.
When to Use It — classic (2013–2016)
Ranked #19th in its category — specialized fit
This pattern sits in the 55% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.
What changed between 2013 and 2026
The answer is 13 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.