404 — service not found or not published

Updated 2026-11-13

A call answers HTTP 404 "Not found". This page lists the causes — wrong address, draft, unpublished, deleted — and how to tell them apart.

What you see

{ "error": "Not found", "message": "Service not found or not published" }

The answer means: there is no published service under the id in the address. It is the same answer for an id that never existed, a draft, an unpublished service and a deleted one. People who are not the owner cannot tell these cases apart; the owner can, in the app.

Causes and fixes

  1. The service is a draft. A new service is a draft until it is published, and a draft cannot be called. Open the service and click Publish (Veröffentlichen). See Publish and republish.
  2. The id in the address is wrong. One missing or changed character is another id. Copy the address again from the service: the snippets under API → Code contain it complete.
  3. The path is wrong. The address is https://spreadapi.io/api/v1/services/SERVICE_ID/execute. Check for a missing /execute, a doubled slash or a placeholder such as {id} or SERVICE_ID that was never replaced. See Call a service over the API.
  4. The service was unpublished. The owner took it offline with Unpublish (Deaktivieren). The address answers 404 until the service is published again; the id stays the same.
  5. The service was deleted. A deleted service is gone with its address. See Delete a service or the account.
  6. You are calling another service. Every service has its own id, a copy of a service too. Calls must use the id of the service that is published.

How the owner checks

  1. Open the service list and find the service; see Manage services for the status badges.
  2. Open the service. The header shows Publish for a draft and the status button Published for a service that is online.
  3. Compare the id in the browser address of the service page with the id in the failing call.
  4. If the service is a draft, publish it. If publishing is refused, see Publish problems.

A plan change does not take a service offline: what is published stays published. See The published services limit.

Saved is not published

Save (Speichern) stores your work in the draft. Callers only ever reach the published version. A service that was saved but never published answers 404; a published service whose changes were saved but not republished still answers with the old version. See Wrong or old results.

Other addresses of the same service

The discovery address, the MCP address, the web app and the snippets all need a published service too. See The discovery address, The MCP address of a service and The web app.

For developers and agents

  • API, GET and POST: HTTP 404, {"error": "Not found", "message": "Service not found or not published"}.
  • Discovery address (/d/{id}): HTTP 404, {"success": false, "error": "Service not found or not published"}.
  • Service MCP address: HTTP 404 with the error Service not found or not published.
  • OpenAPI file of the service: HTTP 404 for an id without a published service.
  • A 404 is not counted as a call of the month and does not appear in the usage log.
  • The check for a published service comes before the token check: with a wrong id you get 404 whatever token you send.
  • For an agent: do not retry a 404. Report the id you called and ask the user to confirm the address and that the service is published. An agent connected to the account can list the services and their status instead; see What an agent can do.

FAQ

What does "Service not found or not published" mean?

There is no published service under the id in your address. Either the id or the path is wrong, or the service is a draft, was unpublished or was deleted.

Why does my new service answer 404?

A new service is a draft, and a draft cannot be called. Save it and click Publish (Veröffentlichen); the address works as soon as publishing has succeeded.

I saved my service. Why is it still not reachable?

Saving stores the draft; it does not put the service online. Click Publish after saving.

Does the address change when I unpublish and publish again?

No. The service keeps its id, so the same address works again once the service is published.

Can I call a draft to test it?

Not over the API address. Use the test button in the editor, which runs your values on the draft: see Test before publishing.

How do I find the correct address of my service?

Open the published service and go to API → Code; every snippet there contains the full address with the service id. Copy it from there instead of typing it.

Does a 404 count against my monthly calls?

No. A call that answers 404 is not counted and is not listed in Usage → Log.

Did my service go offline because of my plan?

No. A published service stays online when the plan changes, and it can be published again. Check whether someone unpublished or deleted it.

My AI assistant says the service cannot be found. What now?

Check first that the service is published, then that the assistant uses the current address. More cases are in AI troubleshooting.