API


Version 1

GET /api/v1/variables

Retrieve the list of variables used in nonsense entries. Note that variables that are contained in entries retrieved via the API currently must be replaced on the client side with the client’s own variable logic implementation.

GET /api/v1/nonsense/random

Retrieve a random nonsense entry as JSON.

GET /api/v1/nonsense

Retrieve the nonsense database as a CSV1, JSON, or TXT2 file.

You may append these parameters at the end of the URL:

  • q=query — Restrict entries in the database export matching a search term.
  • format=format — Export the database as a csv1, json, or txt2 file.
  • after=timestamp — Only export entries after a specified Unix timestamp.
  • before=timestamp — Only export entries before a specified Unix timestamp.

Examples:

GET /api/v1/nonsense/:uuid

Retrieve a specific nonsense entry as JSON by its UUID.

GET /api/v1/nonsense/:uuid.png

Retrieve a share image of a specific nonsense entry by its UUID. Note that PNG is the only supported format for now.

GET /api/v1/nonsense/status

Retrieve the status of the nonsense database. This is useful when the client is caching the database for offline use. In that case, the client can compare the cache with the online database based on the timestamp of the latest entry.

EXPERIMENTAL: OData backend

This is experimental and may be removed in the future.

The (minimal) OData endpoints only exist to be used in data visualization software such as Tableau, like this dashboard for example.

/odata/v2/$metadata

Retrieve the metadata about the columns that are in the database with each of their own types.

/odata/v2/nonsense_list

Retrieve the database as Atom via OData v2. You can append ?all=true at the end of the URL to retrieve the full database.

Who’s using Nontrinsic?

Footnotes

  1. The default format for the export if the format is not explicitly included. 2

  2. Only single-line nonsense entries will be included in the plain text file (TXT) export. 2