--- title: Deregister a site url: https://developers.wpengine.com/docs/ai/api/reference/operations/deletesite/ image: https://developers.wpengine.com/og/docs/ai/api/reference/operations/deletesite.png --- # Deregister a site DELETE /v1/sites/{client_id} Select code sample ```php request('DELETE', 'https://api.ai.wpengine.com/v1/sites/example', [ 'headers' => [ 'Authorization' => 'Bearer ', ], ]); echo $response->getBody(); ``` - Current environment Deregisters the calling site, revoking its registration along with any site activations and connected WordPress user accounts. Called by the WordPress plugin when a site disconnects. The caller must authenticate with the site’s own oauth-ext access token, and — unlike GET and PATCH on this path — the path identifier must be the `client_id` that token was issued for, not the site’s `site_id`. Requests for any other site are answered with 404 rather than 403 so a site cannot probe for the existence of registrations it does not own. Deregistration is idempotent from the caller’s point of view: once the registration is revoked, subsequent calls return 404. ## Authorizations - **[bearerAuth](https://developers.wpengine.com/docs/ai/api/reference/#bearerauth)** ## Parameters ### Path Parameters **client_id** required string The site’s stable `site_id`, or its `client_id` (the original credential identifier), which remains supported for backward compatibility. ## Responses ### 200 The site was deregistered. Media typeapplication/json object **status** required Confirms the registration was revoked. string Allowed values: deregistered #### Example ```json { "status": "deregistered" } ``` ### 401 Missing or invalid bearer token Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` #### Headers **WWW-Authenticate** string ##### Example ``` Bearer realm="ai-services" ``` ### 403 The token is valid, but the request is forbidden. Error type “permission_error” means the token’s scope/permission is insufficient or the authenticated user is not authorized for the target account; “entitlement_required” means the account may not use WP Engine AI, with error_code giving why when known (not_eligible, terms_required, not_enabled or suspended) and portal_url where to fix it; “account_required” means no billing account could be resolved; and “billing_account_pending” means billing isn’t set up for the account yet, usually because its setup after AI was turned on hasn’t finished. Retry shortly. On /v1/chat/completions when content moderation is enabled, and on /v1/sessions/{session_id}/events, error type “content_policy_violation” instead means the request content was blocked by content moderation policy; that response never identifies which filter or category matched. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ### 404 No active registration matches the path identifier, or it does not belong to the authenticated site. ### 500 The server encountered an unexpected error while handling the request. Safe to retry once; if it persists, the cause is server-side and the request payload was not the problem. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ### 503 A required dependency is temporarily unavailable. Retry after a short delay with exponential back-off. An entitlement lookup failure uses error type “entitlement_unavailable”. A model without complete rate coverage uses error type “model_unpriced”. A credit balance that can’t be read uses error type “balance_unavailable”. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ## Was this helpful? Thanks for the feedback! ```json {"@context":"https://schema.org","@graph":[{"@type":"WebSite","@id":"https://developers.wpengine.com/#website","name":"WP Engine Product Documentation","url":"https://developers.wpengine.com/","description":"Resources for developing, deploying, and scaling on WP Engine.","inLanguage":"en-US","keywords":["API documentation","product documentation","headless WordPress","managed WordPress hosting"],"publisher":{"@id":"https://wpengine.com/#organization"}}]} ```