bw:web_service_tool
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
bw:web_service_tool [2020/12/15 12:29] akoehler [Related Documents] |
bw:web_service_tool [2022/08/02 16:25] (current) akoehler |
||
|---|---|---|---|
| Line 125: | Line 125: | ||
| * [[SBO_SL_v25|SAP Business One using Service Layer with Bizweaver v2.5 and higher]] | * [[SBO_SL_v25|SAP Business One using Service Layer with Bizweaver v2.5 and higher]] | ||
| * [[BigCommerce_API|BigCommerce API]] | * [[BigCommerce_API|BigCommerce API]] | ||
| + | |||
| + | ====Web Service Tool Variables=== | ||
| + | |||
| + | ^ Name ^ Description^| | ||
| + | |Alt-svc| HTTP header allows a server to indicate that another network location (the " | ||
| + | |AuthenticationRequired |True or False if the authentication required checkbox is selected| | ||
| + | |BinaryDataFileName| This indicates the file name and location used for binary data and the exetension| | ||
| + | |BodyInfo| This is the request body of the API call that is being sent if any| | ||
| + | |BodyType| The type of body radio button that is selected ex. Raw, | ||
| + | |CF-Cache-Status| cache type being used for the API call default is Dynamic| | ||
| + | |CF-Ray| This header is a hashed value that encodes information about the data center and the visitor’s request.| | ||
| + | |Connection| This indicates that the WebService2 tool will keep the connection alive " | ||
| + | |Content-Encoding|The Content-Encoding representation header lists any encodings that have been applied to the representation (message payload), and in what order. This lets the recipient know how to decode the representation in order to obtain the original payload format. Content encoding is mainly used to compress the message data without losing information about the origin media type.| | ||
| + | |Content-Length| The Content-Length header indicates the size of the message body, in bytes, sent to the recipient.| | ||
| + | |Content-Security-Policy| The HTTP Content-Security-Policy response header allows website administrators to control the resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (Cross-site_scripting).| | ||
| + | |Content-Type| The Content-Type representation header is used to indicate the original media type of the resource (prior to any content encoding applied for sending). This will include the charset| | ||
| + | |ContentType |The Content-Type representation header is used to indicate the original media type of the resource (prior to any content encoding applied for sending).| | ||
| + | |CookieInfo| This will indicate if any information was entered in the cookies field if | | ||
| + | |Date| This indicates the date and time the request is being made| | ||
| + | |EnableJSONBodyFormat| True or False if the format body for JSON checkbox is selected| | ||
| + | |Expect-CT| The Expect-CT header lets sites opt into reporting and/or enforcement of Certificate Transparency requirements, | ||
| + | |FileAttachment| This indicates the file that is attached to the request| | ||
| + | |FormURLEncodedInfo| This indicates the data if any in the form URL encoded fields| | ||
| + | |GraphQL| This indicates if the GraphQL radio button was selected | | ||
| + | |HeaderInfo| This indicates if there was any header data passed into the API call| | ||
| + | |HTTP_X_SHOPIFY_SHOP_API_CALL_LIMIT| Returns the number number of total API calls made and the total number available| | ||
| + | |IgnoreCertificateErrors True or False if the ignore self-signed certificate errors checkbox is selected| | ||
| + | |InputString| This is the data that is being sent to the Salesforce API| | ||
| + | |IsBinaryData| True or False flag | | ||
| + | |IsSuccessful| True or False flag that indicates if the API call was successful or not| | ||
| + | |Link| This indicates the URL that is being returned by the API | | ||
| + | |Location| This specifies the name and location of the binary that is being used for an API Call| | ||
| + | |Method| The type of call you are making ex. Get, | ||
| + | |NEL| The HTTP NEL response header is used to configure network request logging.| | ||
| + | |OperationType| Dealing with the SAP SL or Salesforce connector it will be the option that is selected ex. Get Token, Interact with Data| | ||
| + | |OutputString| This is the response returned from the API| | ||
| + | |Referrer-Policy| The Referrer-Policy HTTP header controls how much referrer information (sent with the Referer header) should be included with requests. Aside from the HTTP header, you can set this policy in HTML.| | ||
| + | |RequestTimeout| The length of time entered into the timeout field in the Webservice2 tool default 100 seconds| | ||
| + | |RESTConnectionName| This indicates the connection used from the connection manager| | ||
| + | |SalesForce_AccessToken| This indicates the Salesforce access token when generated using the Salesforce connector| | ||
| + | |SalesForce_Behavior| Shows either Production or Sandbox| | ||
| + | |SalesForce_InstanceID| This indicates the instance id sent back from Salesforce| | ||
| + | |SalesForce_ManageData| This indicates if the manage object and data are selected when the Salesforce connector is selected| | ||
| + | |SalesForce_ObjetName| This indicates what object is selected when managing data in the Salesforce connector | | ||
| + | |SalesForce_RecordID| This indicates the record Id entered in the Record Id field in the Salesforce connector| | ||
| + | |SAPServiceLayer_RecordIDDataType| This indicates the data type of Record Id for the SAP Service Layer Record Id field| | ||
| + | |Server| the server that is used for the Webservice2 tool which is cloudflare| | ||
| + | |ServiceType| This will show either “Get Token”, “Interact with data” or “Manage Objects” etc. For custom, it should be blank| | ||
| + | |Set-Cookie| The Set-Cookie HTTP response header is used to send a cookie from the server to the user agent so that the user agent can send it back to the server later. To send multiple cookies, multiple Set-Cookie headers should be sent in the same response.| | ||
| + | |StatusCode| The status of an API call response ex. 200, 400| | ||
| + | |StatusDescription| The message for the API status code| | ||
| + | |Strict-Transport-Security| The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) informs browsers that the site should only be accessed using HTTPS and that any future attempts to access it using HTTP should automatically be converted to HTTPS.| | ||
| + | |Transfer-Encoding| The Transfer-Encoding header specifies the form of encoding used to safely transfer the payload body to the user.| | ||
| + | |URI| This indicated the URI entered into the Webservice2 tool| | ||
| + | |Vary| The Vary HTTP response header describes the parts of the request message aside from the method and URL that influenced the content of the response it occurs. Most often, this is used to create a cache key when content negotiation is in use.| | ||
| + | |X-Content-Type-Options| The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should be followed and not be changed. The header allows you to avoid MIME type sniffing by saying that the MIME types are deliberately configured.| | ||
| + | |StepMessage| During a failure the reason for failure will be populated here| | ||
| + | |StepStatus| True or False| | ||
| + | |**Note**| Some APIs will return different variables that are specific to that API and not Bizweaver| | ||
bw/web_service_tool.1608053377.txt.gz · Last modified: 2020/12/15 12:29 by akoehler
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
