Find Answers

Find Answers

Specified Languages
British English

Contact Us

Merchant Support

Toll-Free Phone:
(877) 447-3938

Support Hours:
(Closed major holidays)

Reseller Support

Toll-Free Phone:
(888) 437-0481

Support Hours:
M–F: 6 AM – 5 PM PDT
(Closed major holidays)

Affilate Support

Toll-Free Phone:
(866) 682-4131

Support Hours:
M–F: 6 AM – 5 PM PDT
(Closed major holidays)

Corporate Offices

Authorize.Net (Utah)
P.O. Box 947
American Fork, UT 84003-0947
Tel: 801.492.6450
Fax: 801.492.6489

What is the difference between HTTP GET and HTTP POST?

Doc ID:    A1702
Version:    3.0
Status:    Published
Published date:    05/31/2017
Updated:    05/31/2017


The Hypertext Transfer Protocol (HTTP) is the heart of the World Wide Web. It defines methods used when sending, receiving, or modifying resources over the web.

GET is the HTTP method used when requesting a resource -- for example, when loading a web page or its elements.

The only way to send data with GET is by adding parameters to the URL. Usually, that means adding a question mark ("?") to the URL, followed by a set of names and values, separated by ampersands ("&"). For example:

When using Secure HTTP (HTTPS), it is important to note that any parameters in the URL will not be encrypted in server logs or browser caches, which in turn may or may not be adequately secured.

The POST method, in contrast, is specifically used to submit data to servers. The data is stored in the body of the HTTP request, rather than in the URL. Therefore, when used with HTTPS, the HTTP body and its sensitive data are fully encrypted.

We strongly recommend using HTTP POST for your API calls to or to

Authorize.Net has disabled HTTP GET as an option for the above URLs as of the following dates:

Sandbox: 05/01/2017
Prodution: 05/31/2017

You can use the Data Validation Tool to help determine if your solution is using GET or POST. When submitting a request to the Data Validation Tool, the REQUEST_METHOD header will indicate whether the request was submitted using GET or POST.

Please consult with your web developer if you have questions about which method your solution uses, and for assistance in switching to HTTP POST.

Rate This Item