Skip to main content

API Challenges Simple Todo List

A Simple todo list

Use the Content-Type header to define the payload content e.g.

Content-Type: application/json

Set Content-Type header to application/xml if you want to send in XML.

Content-Type: application/xml

You can control the returned data format by setting the Accept header

You can request XML response by setting the Accept header.

i.e. for XML use

Accept: application/xml

You can request JSON response by setting the Accept header.

i.e. for JSON use

Accept: application/json

Additional response Accept headers are supported.

Accept: text/csv
Accept: text/plain
Accept: text/html
Accept: application/x-ndjson
Accept: application/jsonl
Accept: application/json-seq
Accept: text/tab-separated-values

Some requests can be filtered by adding query params of fieldname=value. Where only matching items will be returned.

Filter conditions can use field=value for equals, field!=value or field!value for not equals, field<value, field>value, field<=value, and field>=value for comparisons, field~=regex for regular expression matches, and field*=wildcard for wildcard matches where * matches many characters and ? matches one character. Multiple query params are combined as AND conditions.

e.g. /thing?size=2&status=true

Some requests can be sorted by adding the _sortBy query param with a field name. Use _sortBy=+field or _sortBy=field for ascending order, and _sortBy=-field for descending order. Multiple fields can be combined with commas, e.g. _sortBy=+field,-other.

Collection requests can be paged with _limit=limit and _offset=offset. Offset is zero-based, the default limit is 10, and the maximum limit is 20.

Model

Things

todo

Fields:
Fieldname Type Description
idAUTO_INCREMENT
  • Field is an ID and should not be amended or set
Example: "80"
titleSTRING
  • The title of the TODO Item
  • Value is mandatory
  • Value can not be empty
  • Maximum length allowed is 50
Example: "A title"
doneStatusBOOLEAN
  • Status to track the todo completion
  • Value must be a Boolean (true, false) value
Example: "false"
descriptionSTRING
  • Longer description of the todo
  • Maximum length allowed is 200
Example: "my description"

Example JSON Output from API calls


{
  "todos": [
    {
      "id": 80,
      "title": "A title",
      "doneStatus": false,
      "description": "my description"
    }
  ]
}

Example XML Output from API calls


<todos>
  <doneStatus>false</doneStatus>
  <description>my description</description>
  <id>80</id>
  <title>A title</title>
</todos>

Example JSON Input to API calls


{
  "id": 1,
  "title": "A title",
  "doneStatus": false,
  "description": "my description"
}

Example XML Input to API calls


<todo>
  <doneStatus>false</doneStatus>
  <description>my description</description>
  <id>1</id>
  <title>A title</title>
</todo>

API

The API takes body with objects using the field definitions and examples shown in the model.

End Points

/todos

e.g. /todos

This endpoint can be filtered with fields as URL Query Parameters.

e.g. /todos?title=A%20title&description=my%20description

This endpoint can be sorted with the _sortBy URL Query Parameter. Use _sortBy=+field or _sortBy=field for ascending order, and _sortBy=-field for descending order. Multiple fields can be combined with commas, e.g. _sortBy=+field,-other.

e.g. /todos?_sortBy=+id

This endpoint can be paged with the _limit and _offset URL Query Parameters.

e.g. /todos?_limit=10&_offset=0

QUERY content uses Content-Type: application/x-www-form-urlencoded with fields such as title=Task&_sortBy=-id.

/todos/:id

e.g. /todos/:id

/challenger/:guid

e.g. /challenger/:guid

/challenger

e.g. /challenger

/challenger/database/:guid

e.g. /challenger/database/:guid

/challenges

e.g. /challenges

/heartbeat

e.g. /heartbeat

/todos/export

e.g. /todos/export

/secret/token

e.g. /secret/token

/secret/note

e.g. /secret/note

Open Swagger UI

 

Copyright Compendium Developments Ltd 2020 - 2026