- Remove unneeded fields from a response to save on data transfer
- Expand relationships to minimise API calls
- Provide paged search results
- Returning only matching results
Lists are filtered by schedule according to the request context. This is explained in more detail in the Scheduling section.
Skylark API can return results using queries on fields and values. This allows client applications to get specific search results. These filters can also be used to automatically generate Set contents using Computed Scheduled Items.
The Skylark API can filter in several different ways:
|Specific value||Returns the Episodes with the slug ‘titanic’|
|Not a specific value||Returns Episodes that don’t have the slug ‘titanic’|
|One of a list of values||Returns Episodes that have any one of the included slugs|
|String contains a substring||Returns episodes with slugs containing the specified string (case-sensitive)|
|String contains a substring||Returns episodes with slugs containing the specified string (case-insensitive)|
|Specified timestamp||Created at of after the given timestamp. Dates and times are specified in ISO8601 format|
|Relative timestamp||Created within the last 10 days. Relative dates are calculated with respect to the current time.|
|Relationships||Images with the image_type_url field equal to the type at the given URL|
|Blank||Return all Sets with a blank description|
|Null||Return all Sets without a sponsor|
|Set Contents||Episodes that have been scheduled into either of the given Sets|
|Field on relationship||Returns Episodes with the given rating slug.|
|Multiple relationship URLs||Returns Episodes that have either of the given tag URLs.|
Timestamp queries can use the following field suffixes:
|Greater than or equal to the timestamp|
|Greater than the timestamp|
|Less than or equal to the timestamp|
|Less than the timestamp|
For more specific results, multiple filters can be chained together:
This example would return any Object with a slug ‘titanic’ that was published on or after the specified date
If any filter field does not match the Object queried, a 400 Bad Request error is returned showing which field can not be found.
As well as structured filtering, many Skylark objects also support filtering using free-text search by adding the lucene_query parameter to the request containing a search query in Lucene syntax. The fields covered by the search index are dependent on the Skylark configuration.
/?lucene_query=(title:titanic OR synopsis:titanic)
If the complexity of a lucene query is not required, comma-separated search terms can be used with the query parameter e.g.
If a field does not exist or is not indexed this will just return an empty result list. The fields covered by this feature are dependent on the Skylark configuration.
Free text search can be combined with other filters, though care needs to be taken with performance. End-user facing search features should prefer the Multi-search API, which can search over multiple resource types, track popular searches, and provide spelling corrections.