Subscriptions
View as MarkdownList hosting subscriptions and attach an application.
Authorization
oauth2 hosting.subscription:readGoDaddy OAuth 2.0 access token. The scope(s) listed on each operation are enforced per-operation. A token requires at least one of the scopes listed for that operation.
In: header
Scope: hosting.subscription:read
Query Parameters
Hosting product to scope the operation to. This filter is required rather than optional: an optional filter introduced after general availability would have to default to WEB_HOSTING for ever, or the set of subscriptions returned would silently change for clients that omit it. It is made required now, while this spec is still Beta.
Header Parameters
W3C Trace Context identifier for this request. Clients should send a traceparent on every request so the trace can be correlated across services. See https://www.w3.org/TR/trace-context/ for the format.
^[0-9a-f]{2}-[0-9a-f]{32}-[0-9a-f]{16}-[0-9a-f]{2}$Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/subscriptions?hostingProduct=WEB_HOSTING"{ "totalItems": 0, "totalPages": 0, "links": [ { "href": "http://example.com", "rel": "string", "title": "string", "targetMediaType": "string", "targetSchema": null, "method": "string", "submissionMediaType": "application/json", "submissionSchema": null } ], "items": [ { "subscriptionId": "string", "hostingProduct": "WEB_HOSTING", "tier": "ECONOMY", "label": "string", "status": "ACTIVE", "attachedCount": 0, "slotLimit": 0, "availableSlots": 0, "paidThroughDate": "2027-08-06T00:00:00Z", "links": [ { "href": "http://example.com", "rel": "string", "title": "string", "targetMediaType": "string", "targetSchema": null, "method": "string", "submissionMediaType": "application/json", "submissionSchema": null } ] } ]}Authorization
oauth2 hosting.subscription:readGoDaddy OAuth 2.0 access token. The scope(s) listed on each operation are enforced per-operation. A token requires at least one of the scopes listed for that operation.
In: header
Scope: hosting.subscription:read
Path Parameters
Application identifier in {PRODUCT}-{id} form. The prefix is the application type in upper case — an upper-case letter followed by any number of upper-case letters, digits, or underscores — then a hyphen, then the identifier. For NODEJS, the suffix is a 10-character nanoid. Example: NODEJS-aBcDeFgHiJ.
^[A-Z][A-Z0-9_]*-[A-Za-z0-9_-]+$Header Parameters
W3C Trace Context identifier for this request. Clients should send a traceparent on every request so the trace can be correlated across services. See https://www.w3.org/TR/trace-context/ for the format.
^[0-9a-f]{2}-[0-9a-f]{32}-[0-9a-f]{16}-[0-9a-f]{2}$Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/apps/string/subscription"{ "subscriptionId": "string", "hostingProduct": "WEB_HOSTING", "attachState": "ACTIVE", "appState": "PUBLISHED", "links": [ { "href": "http://example.com", "rel": "string", "title": "string", "targetMediaType": "string", "targetSchema": null, "method": "string", "submissionMediaType": "application/json", "submissionSchema": null } ]}Authorization
oauth2 hosting.subscription:writeGoDaddy OAuth 2.0 access token. The scope(s) listed on each operation are enforced per-operation. A token requires at least one of the scopes listed for that operation.
In: header
Scope: hosting.subscription:write
Path Parameters
Application identifier in {PRODUCT}-{id} form. The prefix is the application type in upper case — an upper-case letter followed by any number of upper-case letters, digits, or underscores — then a hyphen, then the identifier. For NODEJS, the suffix is a 10-character nanoid. Example: NODEJS-aBcDeFgHiJ.
^[A-Z][A-Z0-9_]*-[A-Za-z0-9_-]+$Header Parameters
W3C Trace Context identifier for this request. Clients should send a traceparent on every request so the trace can be correlated across services. See https://www.w3.org/TR/trace-context/ for the format.
^[0-9a-f]{2}-[0-9a-f]{32}-[0-9a-f]{16}-[0-9a-f]{2}$Request Body
application/json
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PUT "https://example.com/apps/string/subscription" \ -H "Content-Type: application/json" \ -d '{ "subscriptionId": "string" }'{ "subscriptionId": "string", "hostingProduct": "WEB_HOSTING", "attachState": "ACTIVE", "appState": "PUBLISHED", "links": [ { "href": "http://example.com", "rel": "string", "title": "string", "targetMediaType": "string", "targetSchema": null, "method": "string", "submissionMediaType": "application/json", "submissionSchema": null } ]}Agent & Automation Notes
hosting.application:read, hosting.application:create, hosting.application:update, hosting.application:delete, hosting.source:write, hosting.deployment:execute, hosting.secret:write, hosting.log:readRelated
Last updated on
How is this guide?