Create custom object definitions

You can post custom object definitions with the request body schema described below.

This operation also allows you to use the List custom object definitions response schema as its request schema. If you want to copy all the existing custom objects from an old tenant to a new tenant, you can make a List custom object definitions call in your old tenant and then use its response directly as the request of this operation in the new tenant to import all the custom objects from the old tenant.

The label field is the UI label of the custom object. The object field contains the API Name of the custom object.

Limitations

This custom object definition has the following limitations:

  • The maximum number of characters for the Custom Object API Name (object) is 64.
  • The maximum number of characters for the Custom Object Label (label) is 64.
  • The maximum number of characters for the Custom Object Description 250.
  • The maximum number of custom fields in an custom object is 50.
  • The maximum number of characters for the custom field API name is 64.
  • The maximum number of characters for the custom field label (label) is 64.
  • The maximum number of characters for the custom field Description is 250.
  • The maximum number of picklist or multiselect options is 250.
  • The maximum length of characters for the Text field is 255.
  • The maximum length of characters for the Long Text field is from 256 to 8,192.
  • The maximum number of digits to the left of the decimal point for the Number field is 13, and to the right is 9.
Request
header Parameters
Accept-Encoding
string

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.

Content-Encoding
string

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.

Zuora-Track-Id
string <= 64 characters

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 (').

Zuora-Entity-Ids
string

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.

Zuora-Org-Ids
string

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.

Authorization
required
string

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

Zuora-Version
string <date>

API version that determines the response schema. The default version is used if this parameter is not included. Specify Zuora-Version in the request header if you expect a specific response schema.

Request Body schema: application/json
required

The custom object definitions to be created

object (customObjectDefinitions)

The custom object definitions. This object maps types to custom object definitions.

Responses
200

OK

400

Bad request

post/objects/definitions/default
Request samples
application/json
{
  • "definitions": {
    }
}
Response samples
application/json
{
  • "count": 2,
  • "definitions": {
    }
}