Creating services using the rest api always fails with "service name required"

[antonmagnus]

Steps to reproduce.
Create a new sprite $SPRITE_NAME

Run the example from the docs:

curl -X PUT
-H "Authorization: Bearer $SPRITE_TOKEN"
-H "Content-Type: application/json"
-d '{"args":["-m","http.server","8000"],"cmd":"python","http_port":8000,"needs":["postgres"]}'
"https://api.sprites.dev/v1/sprites/$SPRITE_NAME/services/$SERVICE_NAME"

Returns "service name required".

Same with basic services

curl -X PUT
-H "Authorization: Bearer $SPRITE_TOKEN"
-H "Content-Type: application/json"
-d '{"name":"testservice","cmd":"/bin/sh","args":["-c","echo hello"],"needs":[]}'
"https://api.sprites.dev/v1/sprites/$SPRITE_NAME/services/$SERVICE_NAME"

Returns "service name required"

[samwightt]

Same issue here, almost none of the examples work in the documentation more than a week after public launch. The documentation is vague, unclearly worded, and basic things like "oh hey here's how to use our stuff" is just missing. These are things that would take like maybe a few hours just to write out shitty documentation for (and verify things work). Can that be prioritized please? If you want people to use your stuff, you kinda have to document how properly to use the stuff.

[antonmagnus]

Yes, my current workaround is creating the sprites and then managing the services with the internal api in the sprite.
I've seen these issues more and more. Seems like vibe-coding without human validation.