API Headers

A header specifies details about the API request and response.

Overview

In an API call, a header provides additional information about your request and preferred response, such as your authorization to access the endpoint and the format to return in the response.

Accept

The content type that you want the API response returned in. Supported in all Data Query API endpoints. Valid values are application/json, application/jsonlines, or text/csv. Default is application/json.

Accept-Language

The language that you're sending in the API request body. Use this header in PATCH calls to localize basic information, such as display names, descriptions, and explanations. You can specify one language per API call. Use any of the following language codes:

  • en: English (United States). This is the default.
  • fr: French
  • de: German
  • pt: Portguese (Brazil)
  • es: Spanish (Mexico)
  • es-ES: Spanish (Spain)

apikey

Your Visier API key. Required in all API calls. For more information, see Generate an API Key.

Authorization

The JWT for OAuth 2.0. Required in API calls using OAuth 2.0 authentication. For more information, see OAuth 2.0 with Open ID Connect (OIDC).

Content-Type

The content type that you're sending in the API request body. Default is application/json.

Cookie:VisierASIDToken

A security token. Required in API calls using basic authentication. For more information, see Basic authentication.

Cookie:VisierImpersonationToken

A token that allows you to make API calls as the impersonated user. To get the token, see "Request an impersonation token" in API Reference.

NonVersioned

If true, the API call executes on non-versioned artifacts and create/update actions take effect without a new production version. If false, the API call executes on versioned artifacts and create/update actions release a new production version. Default is false. For more information, see Non-Versioned Security.

Prefer

When NonVersioned: true, use Prefer to optionally specify if API calls should be subject to locking. Locking prevents incremental changes in multiple API calls from overwriting each other. The Prefer header works alongside a tenant feature flag. When enabled, the default is nvLock=global. When disabled, the default is not to lock API calls. Contact Visier Technical Support to enable the tenant feature flag. Valid values for the Prefer header:

  • nvLock=global: Run API calls sequentially. Sequential API calls prevent calls from unintentionally overwriting each other.
  • nvLock=artifact: Allow API calls in parallel. Parallel API calls only work if the calls do not conflict with each other. If a change wasn't applied, the request fails and returns the HTTP 409 conflict error. Run the request again until successful.
  • nvLock=none: Disable the global lock if the tenant feature flag is enabled.

For more information, see Lock non-versioned security artifacts.

ProjectID

The project UUID in which to make your changes. For more information, see Projects API.