module function · N/https/clientCertificate
post()
clientCertificate.post(options)
Sends a SSL secured POST request to a remote server.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1clientCertificate.post({2 url: /* string, required */,3 certId: /* string, required */,4 body: /* string, required */,5 headers: /* object, optional */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.url | string | required | The URL address of the remote server. |
| options.certId | string | required | The ID of the client certificate. |
| options.body | string | required | The POST data to be sent to the remote server. |
| options.headers | object | optional | The HTTPS headers associated with the request. For more information, see HTTPS Header Information . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to clientCertificate.post(options) today. How should it read?
C
community proposals
Competing syntax for post, 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?