Delete a service location
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/service-locations/v1-service-location-destroy.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
DELETE/
Deletes a service location. It can be restored. Deleting one that is already deleted also succeeds (its delete time is set again).
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The service location's id (
idfrom List service locations). A hash id from an earlier answer; unique keys and document numbers (such asPO0042) don't work here.- Example
EDhVUaC6jbLbed
- Example
Request body
This operation takes no request body.
Response
200Successful response.
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.- When
- Your role cannot update services. This 403 has a short body,
{"message": "Insufficient Permission"}, with nosuccessorerror. - Fix
- Ask a team owner to raise Manage Services for your role.
404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- No service location with this id in the team.
error.codeis null anderror.messagenames the record type. - Fix
- Check the id.
Related
- PATCHRestore a service location
/v1/ api/ store/ {team_slug}/ service_location/ {hash_id}/ restore
