Eventify Categories API — Full CRUD Endpoints Reference

Categories provide a simple classification layer for events in Eventify. Each category has only a name field, keeping the resource lightweight and easy to manage. Events reference a category via their category_id foreign key, and the category object is included as an eager-loaded relation whenever you fetch event data through the Events API. Use the five endpoints below to list, retrieve, create, update, and delete categories.

The category object

integer

Auto-incremented primary key uniquely identifying the category.

string

Human-readable display name for the category (e.g. "Technology", "Music", "Sports").

datetime

ISO 8601 datetime string set automatically when the record is first created.

datetime

ISO 8601 datetime string updated automatically whenever the record is modified.

GET /api/category

Returns an array of all category records in the database. No filtering, pagination, or sorting parameters are supported — the full collection is always returned.

curl http://localhost:8000/api/category \
  -H "Accept: application/json"

Response — 200 OK

[
  {
    "id": 1,
    "name": "Technology",
    "created_at": "2024-05-01T00:00:00.000000Z",
    "updated_at": "2024-05-01T00:00:00.000000Z"
  },
  {
    "id": 2,
    "name": "Music",
    "created_at": "2024-05-01T00:00:00.000000Z",
    "updated_at": "2024-05-01T00:00:00.000000Z"
  },
  {
    "id": 3,
    "name": "Sports",
    "created_at": "2024-05-01T00:00:00.000000Z",
    "updated_at": "2024-05-01T00:00:00.000000Z"
  }
]

Returns an empty array [] with status 200 when no categories exist.

GET /api/category/{id}

Returns a single category identified by its integer id. Path parameter

integer

required

The unique identifier of the category to retrieve.

curl http://localhost:8000/api/category/1 \
  -H "Accept: application/json"

Response — 200 OK

{
  "id": 1,
  "name": "Technology",
  "created_at": "2024-05-01T00:00:00.000000Z",
  "updated_at": "2024-05-01T00:00:00.000000Z"
}

Error responses

Status	Body
`404 Not Found`	`{"message": "Categoria no encontrada"}`

POST /api/category

Creates a new category. The only required field is name. Returns the created category object with HTTP 201 Created. Request body

string

required

Display name for the new category. Maximum 255 characters. Must be a non-empty string.

curl -X POST http://localhost:8000/api/category \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{"name": "Art & Culture"}'

Response — 201 Created

{
  "id": 4,
  "name": "Art & Culture",
  "created_at": "2024-05-20T10:00:00.000000Z",
  "updated_at": "2024-05-20T10:00:00.000000Z"
}

Error responses

Status	Body
`422 Unprocessable Entity`	Laravel validation error object — e.g. `name` missing or exceeds 255 characters

PUT /api/category/{id}

Updates an existing category. The name field is optional — if omitted, the existing value is preserved. The record is located by id before any update is applied. Path parameter

integer

required

The unique identifier of the category to update.

Request body

string

New display name for the category. Maximum 255 characters. If provided, must be a non-empty string.

curl -X PUT http://localhost:8000/api/category/4 \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{"name": "Arts & Culture"}'

Response — 200 OK

{
  "id": 4,
  "name": "Arts & Culture",
  "created_at": "2024-05-20T10:00:00.000000Z",
  "updated_at": "2024-05-20T11:45:00.000000Z"
}

Error responses

Status	Body
`404 Not Found`	`{"message": "Categoria no encontrada"}`
`422 Unprocessable Entity`	Laravel validation error object

DELETE /api/category/{id}

Permanently deletes the category with the given ID. Path parameter

integer

required

The unique identifier of the category to delete.

curl -X DELETE http://localhost:8000/api/category/4 \
  -H "Accept: application/json"

Response — 200 OK

{
  "message": "Categoria borrada"
}

Error responses

Status	Body
`404 Not Found`	`{"message": "Categoria no encontrada"}`

Deleting a category that is currently referenced by one or more events will set those events’ category_id to null (cascade set null behaviour defined in the events migration). Verify that no events are using a category before deleting it if referential integrity matters to your application.

​The category object

​GET /api/category

​GET /api/category/{id}

​POST /api/category

​PUT /api/category/{id}

​DELETE /api/category/{id}

The category object

GET /api/category

GET /api/category/{id}

POST /api/category

PUT /api/category/{id}

DELETE /api/category/{id}