Create a template record
Creates a new template record.
Path parameters
The account id
The template id or short name
Request body
Example request
{
"name": "",
"type": "MX",
"content": "mx.example.com",
"ttl": 600,
"priority": 10
}Response
Successfully create a template record.
Example response
{
"data": {
"id": 296,
"template_id": 268,
"name": "",
"content": "192.168.1.1",
"ttl": 3600,
"priority": null,
"type": "A",
"created_at": "2016-04-26T08:23:54Z",
"updated_at": "2016-04-26T08:23:54Z"
}
}Changes
Changed in 3 of the 52 revisions of this API.16512
- ▲
the
/response's property type changed fromintegertostringnullfor statusresponse-property-type-changed
- ▲
- ▲
added the new required request property
new-required-request-property
- ▲
added the new required request property
new-required-request-property
- ▲
added the new required request property
new-required-request-property
- ○
added the new optional request property
new-optional-request-property
- ○
added the new optional request property
new-optional-request-property
- ○
the response property
became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ▲
- ▲
the response property
/became nullable for the statusresponse-property-became-nullable
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the response property
/became optional for the statusresponse-property-became-optional
- ▲
the
/response's property type changed fromstringnulltointegerfor statusresponse-property-type-changed
- ●
removed the request property
request-property-removed
- ●
removed the request property
request-property-removed
- ●
removed the request property
request-property-removed
- ●
removed the request property
request-property-removed
- ●
removed the request property
request-property-removed
This revision also has 25 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲