Business 360 REST API Reference > Business 360 REST API > Request header
  

Request header

Use a request header to define the operating parameters or the metadata of a REST operation.
The following table lists the request header parameters:
Parameter
Description
Content-Type
Format of the request body.
Accept
Format of the request response. Accepts application/json.
IDS-SESSION-ID
The session ID of the user. See Session IDs.
MODEL_VERSION
Current version of the MDM SaaS configuration that includes the data model. Specify the model version as the current epoch timestamp in milliseconds.
If you don't specify the model version, the REST API defaults to using the cached version. Metadata related to the model is refreshed and cached every five minutes. If you submit API requests immediately after significant model changes without specifying the model version, responses might be based on an outdated cached model version. To get a correct response, specify the model version or wait up to five minutes until the metadata related to model refreshes and caches before you submit requests.
To improve performance and avoid request failures due to version differences, specify the same model version parameter in the request header when you send multiple requests in succession.
To construct the REST API request header for a resource, add the header parameter after the following request line:
//<baseURL>/v1/api/
Use the following syntax to construct the REST API request header for a REST API resource:
<METHOD> https: //<baseApiURL>/business-entity/public/api/v1/<resource name>
Content-Type: application/json
Accept: application/json
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
For example, you might use the following request to read a business entity master record:
GET https: //<baseApiURL>/business-entity/public/api/v1/entity/c360.organization/70046899550283630729399822719 HTTP/1.1
Content-Type: application/json
Accept: application/json
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
MODEL_VERSION:1706774113534