API ReferenceDomainDomain LifecycleDomains & DNSv1 (Legacy)Get required legal agreements for a TLD GET
Get required legal agreements for a TLD
View as MarkdownReturns the TLD-specific legal agreements that must be accepted before purchase or transfer.
Full description
Returns the TLD-specific legal agreements that must be accepted before purchase or transfer. The agreementKeys from this response are required in the consent object.
Authorization
bearerAuth AuthorizationBearer <token>
Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Query Parameters
tlds*array<string>
list of TLDs whose legal agreements are to be retrieved
v1-privacy*boolean
Whether or not privacy has been requested
forTransfer?boolean
Whether or not domain tranfer has been requested
Header Parameters
X-Market-Id?string
Unique identifier of the Market used to retrieve/translate Legal Agreements
Format
bcp-47Default
"en-US"Response Body
curl -X GET "https://example.com/v1/domains/agreements?tlds=string&v1-privacy=true"[ { "agreementKey": "string", "content": "string", "title": "string", "url": "string" }]Agent & Automation Notes
Scopes
domains.domain:read, domains.domain:create, domains.domain:delete, domains.domain:update, domains.contact:update, domains.dns:update, domains.transfer:executeRate limit60 req/min per credential
On failureGET operations are safe to retry. PUT/PATCH DNS are idempotent by shape. POST purchase is NOT idempotent — verify state before retrying.
Related
Last updated on
How is this guide?