Get a Custom Field
GET/v2/settings/extensions/custom-apis/:custom_api_id/fields/:custom_field_id
Get a Custom Field
Request
Path Parameters
The id of the Custom API.
The id of the Custom Field.
Responses
- 200
- 400
- 404
- 500
OK
- application/json
- Schema
- Example (from schema)
Schema
- BooleanCustomFieldAttributes
- StringCustomFieldAttributes
- IntegerCustomFieldAttributes
- FloatCustomFieldAttributes
data object required
The unique identifier of the Custom Field.
Specifies the type of the resource object, use custom_field
for Custom Field.
Possible values: non-empty
and <= 255 characters
Specifies the name of this Custom Field.
Possible values: <= 255 characters
Specifies the description for this Custom API.
Possible values: non-empty
and <= 63 characters
Specifies a slug that must be unique within the scope of the Custom API. This slug will be value as the key in the JSON Object in all entries.
Possible values: [string
, integer
, boolean
, float
]
Specifies the type of the field. This field cannot be updated.
Enabling this field will mean Custom API Entries created in this Custom API will use this value in the URL instead of the id
attribute. In order to set this field, the field must be a string, and unique, not allow null values, no entries have been created yet, and this field cannot be set to true on another custom field. This field cannot be updated. In addition to any validation rules you create, the values must be Unreserved URL Characters (i.e., be alpha-numeric, or one of -
, .
, _
or ~
).
presentation object
Possible values: <= 1000
Default value: 0
Specifies the order of the field in the User Interface.
links object
meta object
timestamps objectrequired
Specifies the date the entity is created.
Specifies the date the entity is last updated.
validation object
boolean object
Default value: true
When set to true
, this allows null
values for that field on Custom API Entries. When set to false
, storing null
values is not permitted.
When set to true
, prevents changing the field.
The unique identifier of the Custom Field.
Specifies the type of the resource object, use custom_field
for Custom Field.
Possible values: non-empty
and <= 255 characters
Specifies the name of this Custom Field.
Possible values: <= 255 characters
Specifies the description for this Custom API.
Possible values: non-empty
and <= 63 characters
Specifies a slug that must be unique within the scope of the Custom API. This slug will be value as the key in the JSON Object in all entries.
Possible values: [string
, integer
, boolean
, float
]
Specifies the type of the field. This field cannot be updated.
Enabling this field will mean Custom API Entries created in this Custom API will use this value in the URL instead of the id
attribute. In order to set this field, the field must be a string, and unique, not allow null values, no entries have been created yet, and this field cannot be set to true on another custom field. This field cannot be updated. In addition to any validation rules you create, the values must be Unreserved URL Characters (i.e., be alpha-numeric, or one of -
, .
, _
or ~
).
presentation object
Possible values: <= 1000
Default value: 0
Specifies the order of the field in the User Interface.
links object
meta object
timestamps objectrequired
Specifies the date the entity is created.
Specifies the date the entity is last updated.
validation object
string object
Possible values: <= 65535
Specifies the minimum number of characters that can be stored.
Possible values: <= 65535
Specifies the minimum number of characters that can be stored.
Possible values: <= 1024 characters
An RE2 regular expression that used to restrict the specific characters that can be stored.
Default value: true
When set to true
, this allows null
values for that field on Custom API Entries. When set to false
, storing null
values is not permitted.
nullable: false
Possible values: [yes
, no
]
Default value: no
If yes
, this prevents two Custom API entries from having the same value for this field within the Custom API. When set to no
(the default),
multiple Custom API entries may have the same value
Controls case-insensitive uniqueness for this field. Can only be set to true
if unique
is set to yes
.
If true
, prevents two Custom API entries from having the same value for this field within the Custom API, ignoring case differences.
When set to false
(the default), case is considered when checking for uniqueness.
This value can only be set during field creation and cannot be modified afterwards.
When set to true, the value of this field can be specified only during POST requests and cannot be modified during PUT requests.
The unique identifier of the Custom Field.
Specifies the type of the resource object, use custom_field
for Custom Field.
Possible values: non-empty
and <= 255 characters
Specifies the name of this Custom Field.
Possible values: <= 255 characters
Specifies the description for this Custom API.
Possible values: non-empty
and <= 63 characters
Specifies a slug that must be unique within the scope of the Custom API. This slug will be value as the key in the JSON Object in all entries.
Possible values: [string
, integer
, boolean
, float
]
Specifies the type of the field. This field cannot be updated.
Enabling this field will mean Custom API Entries created in this Custom API will use this value in the URL instead of the id
attribute. In order to set this field, the field must be a string, and unique, not allow null values, no entries have been created yet, and this field cannot be set to true on another custom field. This field cannot be updated. In addition to any validation rules you create, the values must be Unreserved URL Characters (i.e., be alpha-numeric, or one of -
, .
, _
or ~
).
presentation object
Possible values: <= 1000
Default value: 0
Specifies the order of the field in the User Interface.
links object
meta object
timestamps objectrequired
Specifies the date the entity is created.
Specifies the date the entity is last updated.
validation object
integer object
Specifies the minimum whole number that can be stored.
Specifies the maximum whole number that can be stored.
Default value: true
When set to true
, this allows null
values for that field on Custom API Entries. When set to false
, storing null
values is not permitted.
When set to true
, prevents changing the field.
The unique identifier of the Custom Field.
Specifies the type of the resource object, use custom_field
for Custom Field.
Possible values: non-empty
and <= 255 characters
Specifies the name of this Custom Field.
Possible values: <= 255 characters
Specifies the description for this Custom API.
Possible values: non-empty
and <= 63 characters
Specifies a slug that must be unique within the scope of the Custom API. This slug will be value as the key in the JSON Object in all entries.
Possible values: [string
, integer
, boolean
, float
]
Specifies the type of the field. This field cannot be updated.
Enabling this field will mean Custom API Entries created in this Custom API will use this value in the URL instead of the id
attribute. In order to set this field, the field must be a string, and unique, not allow null values, no entries have been created yet, and this field cannot be set to true on another custom field. This field cannot be updated. In addition to any validation rules you create, the values must be Unreserved URL Characters (i.e., be alpha-numeric, or one of -
, .
, _
or ~
).
presentation object
Possible values: <= 1000
Default value: 0
Specifies the order of the field in the User Interface.
links object
meta object
timestamps objectrequired
Specifies the date the entity is created.
Specifies the date the entity is last updated.
validation object
float object
Specifies the minimum whole number that can be stored.
Specifies the maximum whole number that can be stored.
Default value: true
When set to true
, this allows null
values for that field on Custom API Entries. When set to false
, storing null
values is not permitted.
When set to true
, prevents changing the field.
{}
Bad request. The request failed validation.
- application/json
- Schema
- Example (from schema)
- missing-name
Schema
- Array [
- ]
errors Error[]required
A brief summary of the error.
The HTTP response code of the error.
Optional additional detail about the error.
{
"errors": [
{
"title": "string",
"status": "string",
"detail": "string"
}
]
}
{
"errors": [
{
"title": "Bad Request",
"status": "400",
"detail": "The field 'name' is required."
}
]
}
Not found. The requested entity does not exist.
- application/json
- Schema
- Example (from schema)
- not-found
Schema
- Array [
- ]
errors Error[]required
A brief summary of the error.
The HTTP response code of the error.
Optional additional detail about the error.
{
"errors": [
{
"title": "string",
"status": "string",
"detail": "string"
}
]
}
{
"errors": [
{
"title": "Not Found",
"status": "404",
"detail": "Not found"
}
]
}
Internal server error. There was a system failure in the platform.
- application/json
- Schema
- Example (from schema)
- internal-server-error
Schema
- Array [
- ]
errors Error[]required
A brief summary of the error.
The HTTP response code of the error.
Optional additional detail about the error.
{
"errors": [
{
"title": "string",
"status": "string",
"detail": "string"
}
]
}
{
"errors": [
{
"title": "Internal Server Error",
"status": "500",
"detail": "there was a problem processing your request"
}
]
}