module function · N/https
requestSuiteTalkRest()
https.requestSuiteTalkRest(options)
Sends an HTTPS request to a SuiteTalk REST endpoint and returns the response.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1https.requestSuiteTalkRest({2 body: /* string | Object */,3 url: /* string, required */,4 headers: /* Object, optional */,5 method: /* string, optional */6});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.body | string | Object | The PUT/POST data. This is ignored if the options.method parameter is not POST or PUT. | |
| options.url | string | required | The URL of a SuiteTalk REST endpoint. It may also contain query parameters. The URL may be fully qualified, relative, or relative with the /services/rest/ prefix omitted. |
| options.headers | Object | optional | The HTTPS headers. |
| options.method | string | optional | The HTTPS method (DELETE, GET, HEAD, POST, PUT). The default value is GET if options.body is not specified, and POST if options.body is specified. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to https.requestSuiteTalkRest(options) today. How should it read?
C
community proposals
Competing syntax for requestSuiteTalkRest, from GitHub Discussions. Select two or more to compare them side by side.
Loading proposals from GitHub…
D
suggest an alternative
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,saveandRef[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?