module function · N/http

post()

http.post(options)

Sends an HTTP POST request and returns the response.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
http.post(options)
Module
N/http
Returns
http.ClientResponse or http.ServerResponse
Governance
10 units
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1http.post({2    body:    /* string | Object, required */,3    url:     /* string, required */,4    headers: /* Object, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.bodystring | ObjectrequiredThe POST data. Note: Sending a file using multipart/form-data content type in the options.body parameter is not supported.
options.urlstringrequiredThe HTTP URL being requested. For information about resolving a URL, see N/url Module . For information about getting the URL for a script, including Suitelets, see url.resolveScript(options) .
options.headersObjectoptionalThe HTTP headers. For more information, see HTTP Header Information .
B

No Mynt syntax yet.

Nothing in the language compiles to http.post(options) today. How should it read?

C

Competing syntax for post, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

Write the Mynt you wish you could write.

A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.

  • Clarity. Does it say what happens, without ceremony?
  • Consistency. Does it read like load, save and Ref[field]?
  • Expressiveness. Does it cover the cases people actually write?
  • Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?

N/http · http.post(options)

Suggest syntax for post