POST /v1/contacts

Default value: "application/json"

Include the Content-Encoding: gzip header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.

A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue.

The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), and quote (').

The value is in the Bearer {token} format where {token} is a valid OAuth token generated by calling Create an OAuth token.

Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types.

With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident.

An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header.

Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.

The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails.

If the header is not set, the operation is performed in scope of the user's accessible orgs.

Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.

If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.

The contact's personal email address.

The ID of the account associated with the contact.

Note: When creating a contact, you must specify accountNumber, accountId, or both in the request body. If both fields are specified, they must correspond to the same account.

The second line of the contact's address.

The first line of the contact's address, which is often a street address or business name.

The contact's home phone number.

The state or province of the contact's address.

The zip code for the contact's address.

The type of the additional phone number.

Possible values:

• "Other"
• "Mobile"
• "Work"
• "Home"

The city of the contact's address.

The contact's business email address.

A description for the contact.

The number of the customer account associated with the contact.

Note: When creating a contact, you must specify accountNumber, accountId, or both in the request body. If both fields are specified, they must correspond to the same account.

The contact's fax number.

A nickname for the contact.

The contact's business phone number.

The contact's last name.

The mobile phone number of the contact.

An additional phone number for the contact.

If using Zuora Tax, a region string as optionally defined in your tax rules. Not required.

The contact's first name.

The country of the contact's address.

The county. May optionally be used by Zuora Tax to calculate county tax.