---
schema_version: "1"
id: c9a99a972a89879b06929e01987532de25fca2f45d54d037e882b2c3f719be59
title: Sforce Call Options Header
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/api-asynch/guides/api-bulk-v2/reference/bulk-api-2-0-headers-sforce-call-options.md
canonical_url: https://developer.salesforce.com/docs/platform/api-asynch/guide/bulk-api-2-0-headers-sforce-call-options.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 24c7bfdb58034b96e3400b9e0324fcd448e54c4b1e1ad8966fc1d87cc0d539d2
products:
  - Bulk API 2.0 and Bulk API Developer Guide
  - Platform Developer Content
---

# Sforce Call Options Header

Use the `Sforce-Call-Options` header to specify client-specific options when accessing Bulk API 2.0 resources.

## Header Field Name and Values

**Field name:** `Sforce-Call-Options`

**Field values:**

- `client`—A string that identifies a client, for use, for example, in event log files.
- `defaultNamespace`—A string that identifies a developer namespace prefix. Resolve field names in managed packages without having to specify the namespace everywhere.

**Example:**

If the developer namespace prefix is `battle`, and you have a custom field called `botId` in a package, set the default namespace with the call options header:

```nolang
Sforce-Call-Options: client=CaseSensitiveToken, defaultNamespace=battle
```

Then queries such as the following succeed:

```nolang
/services/data/vXX.X/query/?q=SELECT+Id+botID__c+FROM+Account
```

In this case, the actual field queried is the `battle__botId__c` field.

Using this header allows you to write client code without having to specify the namespace prefix. In the previous example, without the header you must write `battle__botId__c`.

If this field is set, and the query also specifies the namespace, the response doesn’t include the prefix. For example, if you set this header to `battle`, and issue a query like `SELECT+Id+battle__botID__c+FROM+Account`, the response uses a `botId__c` element, not a `battle_botId__c` element.

The `defaultNamespace` field is ignored when retrieving describe information, which avoids ambiguity between namespace prefixes and customer fields of the same name.