Veritone Search API includes rich, full-text search features to query against an organization’s public and private media indexes. The search function is highly customizable includes core functions that support parsing, aggregation, and auto-completion. Searches are performed using a variety of supported query types, expressed in JSON. Most search operations make use of optional query configurations that allow you to control the search behavior and narrow results by defining aspects of the content and values.
Veritone API is built around the GraphQL paradigm to provide a more efficient way to deliver data with greater flexibility than a traditional REST approach. GraphQL is a query language that operates over a single endpoint using conventional HTTP requests and returning JSON responses. The structure not only lets you call multiple nested resources in a single query, it also allows you to define requests so that the query you send matches the data you receive.
To make effective use of the Search API, you’ll need to know a few things about how data is stored in Veritone, the various options for structuring queries, and requirements for performing successful requests. This quickstart guide provides everything you need to help get your integration up and running as quickly as possible. We designed this quickstart to be user-friendly and example-filled, but if you have any questions, please don’t hesitate to reach out to our Developer Support Team for help.
Veritone uses a single endpoint for accessing the API. All calls to the API are POST requests and are served over http with application/json encoded bodies. The base URL varies based on the geographic region where the services will run. When configuring your integration, choose the base URL that supports your geographic location from the list below.
| Region | Base URL |
| United States | [https://api.veritone.com/v3/graphql](https://api.veritone.com/v3/graphql) |
| Europe | [https://api.uk.veritone.com/v3/graphql](https://api.uk.veritone.com/v3/graphql) |
Note: The above base URLs are provided for use within SaaS environments. On-prem deployments access the API using an endpoint that's custom configured to the environment.
To make it easier to explore, write, and test the API, we set up GraphiQL — an interactive playground that gives you a code editor with autocomplete, validation, and syntax error highlighting features. Use the GraphiQL interface to construct and execute queries, experiment with different schema modifications, and browse documentation. In addition, GraphiQL bakes authorization right into the schema and automatically passes the Authentication header with a valid token when you’re logged into the Veritone system.
Veritone’s GraphiQL interface is the recommended method for ad hoc API requests, but calls can be made using any HTTP client. All requests must be HTTP POST to the base URL for your geographic region with the query parameter and application/json encoded bodies. In addition, requests must be authenticated using an API Token. Pass the token in your request using the Authorization header with a value Bearer token. If you’re using a raw HTTP client, the query body contents must be sent in a string with all quotes escaped.
Veritone Job API uses bearer token authentication for requests. To authenticate your calls, provide a valid API Token in the Authentication header of the request with the value Bearer token. Requests made without this header or with an invalid token will return an error code.
An API Token can be generated in the Veritone Admin App by your organization administrator. If your organization does not use the Admin App, please contact your Veritone Account Manager for assistance.
To generate an API Token:
- Log into the Veritone Platform and select Admin from the App Picker drop-down. The Admin App opens.
- Click the API Keys tile. The API Key page opens.
- Click New API Key. The New API Key window opens.
- Enter a token name and select the permissions needed for the token to perform the required API tasks. Click Generate Token to save. The Token Generated window opens.
- Copy your token and click Close when finished.
Note: Once the Token Generated window closes, the token code no longer displays and it cannot be viewed again.
Search operations return results in order of relevance — the result that’s most relevant to the search query is the first item in the result set, and the least relevant is last. Relevance scoring is based on three primary factors:
- Term Frequency: How often does the term appear in the field? The more often, the more relevant. A field containing five instances of the same term is more likely to be relevant than a field containing just one mention.
- Inverse Index Frequency: How often does each term appear in the index? The more often, the less relevant. Terms that appear in many records have a lower weight than more-uncommon terms.
- Field Length: How long is the field? The longer it is, the less likely it is that words in the field will be relevant. A term appearing in a field with a short title carries more weight than the same term appearing in a long content field.
Veritone Search API gives you the flexibility to build a variety of query types to search and retrieve indexed media and mentions content. The Search API allows you to combine a series of simple elements together to construct queries as simple or as complex as you’d like in JSON format. Although queries are customizable, there is a common structure and set of core parameters that each must use. In addition, there are a number of optional filters, components, and syntax options that can be specified to modify a query.
Searches in Veritone are performed against two types of content: media and mentions. Each request must specify one of the following search content types as the root operation of the request.
- Search Media: The Search Media operation searches media files and assets for matching records.
- Search Mentions: The Search Mentions operation searches for matching records in mentions and watchlists.
Regardless of the level of complexity, each search query in Veritone operates on four core elements: an index, a field, an operator, and an operator value or variable(s).
All search functionality runs against Veritone’s public and private index databases. The index field defines whether to search the organization’s public or private index (or both) for matching documents. There are two possible index values: "global," which refers to the public media index, and "mine", which refers to private media uploaded to an account. Each request must specify at least one index value enclosed in brackets.
Content in Veritone is made searchable by mapping to specific document and data types. The field parameter defines the type of data/document to be searched, and each query must specify a value for the field property to be successful. If a field value is not provided, an empty result set will be returned. The field parameter uses a definitive set of values. See Appendix 1: Fields for more information.
Operators are the heart of the query — they describe the type of search that will be performed. Each operator uses one or more additional properties that add greater definition to the query criteria. All queries must specify at least one operator.
The table below provides an overview of the different operators that can be used. Additional information about each of the operators is provided in the section on Query Schema and Types.
| range | Finds matching items within a specified date/time range. |
| term | Finds an exact match for a word or phrase. |
| terms | Finds exact matches for multiple words or phrases. |
| query_string | Searches plain text strings composed of terms, phrases, and Boolean logic. |
| word_proximity | Finds exact matches for words that are not located next to one another. |
| exists | Checks for the presence of a specified engine output data type. |
| and | Finds records for matching values when all of the conditions are true. |
| or | Finds matching records when at least one of the conditions is true. |
| query_object | Searches for an array of objects with a common field. |
To apply two or more Booleans to a single field, group multiple terms or clauses together with parenthesis.
Below is an example of a search for Kobe or Bryant and basketball or Lakers.
value: "(kobe OR bryant) AND (basketball OR lakers)"
Veritone Search API supports escaping special characters in a query string to ensure they aren’t interpreted by the query parser. If any of the following special characters have been enabled, use a double backslash before the character to search for it.
Special characters: + - ! ( ) { } [ ] ^ " ~ * ? : \
In the example below, the ! is escaped since it’s part of the company name "ideaDes!gns".
value: "ideaDes\\!gns"
Use a single backslash to escape quotes around a phrase in a query string. The example below escapes the double quotes around "Kobe Bryant" to ensure they’re interpreted literally and not as string closers.
value: "\"kobe bryant\" AND (basketball OR lakers)"
Veritone Search API accepts a variety of query types, features, and options that make it easy to build queries as simple or complex as you’d like.
Queries can be constructed in multiple ways to search terms, phrases, ranges of time, and more. In addition, the Search API supports query modifiers (such as Wildcards and Select Statements) to provide an even broader range of searching options.
A schema is created by supplying a Search Media or Search Mentions content type as the root operation and then providing a query object with an operator, index, field, and a list of other properties that describe the data you want to retrieve. All search requests specify JSON data as the response field.
query{ => The base query parameter used to set up the GraphQL query object. (required)
-------request fields-----------
searchMedia(search:{ => The content type to be searched and search variable. (required)
index: array => Specifies whether to search the public ("global") or private (“mine) index. (required)
query: object => The query object that defines the pipeline for the data to be returned. (required)
field: string => The data or document type to be searched. (required)
operator: string => The type of search to be performed. Common types include term, range, and query_string. (required)
value: string => The exact data to be searched for in a field. (required)
offset: integer => The zero-based index of the first record to show in the response. (optional)
limit: integer => The maximum number of results to return. (optional)
}){
-------return fields------------
jsondata: => A JSON object with response data. Each search request must specify jsondata as the return field. (required)
}
}Veritone supports several types of queries, which are identified by the operator field. Queries are organized in a hierarchical structure and use nested fields in curvy brackets. The schema uses the query parameter as a wrapper around a subquery that contains an operator, field, and a value or variables. The various query types allow you to customize the search — available options are described below.
The term/terms operators are used to find exact matches of keywords or phrases. A term/terms query can match text, numbers, and dates. Searches produce a list of records that contain the keywords or phrases, no matter where they appear in the text.
Important Notes:
-
Enclose single keywords and phrases in quotation marks (e.g., "basketball", “Mike Jones”). -
A phrase includes two or more words together, separated by a space (e.g., "free throw line"). The order of the terms in a phrase is respected. Only instances where the words appear in the same order as the input value are returned.
Search by Term
The term operator is used to find an exact match for a single keyword or phrase.
The following example shows a term search against the global index to find media files where the word "Mike" appears in the program name.
query: {
operator: "term"
field: "programName"
value: "mike"
}
}
Search by Terms
The terms operator allows you to search for multiple keywords or phrases. Search terms can include any string of words or phrases separated by commas. When submitting multiple search terms, search uses a default OR behavior and will return results that contain an exact match of any of the words/phrases.
Important Note: When building a terms query, note that the terms operator and the values property are written in plural form.
The example below is a terms search query for the words "football" and “touchdown” found in transcript text in the user’s private media index.
query: {
operator: "terms"
field: "transcript.transcript"
values: ["football", "touchdown"]
}
The range operator can be used to find content that falls into a specified time frame. This query supports the following types of ranges:
-
**Inclusive Range:** Uses a combination of comparison property filters to find matching content between a specific starting and ending date. -
**Open-Ended Range:** Uses a single comparison property filter to search before or after a specific point in time.
A range query must include at least one comparison property and specify the date as the value (using Unix/Epoch Timestamp format in milliseconds and UTC time zone).
Comparison Properties
| gt | greater than: Searches for documents created after the specified date/time. |
| lt | less than: Searches for documents created before the specified date/time. |
| gte | greater than or equal to: Searches for documents created on or after the specified date/time. |
| lte | less than or equal to: Searches for documents created on or before the specified date/time. |
Inclusive Date Range
To search for records created between specified dates, use two of the comparison property options to define the to and from dates.
The following example is a search against the public index for the 10 most recent media files timestamped on or after 1/26/2017, 5:54:00 AM, and before 6/23/2017, 6:30:00 AM.
query: {
operator: "range"
field: "absoluteStartTimeMs"
gte: 1485417954000
lt: 1498199400000
}
}
Open-Ended Date Range
To search with an open-ended range (e.g., find files before a specified date), use just one of the comparison property options.
The example below shows a search for the 30 most recent media files in the public index timestamped after 3/15/2017 at 6:30:00 AM.
query: {
operator: "range"
field: "absoluteStartTimeMs"
lt: 1485417954000
}
The query_string operator performs full-text searches and constructs queries as text strings using terms, phrases, and Boolean logic. The biggest advantage of the query string is its syntax that parses multiple structured queries into simpler ones.
Important Notes:
-
The query string supports more complex query constructs, such as wildcard searches. -
Multiple query statements that are not joined by the *and* operator will return results that match any of the conditions. -
Date and time values are not supported in a query string.
The below example will return results transcripts where "Kobe Bryant" or “Lakers” was found.
query: {
operator: "query_string"
field: "transcript.transcript"
value: "\"kobe bryant\" lakers"
}
Using AND/OR in a Query String
You can specify a broader or more narrow search by using the AND and OR operators between values in a query string. When using AND/OR within a quoted string, they are treated as part of the field value (not the main query operator) and must be written in all uppercase. In addition, multiple terms in a query string can be grouped together using parenthesis to make the logic clear. Note that terms in parentheses are processed first.
The following example is a search for transcripts where "Kobe Bryant" was found with either the word “basketball” or the word “Lakers.”
query: {
operator: "query_string"
field: "transcript.transcript"
value: "\"kobe bryant\" AND (basketball OR lakers)"
}
While the terms query searches for specified terms in the exact order as the input value, a word proximity search allows the words to be separated or to appear in a different order. The word proximity operator uses the inOrder property as a Boolean to find terms where they do not appear together, and the distance property to specify the maximum number of words that can separate them.
Word Proximity Properties
| inOrder | yes | Boolean | A Boolean that when set to false searches for all of the words in an order different than the input value. Note that if the distance property has a value of 0, inOrder will be set to true. | inOrder: false |
| distance | yes | integer | The number of non-search words that can separate the specified terms to be found. To match words in the same order as the input value, use a distance value of 0. (Note that a 0 value sets inOrder to true.) To transpose two words, enter a value of 1. | distance: 10 |
The following query finds the terms "NFL," “football,” and “game” in transcript text when they appear within 10 words of one another in any order.
query: {
operator: "word_proximity"
field: "transcript.transcript"
values: ["nfl football game"]
inOrder: false
distance: 10
}
The exists operator is used to check for the presence of a specific field. This query is useful for retrieving matching media files of a specific data type. If the specified field is not found, the operator will consider it non-existent and it will return no results.
The example below is a search for media files with the field "veritone-file.mimetype".
query: {
operator: "exists"
name: "veritone-file.mimetype"
}
The and and or operators allow you to combine two or more query clauses with Boolean logic to create broader or more narrow search results. These operators chain conditional statements together and always evaluate to true or false. As main query operators, and/or are case insensitive and can be written as uppercase or lowercase. It’s important to note that when using these operators in compound queries, and takes precedence over or.
and Operator
The and operator matches documents where both terms exist anywhere in the text of a single record.
The search below returns results for "Morning Show AM" mentions found on November 11, 2017.
query: {
operator: "and",
conditions: [
{
operator: "term"
field: "trackingUnitName"
value: "Morning Show AM"
},
{
operator: "term"
field: "mentionDate"
value: "2017-11-09"
}
]
}
or Operator
The or operator connects two conditions and returns results if either condition is true.
The example below shows a search for the name "Bob" or “Joe” or “Sue” in a transcript or records that created on or after November 17, 2017 at 9:00 AM.
query: {
operator: "or",
conditions: [
{
operator: "terms",
field: "transcript.transcript"
values: ["bob", "joe", "sue"]
},
{
operator: "range",
field: "absoluteStartTimeMs"
gte: 1510909200000
}
]
}
Combining and & or
The and and or (and not) operators can be combined as multi-level subqueries to create a compound condition. When these operators are used together, it’s important to note that not is evaluated first, then and, and finally or.
The example below is a search for records found between November 17, 2017 at 9:00 AM and December 1, 2017 at noon where the word "basketball" or “Lakers” was found in a transcript, or the NBA logo was detected.
operator: "and",
conditions: [
{
operator: "range"
field: "absoluteStartTimeMs,
gte: 1510909200000
lte: 1512129600000
},
{
operator: "or"
conditions: [
{
operator: "query_string"
field: "transcript.transcript"
value: ["basketball", "lakers"]
}
operator: "term"
field: "logo-recognition.series.found"
value: "NBA"
}
]
}
]
}
The query_object operator allows an array of objects to be queried independently of one another. Each query_object uses a Boolean operator (e.g., and, or, not) to combine a list of nested subqueries. Nested subqueries can use any operator type.
The below example is a search for an ESPN logo or the words "touchdown" and “ruled” or “college” in a transcript on or before December 11, 2017 at 9:11 PM.
operator: "query_object"
query:{
operator: "or"
conditions: [{
operator: "range"
field: "absoluteStartTimeMs"
lte: 1513026660000
},
{
operator: "term"
field: "logo-recognition.series.found"
value: "ESPN"
},
{
operator: "query_string"
field: "transcript.transcript"
value: "touchdown AND (ruled OR college)"
}
]
}
A not modifier returns search results that do not include the specified values. Any of the query operators can be negated by adding the property not with a value of true. Note that negation is currently unsupported at the compound operator level.
The below example is a search that excludes the terms "NFL," “football,” and “game.”
query: {
operator: "terms"
field: "transcript.transcript"
values: ["nfl", "football", "game"]
not: true
distance: 10
}
The wildcard modifier is useful when you want to search various forms of a word. Wildcard searches can be run on individual terms, using ? to replace a single character, and * to replace zero or more characters. For example, he* returns results that would include her, help, hello, helicopter and any other words that begin with "he". Searching he? will only match three-letter words that start with “he”, such as hem, hen, and her.
Important Notes:
-
There can be more than one wildcard in a single search term or phrase, and the two wildcard characters can be used in combination. (e.g., j*?? will match words with three or more characters that start with the letter j.) -
Wildcard matching is only supported within single terms and not within phrase queries. (e.g., m*th* will match "method" but not “meet there”.) -
A wildcard symbol cannot be used as the first character of a search.
A select query modifier lets you retrieve only the data that you want. It also allows you to combine data from multiple field property sources. Submitting a request with the select parameter returns full record matches for all of the specified values. To use the select filter, enter a comma-separated list of field names to return.
The example below is a search for records where "Kobe Bryant" along with either the word “basketball” or the word “Lakers” is found in either a transcript or a file uploaded to Veritone CMS.
query: {
operator: "query_string"
field: "transcript.transcript"
value: "\"kobe bryant\" AND (basketball OR lakers)"
},
select: ["transcript.transcript", "veritone-file"]
}
Veritone’s GraphiQL interface is a service you can use to easily interact with the Search API. We recommend using GraphiQL (https://api.veritone.com/v3/graphiql) for making test API requests, but calls can also be made using a different HTTP client. All requests must be HTTP POST to the Veritone GraphQL endpoint with the query parameter and application/json encoded bodies. In addition, requests must be authenticated with an API Token. Pass the token in your request using the Authorization header with a value Bearer . If you’re using a raw HTTP client, the query body contents must be sent in a string (not an object) with all quotes escaped.
Following are a variety of example queries that demonstrate how to put everything together. The sample requests provided are structured for use in our GraphiQL interface, but we’ve also included the basic cURL structure for your reference below. Please note that the examples shown do not use client information and are not language specific. For fields that require account-specific data (such as a Recording ID), replace the value with your own.
curl -X POST \
https://api.veritone.com/v3/graphql \
-H 'authorization: Bearer 2079b07c-1a6f-4c2e-b534-a1aaa7f7fe42' \
-H 'content-type: application/json' \
-d '{
"query": " query { searchMedia(search: { offset: 0, limit: 2, index: [\"global\"], query: { operator: \"term\", field: \"programName\", value: \"basketball\" }}) { jsondata } }"
}'The following example is a media search of both indexes where NBA was recognized as text and the words "Kobe Bryant" and “basketball” or “Lakers” was found in a transcript. This request also includes a select statement that limits the search to transcripts and Veritone files.
query{
searchMedia(search:{
offset: 0
limit: 1
index: ["mine"]
operator: "query_object"
query:{
operator: "or"
conditions: [{
operator: "range"
field: "absoluteStartTimeMs"
lt: 1485417954000
},
{
operator: "term"
field: "text-recognition.series.ocrtext"
value: "nba"
},
{
operator: "query_string"
field: "transcript.transcript"
value: "\"kobe bryant\" AND (basketball OR lakers)"
}
]
}
}) {
jsondata
}
}{
"data": {
"searchMedia": {
"jsondata": {
"results": [
{
"recording": {
"recordingId": "16322767",
"fileLocation": "https://inspirent.s3.amazonaws.com/assets/16322767/b8936c78-2186-72e5-93af-5c5aa13dd982.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171215%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171215T155327Z&X-Amz-Expires=604800&X-Amz-Signature=49a0bec006693905a66cfb0972167170b14947e05c66dbcf98ed705f31726a03&X-Amz-SignedHeaders=host",
"fileType": "video/mp4",
"programId": "-1",
"programName": "Private Media",
"mediaSourceId": "-1",
"mediaSourceTypeId": "5",
"tags": [
{
"value": "TEDx",
"displayName": "TEDx"
},
{
"value": "Tolo West",
"displayName": "Tolo West"
}
],
"sliceTime": 1484780795,
"mediaStartTime": 1484780045,
"aibDuration": 810,
"isOwn": true,
"hitStartTime": 1484780795,
"hitEndTime": 1484780855
},
"startDateTime": 1484780795,
"stopDateTime": 1484780855,
"hits": []
}
],
"totalResults": 728274,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "171a1b10-e9c0-11e7-bae7-61a10650068b",
"timestamp": 1513353207
}
}
}
}The example below is a media search against the private index for records with a filename.
query{
searchMedia(search:{
offset: 0
limit: 1
index: ["mine"]
query:{
operator: "exists"
name: "veritone-file.filename"
}
}) {
jsondata
}
}{
"data": {
"searchMedia": {
"jsondata": {
"results": [
{
"recording": {
"recordingId": "43033727",
"fileLocation": "https://inspirent.s3.amazonaws.com/assets/43033727/ea9d9845-775b-48cd-aada-16fa56894ba0.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171215%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171215T181255Z&X-Amz-Expires=604800&X-Amz-Signature=2fd918d5ac20979bd27d365bfa455904cf1726307fddbd362a28a8bd9a0a81a8&X-Amz-SignedHeaders=host",
"fileType": "video/mp4",
"programId": "-1",
"programName": "Weekly Talkshow",
"programLiveImage": "https://inspirent.s3.amazonaws.com/assets/43033727/fe693b30-18ae-47c7-984f-530eab61d7.jpeg",
"mediaSourceId": "-1",
"mediaSourceTypeId": "5",
"sliceTime": 1512682022,
"mediaStartTime": 1512681992,
"aibDuration": 90,
"isOwn": true,
"hitStartTime": 1512682022,
"hitEndTime": 1512682082
},
"startDateTime": 1512682022,
"stopDateTime": 1512682082,
"hits": [
{
"veritone-file": {
"filename": "Veritone_v06.mp4",
"mimetype": "video/mp4",
"size": 162533502
}
}
]
}
],
"totalResults": 733275,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "930f0960-e1c3-11e7-9e94-eba5f6b5faf7",
"timestamp": 1513361576
}
}
}
}The example below is a media search of the public index for Coke or Pepsi logos but not Redbull.
query{
searchMedia(search:{
offset: 0
limit: 1
index: ["global"]
query:{
operator: "or"
conditions: [{
operator: "term"
field: "logo-recognition.series.found"
value: "Coke"
},
{
operator: "term"
field: "logo-recognition.series.found"
value: "Pepsi"
},
{
operator: "term"
field: "logo-recognition.series.found"
value: "Redbull"
not: true
}]
}
}) {
jsondata
}
}{
"data": {
"searchMedia": {
"jsondata": {
"results": [
{
"recording": {
"recordingId": "43842334",
"fileLocation": "https://inspirent.s3.amazonaws.com/tv-recordings/vv-stream/39898/2017/12/14/processed/39898_20171214_0720_263a786f-3d59-4572-9752-984ded917573.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171214%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171214T211125Z&X-Amz-Expires=604800&X-Amz-Signature=af6b9acc5b113949fb3d01ec3464c14e10449bd0bd51d250bdd906504588caa2&X-Amz-SignedHeaders=host",
"fileType": "video/mp4",
"programId": "27405",
"programName": "Prime Time",
"programImage": "https://s3.amazonaws.com/prod-veritone-ugc/programs/27405/3tWiUgZNS42vWB55dED3_GRftjRV6_400x400.jpg",
"mediaSourceId": "37802",
"mediaSourceTypeId": "2",
"isPublic": true,
"sliceTime": 1513236060,
"mediaStartTime": 1513236000,
"aibDuration": 120,
"isOwn": false,
"hitStartTime": 1513236064,
"hitEndTime": 1513236067
},
"startDateTime": 1513236060,
"stopDateTime": 1513236120,
"hits": [
{
"logo-recognition": {
"source": "bf50297a-55f1-5a27-17a1-d213ae0c7f55",
"series": [
{
"end": 67000,
"found": "Pepsi",
"salience": 0.300785630941391,
"start": 64000
}
]
}
}
]
}
],
"totalResults": 808,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "57d785e0-9213-11e7-9a71-df8e48a9af47",
"timestamp": 1513285885
}
}
}
}The example below is a media search of the public index for instances where the words emergency, broadcast, and fire are found in any order within 10 words of one another.
query{
searchMedia(search:{
offset: 0
limit: 1
index: ["global"]
query:{
operator: "word_proximity"
field: "transcript.transcript"
inOrder: false
distance: 10
values: ["emergency", "broadcast", "fire"]
}
}) {
jsondata
}
}{
"data": {
"searchMedia": {
"jsondata": {
"results": [
{
"recording": {
"recordingId": "36744245",
"fileLocation": "https://inspirent.s3.amazonaws.com/recordings/1832ec2e-7342-41e5-4396-b0d681009e21_original.mp3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171214%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171214T211646Z&X-Amz-Expires=604800&X-Amz-Signature=6865eb270e11e9cae746230ed2247a2f336edbe3e7cde199af487319facf1c43&X-Amz-SignedHeaders=host",
"fileType": "audio/mpeg",
"programId": "26372",
"programName": "Morning Drive",
"programImage": "https://s3.amazonaws.com/prod-veritone-ugc/programs/26972/y3wVqN69SreXR6FREBqQ_WINS-AM.jpg",
"programLiveImage": "https://s3.amazonaws.com/prod-veritone-ugc/programs/25072/WpH0ipIYSzKA2Brvl0DX_BczwZNdTzmfmRbA3nTJA_MwvD0M4bRr2ELAcK8uQD_wins%2525201010.JPG",
"mediaSourceId": "32063",
"mediaSourceTypeId": "1",
"isPublic": true,
"sliceTime": 1503398731,
"mediaStartTime": 1503398701,
"aibDuration": 90,
"isOwn": false,
"hitStartTime": 1503398752,
"hitEndTime": 1503398754
},
"startDateTime": 1503398731,
"stopDateTime": 1503398791,
"hits": [
{
"transcript": {
"source": "temporal",
"transcript": [
{
"hits": [
{
"queryTerm": "broadcast",
"startTime": 51.829,
"endTime": 52.51
},
{
"queryTerm": "fire",
"startTime": 52.579,
"endTime": 52.949
},
{
"queryTerm": "emergency",
"startTime": 53.44,
"endTime": 53.989
}
],
"startTime": 43.01,
"endTime": 72.479,
"text": "seriously in a train crash in suburban Philadelphia early today a SEPTA commuter train struck an unoccupied parked train at a terminal in Upper Darby broadcast a fire recorded the emergency call Act of one market Acura one market town on her you know . Her and want to honor him by the N.T.S.B. is trying to determine the cause we have mostly clear skies but some low clouds a little bit a haze around seventy five degrees heading for ninety"
}
]
}
}
]
}
],
"totalResults": 95,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "17334140-e374-11e7-b0e6-a586c4474dec",
"timestamp": 1513286206
}
}
}
}The example below is a media search of the private index for the word Paris when it does not appear with Las Vegas.
query{
searchMedia(search:{
offset: 0
limit: 1
index: ["mine"]
query:{
operator: "query_string"
field: "transcript.transcript"
value: "paris NOT \"las vegas\""
}
}) {
jsondata
}
}{
"data": {
"searchMedia": {
"jsondata": {
"results": [
{
"recording": {
"recordingId": "36397022",
"fileLocation": "https://inspirent.s3.amazonaws.com/assets/36397022/17996ce6-1d2e-43c7-9398-d6f359f56d96.mp3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171214%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171214T212013Z&X-Amz-Expires=604800&X-Amz-Signature=b7459f5c243c4c6a28a803b083c27265a605fd2d3426ba47f945a423fef6839c&X-Amz-SignedHeaders=host",
"fileType": "audio/mp3",
"programId": "-1",
"programName": "Morning Chat",
"programLiveImage": "https://s3.amazonaws.com/veritone-ugc/temp%2FprogramLiveImageURL%2F74DgqpH2RMyu2i5MtSb5_Test(1).png",
"mediaSourceId": "-1",
"mediaSourceTypeId": "5",
"sliceTime": 1501005830,
"mediaStartTime": 1501005380,
"aibDuration": 510,
"isOwn": true,
"hitStartTime": 1501005841,
"hitEndTime": 1501005842
},
"startDateTime": 1501005830,
"stopDateTime": 1501005890,
"hits": [
{
"transcript": {
"source": "temporal",
"transcript": [
{
"hits": [
{
"queryTerm": "Paris",
"startTime": 461.869,
"endTime": 462.159
}
],
"startTime": 461.869,
"endTime": 491.61,
"text": "Paris Jackson is in the upside Wow Wow That's great Naomi star airs Tuesdays on Fox and you can follow her on Twitter at Naomi Campbell thank you so much for calling in Naomi thank you SO MUCH THANK YOU HAVE A GREAT DAY AND . The first say fifty percent . At Macy's It feels good to give back together with the help generosity of our customers and employees we gave back fifty two million dollars to charities nationwide last year"
}
]
}
}
]
}
],
"totalResults": 18071,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "92ab8800-7a14-11e7-8c04-bd019caca41d",
"timestamp": 1513286413
}
}
}
}The following example is a media search of both indexes for either of two faces and a 20th Century Fox logo or an occurrence of Fox Sports found in text.
query{
searchMedia(search:{
offset: 0
limit: 1
index: ["global", "mine"]
query:{
operator: "or"
conditions: [{
operator: "terms"
field: "face-recognition.series.entityId"
values: ["3513c7da-3cde-4444-888e-ddd73e6d0cd9", "f34245b0-096b-4c3d-9646-6271d7d260d1"]
}
{
operator: "or"
conditions: [{
operator: "term"
field: "logo-recognition.series.found"
value: "20th Century Fox"
},
{
operator: "term"
field: "text-recognition.series.ocrtext"
value: "fox sports"
}
]
}
]
}
}) {
jsondata
}
}{
"data": {
"searchMedia": {
"jsondata": {
"results": [
{
"recording": {
"recordingId": "43592937",
"fileLocation": "https://inspirent.s3.amazonaws.com/tv-recordings/17/12/14/6f0026ec-70a6-4ded-4a01-4c4d0ad4df75.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171214%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171214T212939Z&X-Amz-Expires=604800&X-Amz-Signature=059b209149eaf2e4111d56d2b33d0c804f40ca3789b26736db787ca9981d8f45&X-Amz-SignedHeaders=host",
"fileType": "video/mp4",
"programId": "29684",
"programName": "Weekday Afternoons",
"programImage": "https://s3.amazonaws.com/veritone-ugc/programs/25084/XbZ1Aj4JSHmrBNIuWUaW_200px-BBC_World_News_red.svg.png",
"programLiveImage": "https://s3.amazonaws.com/prod-veritone-ugc/programs/25084/qOyniPW3SrmTjVw7B1ow_4de7730beea8e20ba24de2be5ac03cb6.jpg",
"mediaSourceId": "39546",
"mediaSourceTypeId": "2",
"isPublic": true,
"sliceTime": 1513286310,
"mediaStartTime": 1513286100,
"aibDuration": 270,
"isOwn": false,
"hitStartTime": 1513286316,
"hitEndTime": 1513286317
},
"startDateTime": 1513286310,
"stopDateTime": 1513286370,
"hits": [
{
"logo-recognition": {
"source": "bf5a703a-55f1-5a27-17a1-d213ae0c7f55",
"series": [
{
"end": 217000,
"found": "20th Century Fox",
"salience": 0.5717288255691528,
"start": 216000
}
]
}
}
]
}
],
"totalResults": 4886,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "e3cc7680-e115-36e7-9e94-eba5f6b5faf7",
"timestamp": 1513286979
}
}
}
}The example below is a search for mentions with the name "Dallas Cowboys Super Bowl" and have a verification status of “Pending”.
query{
searchMentions(search:{
offset: 0
limit: 1
index: ["mine"]
query:{
operator: "and"
conditions: [{
operator: "term"
field: "trackingUnitName"
value: "Dallas Cowboys Super Bowl"
},
{
operator: "term"
field: "mentionStatusId"
value: "1"
}]
}
}) {
jsondata
}
}{
"data": {
"searchMentions": {
"jsondata": {
"results": [
{
"id": 47569938,
"programFormatName": "Information and News",
"mentionDate": "2017-01-31T07:59:18.000Z",
"mediaStartTime": "2017-01-31T07:45:01.000Z",
"mediaId": 20017455,
"metadata": {
"filename": "AM-RADIO",
"veritone-file": {
"size": 0,
"filename": "AM-RADIO",
"mimetype": "audio/mpeg"
},
"veritone-media-source": {
"mediaSourceId": "14326",
"mediaSourceTypeId": "1"
},
"veritone-program": {
"programId": "3828",
"programName": "AM-RADIO Morning Talk",
"programImage": "https://s3.amazonaws.com/veritone-ugc/cb5e59d4-a986-4e2b-b525-482319df3350%2FbrdProgram%2F2uGsLVKsQeiKN3UuHufC_941478_10151455644772706_951533539_n.jpg",
"programLiveImage": "https://s3.amazonaws.com/prod-veritone-ugc/cb5e59d4-a986-4e2b-b525-482319df3350%2FbrdProgram%2FwwEn3Ya9RgmMQwUEGoD1_LUkKlgZQS36ncUbY8Iz7_2520to%2520live2.JPG"
}
},
"fileLocation": "https://inspirent.s3.amazonaws.com/recordings/9605ea97-87df-428e-6740-720df8b8691c_original.mp3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI7L6G7PCOOOLA7MQ%2F20171215%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171215T205111Z&X-Amz-Expires=604800&X-Amz-Signature=00f62a6e2367c109320c98b9aea190cd28d82ac347eeeca030f42810b7ab75e3&X-Amz-SignedHeaders=host",
"fileType": "audio/mpeg",
"snippets": [
{
"startTime": 857.62,
"endTime": 887.33,
"text": "eighty first women's Australian Open final Monica Seles beat Steffi Graf four six six three six two in one thousand nine hundred twenty eight the Dallas Cowboys beat the Buffalo Bills thirty to thirteen in Atlanta running back Emmitt Smith wins the M.V.P. and fourth consecutive Super Bowl game loss to the Cowboys twenty sixteen at the one hundred fourth women's Australian Open final six three six six four that time capsule your",
"hits": [
{
"startTime": 865.7,
"endTime": 865.929,
"queryTerm": "Dallas"
},
{
"startTime": 865.93,
"endTime": 866.07,
"queryTerm": "Cowboys"
},
{
"startTime": 872.74,
"endTime": 873.31,
"queryTerm": "Super"
},
{
"startTime": 873.31,
"endTime": 873.43,
"queryTerm": "Bowl"
}
]
}
],
"userSnippets": null,
"advertiserId": 0,
"advertiserName": "",
"brandId": 0,
"brandImage": "",
"brandName": "",
"campaignId": 0,
"campaignName": "",
"organizationId": 7295,
"organizationName": "Demo Organization",
"trackingUnitId": 10032,
"trackingUnitName": "Dallas Cowboys Super Bowl",
"mentionStatusId": 1,
"mediaSourceTypeId": 1,
"mediaSourceTypeName": "Audio",
"mediaSourceId": 14326,
"mediaSourceName": "AM-RADIO Morning Talk",
"isNational": true,
"spotTypeId": null,
"spotTypeName": null,
"programId": 3828,
"programName": "AM-RADIO",
"programImage": "https://s3.amazonaws.com/prod-veritone-ugc/cb5e59d4-a986-4e2b-b525-482319df3350%2FbrdProgram%2F2uGsLVKsQeiKN3UuHufC_941478_10151455644772706_951533539_n.jpg",
"programLiveImage": "https://s3.amazonaws.com/veritone-ugc/cb5e52b4-a986-4e2b-b525-482319df3350%2FbrdProgram%2FwwEn3Ya9RgmMQwUEGoD1_LUkKlgZQS36ncUbY8Iz7_2520to%2520live2.JPG",
"impressions": 1894,
"audience": [
{
"gender": "men",
"age_group": "35-44",
"audience": 11,
"isTargetMatch": true
},
{
"gender": "men",
"age_group": "45-49",
"audience": 121,
"isTargetMatch": true
},
{
"gender": "men",
"age_group": "50-54",
"audience": 474,
"isTargetMatch": true
},
{
"gender": "men",
"age_group": "65+",
"audience": 95,
"isTargetMatch": true
},
{
"gender": "women",
"age_group": "50-54",
"audience": 19,
"isTargetMatch": false
},
{
"gender": "women",
"age_group": "65+",
"audience": 693,
"isTargetMatch": false
},
{
"gender": "men",
"age_group": "55-64",
"audience": 481,
"isTargetMatch": true
}
],
"targetAudience": {
"gender": 1,
"genderName": "M",
"ageGroup": [
0,
5
],
"ageGroupMin": 18,
"ageGroupMax": 0,
"impressions": 1182
},
"audienceMarketCount": 3,
"audienceAffiliateCount": 1,
"rating": null,
"ratings": null,
"comments": null,
"markets": [
{
"marketId": 54,
"marketName": "Des Moines-Ames, IA"
}
],
"marketId": null,
"marketName": null,
"hourOfDay": 7,
"dayOfWeek": 2,
"dayOfMonth": 31,
"month": 1,
"year": 2017,
"isMatch": true,
"mentionStatusName": "Pending Verification",
"complianceStatusId": null,
"cognitiveEngineResults": null,
"hits": 4
}
],
"totalResults": 579,
"limit": 1,
"from": 0,
"to": 0,
"searchToken": "ae882400-e1d9-11e7-947b-339cddca931e",
"timestamp": 1513371071
}
}
}
}The table below defines the possible values currently available for the field property. Fields are grouped by category and include a name, a type, and one or more possible values.
| Searches for various aspects of recordings in public and private indexes. | |||
| absoluteStartTimeMs | integer | Absolute start date and time in Unix/Epoch timestamp format. * Must use range operator. |
operator: "range" field: "absoluteStartTimeMs" gte: "1497808410" |
| absoluteStopTimeMs | integer | Absolute stop date and time in Unix/Epoch timestamp format. · Must use range operator. |
operator: "range" field: "absoluteStopTimeMs" gte: "1497808410" |
| recordingId | string | The unique ID associated with the recording container. | operator: "term" field: "recordingId" value: "39590300" |
| fileLocation | string | The URL of the file. | operator: "term" field: "fileLocation" value: "https://inspirent.s3.amazonaws.com/assets/39070300/789eb7b2-6c4d-4ec4-8a79-f4600b7e31c1.mp4" |
| fileType | string | The recording file MIME type. · Value must be entered as lowercase. |
operator: "term" field: "fileType" value: "video/mp4" |
| relativeStartTimeMs | integer | The starting time of the recording in milliseconds. · Must use range operator. |
operator: "range" field: "relativeStartTimeMs" lte: "1497808410" |
| relativeStopTimeMs | integer | The ending time of the recording in milliseconds. · Must use range operator. |
operator: "range" field: "relativeStopTimeMs" lte: "1497808410" |
| isPublic | Boolean | A Boolean that searches the public index when set to true. | operator: "term" field: "isPublic" value: true |
| programName | string | The user-entered name of the program. · Must use query_string operator and the value must be entered as lowercase. |
operator: "query_string" field: "programName" value: "this week in tech" |
| mediaSourceId | string | A UUID assigned by the system that identifies the media ingestion source. | operator: "term" field: "mediaSourceId" value: "39262" |
| mediaSourceTypeId | string | The ID associated with the media source type. | operator: "term" field: "mediaSourceTypeId" value: "4" |
| Searches for various aspects of mentions and watchlists in an organization’s private media index. | |||
| id | string | The unique ID associated with the mention. | operator: "term" field: "id" value: "40392711" |
| programFormatName | string | The radio format name as defined by Wikipedia/Radio\_Format. | operator: "term" field: "programFormatName" value: "Sport" |
| mentionDate | type: date format: date_ optional\_time | The date and time the mention was created. · The date is mandatory and the time is optional. · UTC time zone. · Date format: "yyyy-mm-dd" · The time element "T" must follow the date. · Time format: hh/mm/ss/ms |
operator: "range" field: "mentionDate" gte: "2017-04-13T20:09:09.000" |
| mediaStartTime | type: date format: date_ optional_time | The radio/TV broadcast time of the media. · The date is mandatory and the time is optional. · UTC time zone. · Date format: "yyyy-mm-dd" · The time element "T" must follow the date when adding a time to the value. · Time format: hh/mm/ss/ms · Uses the term or range operator. |
operator: "range" field: "mediaStartTime" gte: "2017-04-13T20:09:09.000" operator: "term" field: "mediaStartTime" value: "2017-04-13T20:09:09.000" |
| mediaSourceId | string | The ID of the media source. | operator: "term" field: "mediaSourceId" value: "12734" |
| mediaSourceName | string | The name of the media source. | operator: "term" field: "mediaSourceName" value: "WPDH-FM" |
| mediaSourceTypeId | integer | The ID of the media source type. Possible values: "1" (Broadcast Radio) "2" (Broadcast TV) "3" (YouTube) "4" (Podcast) "5" (Private Media) |
operator: "term" field: "mediaSourceTypeId" value: "2" |
| metadata.veritone-program.primaryMediaSourceId | string | The primary media source ID metadata. Uses the term or range operator. | operator: "term" field: "metadata.veritone-program.primaryMediaSourceId" value: "21296" |
| metadata.veritone-program.programId | string | The program ID metadata. | operator: "term" field: "metadata.veritone-program.programId" value: "28224" |
| metadata.veritone-program.programName | string | The program name metadata. | operator: "term" field: "metadata.veritone-program.programName" value: "AM Afternoon News 4p6p" |
| veritone-cognitive-profile-params | object | The search query parameters used to generate the mention. | operator: "term" field: "veritone-cognitive-profile-params" value: "hello" |
| isNational | Boolean | A Boolean that when set to true searches for programs that are national. | operator: "term" field: "isNational" value: false |
| audience.gender | string | The gender of the segment. Possible values: "men" "women" |
operator: "term" field: "audience.gender" value: "men" |
| audience.age_group | string | The age group string for the segment. Possible values: "6-11" "12-17" "18-24" "25-34" "35-44" "45-49" "50-54" "55-64" "65+" |
operator: "term" field: "audience.age_group" value: "45-49" |
| audience.audience | integer | The number of impressions for the segment. | operator: "range" field: "audience.audience" gt: "1100" |
| audience.isTargetMatch | Boolean | Specifies whether the audience segment matches (true) or doesn’t match (false) the target audience. | operator: "term" field: "audience.isTargetMatch" value: true |
| targetAudience.gender | integer | The target audience gender. Possible values: "1" (men) "2" (women) "3" (people) |
operator: "term" field: "targetAudience.gender" value: "3" |
| targetAudience.genderName | string | The gender code of the target audience. Possible values are as follows and must be capitalized: "M" (male) "F" (female) "P" (people) |
operator: "term" field: "targetAudience.genderName" value: "F" |
| targetAudience.ageGroup | integer | The target audience age group range. Enter one or more of the possible values to search a target audience age group. Possible values: "0" (18-24) "1" (25-34) "2" (35-44) "3" (45-54) "4" (55-64) "5" (65+) |
operator: "terms" field: "targetAudience.ageGroup" values: ["2", "4"] |
| targetAudience.ageGroupMin | integer | The lower bound of the target age group. | operator: "term" field: "targetAudience.ageGroupMin" value: "25" |
| targetAudience.ageGroupMax | integer | The upper bound of the target age group. | operator: "term" field: "targetAudience.ageGroupMax" value: "54" |
| targetAudience.impressions | integer | The total number of impressions in the target audience. | operator: "range" field: "targetAudience.impressions" gt: "15000" |
| metadata.veritone-file.filename | string | The name associated with the media file. | operator: "term" field: "metadata.veritone-file.filename" value: "AM Afternoon News18" |
| metadata.veritone-file.mimetype | string | The file type metadata. | operator: "term" field: "metadata.veritone-file.mimetype" value: "audio/mpeg" |
| metadata.veritone-file.size | integer | The file size metadata. Uses term or range operator. | operator: "range" field: "metadata.veritone-file.size" gte: "2000" |
| metadata.veritone-media-source.mediaSourceId | string | The media source ID metadata. | operator: "term" field: "metadata.veritone-media-source.mediaSourceId" value: "16390" |
| metadata.veritone-media-source.mediaSourceName | string | The media source name. | operator: "term" field: "metadata.veritone-media-source.mediaSourceName" value: "Morning Drive" |
| metadata.veritone-media-source.mediaSourceTypeId | integer | The identifier of the media source type. Possible values: "1" (Broadcast Radio) "2" (Broadcast TV) "3" (YouTube) "4" (Podcast) "5" (Private Media) |
operator: "term" field: "metadata.veritone-media-source.mediaSourceTypeId" value: "1" |
| fileType | string | The file type of the mention. | operator: "term" field: "fileType" value: "audio/mpeg" |
| snippets.hits.startTime | integer | The start time of the snippet hit. · Uses term or range operator. |
operator: "term" field: "snippets.hits.startTime" value: "824.73" |
| snippets.hits.endTime | integer | The ending time of the snippet hit. · Uses term or range operator. |
operator: "term" field: "snippets.hits.endTime" value: "869.95" |
| snippets.hits.queryTerm | string | A word to search for in the text of the mention hit. · Value must be all lowercase. |
operator: "term" field: "snippets.hits.queryTerm" value: "nfl" |
| snippets.startTime | integer | The starting time of the snippet. · Uses term or range operator. |
operator: "term" field: "snippets.startTime" value: "819.839" |
| snippets endTime | integer | The ending time of the snippet. · Uses term or range operator. |
operator: "term" field: "snippets.endTime" value: "840.16" |
| snippets.text | string | One or more words from the snippet text. · Value must be all lowercase. · Uses query_string or term operator. |
operator: "query_string" field: "snippets.text" value: "team will go on to victory" operator: "term" field: "snippets.text" value: "team" |
| userSnippets.startTime | integer | The start time of the user-edited mention text. · Uses term or range operator. |
operator: "term" field: " userSnippets startTime" value: "78" operator: "range" field: " userSnippets startTime" gte: "78" |
| userSnippets.endTime | integer | The end time of the user-edited mention text. · Uses term or range operator. |
operator: "term" field: "userSnippets endTime" value: "78" operator: "range" field: "userSnippets endTime" lte: "179" |
| userSnippets.snippets.text | string | The user-edited mention text. · Value must be all lowercase. |
operator: "query_string" field: "userSnippets.snippets.text" value: "team will" operator: "term" field: " userSnippets.snippets.text" value: "team" |
| organizationId | string | The unique ID associated with the organization. | operator: "term" field: "organizationId" value: "7685" |
| organizationName | string | The name of the organization. | operator: "term" field: "organizationName" value: "ABC Organization" |
| trackingUnitId | string | The unique ID of the mention. · Uses term or range operator. |
operator: "term" field: "trackingUnitId" value: "20068" |
| trackingUnitName | string | The user-entered name of the mention. Values for this field are case sensitive and must be entered as they are saved in the index. | operator: "term" field: "trackingUnitName" value: "Dallas Cowboys Super Bowl" |
| mentionStatusId | integer | The status of the mention’s verification. Possible values: "1" (Pending Verification) "2" (Verified) "3" (Needs Review) "4" (Request Bonus) "5" (Invalid) "6" (Processing Verification) "7" (Auto Verified) |
operator: "term" field: "mentionStatusId" value: "2" |
| mediaSourceTypeId | integer | The media source type identifier. Possible values: "1" (Broadcast Radio) "2" (Broadcast TV) "3" (YouTube) "4" (Podcast) "5" (Private Media) |
operator: "term" field: "mediaSourceTypeId" value: "2" |
| mediaSourceTypeName | string | The media source name. Possible values: "Audio" "Broadcast TV" "Podcast" "YouTube" "Private Media" |
operator: "term" field: "mediaSourceTypeName" value: "Audio" |
| mediaSourceId | string | The ID of the media source. · Uses term or range operator. |
operator: "term" field: "mediaSourceId" value: "38674" |
| mediaSourceName | string | The user-defined program name. | operator: "term" field: "mediaSourceName" value: "The Weekly Podcast" |
| spotTypeId | integer | The ID of the spot type: Possible values: "17" (Bonus) "15" (Live :05) "16" (Live :10) "1" (Live :15) "2" (Live :30) "3" (Live :60) "14" (MicroMention) "9" (Non Voiced :05) "10" (Non Voiced :10) "11" (Non Voiced :15) "12" (Non Voiced :30) "13" (Non Voiced :60) "4" (Voiced :05) "5" (Voiced :10) "6" (Voiced :15) "7" (Voiced :30) "8" (Voiced :60) |
operator: "term" field: "spotTypeId" value: "17" |
| spotTypeName | string | The name of the spot type. Possible values: "Bonus" "Live :05" "Live :10" "Live :15" "Live :30" "Live :60" "MicroMention" "Non Voiced :05" "Non Voiced :10" "Non Voiced :15" "Non Voiced :30" "Non Voiced :60" "Voiced :05" "Voiced :10" "Voiced :15" "Voiced :30" "Voiced :60" |
operator: "term" field: "spotTypeName" value: "Bonus" |
| programId | string | The unique ID associated with the program. | operator: "term" field: "programId" value: "22979" |
| programName.raw | string | The user-defined name of the program. | operator: "term" field: "programName.raw" value: "Morning Drive - MF 10a1p" |
| impressions | integer | The audience count. | operator: "term" field: "impressions" value: "8" |
| audienceMarketCount | integer | The number of markets where the media was broadcast. | operator: "term" field: "audienceMarketCount" value: "2" |
| audienceAffiliateCount | integer | The number of affiliates for the primary media source. | operator: "term" field: "audienceAffiliateCount" value: "1" |
| rating | float | The number of user-given stars to a watchlist mention. Possible values: "1" "2" "3" "4" "5" |
operator: "term" field: "rating" value: "5" |
| ratings.rating_id | string | The unique ID of the mention rating. | operator: "term" field: "ratings.rating_id" value: "38387" |
| ratings.rating_value | integer | The number user-given stars to a watchlist mention. Possible values: "1" "2" "3" "4" "5" |
operator: "term" field: "ratings.rating_value" value: "5" |
| ratings.date\_created | type: date format: date_ optional_time | The date and time that the mention rating was created. · The date is mandatory and the time is optional. · UTC time zone · Date format: "yyyy-mm-dd" · The time element "T" must follow the date when adding a time to the value. · Time format: hh/mm/ss/ms · Uses the term, query_string or range operators. |
operator: "range" field: "ratings.date_created" lte: "2017-10-13T00:12:34.44948" |
| comments.id | string | The unique ID of the comment. | operator: "term" field: "comments.id" value: "43770" |
| comments.text | string | Text entered as the mention comment. · Value must be entered as all lowercase. · Uses both the term and query_string operators. |
operator: "query_string" field: "comments.text" value: "provides information" |
| comments.date\_modified | type: date format: date_ optional_time | The date and time that the comment was created. · The date is mandatory and the time is optional. · UTC time zone. · Date format: "yyyy-mm-dd" · The time element "T" must follow the date when adding a time to the value. · Time format: hh/mm/ss/ms · Uses the term, query_string or range operators. |
operator: "range" field: "comments.date_modified" lte: "2017-10-20T01:43:35.0909" |
| markets.marketId | integer | The market ID to use as a filter when searching for mentions. (See "Appendix 2: Markets" for a list of all market name values.) · Uses term and range operators. |
operator: "term" field: "markets.marketId" value: "112" |
| markets.marketName | string | The market name to use as a filter when searching for mentions. (See "Appendix 2: Markets" for a list of all market name values.) | operator: "term" field: "markets.marketName" value: "Los Angeles, CA" |
| marketId | integer | The market ID to use as a filter when searching for mentions. (See "Appendix 2: Markets" for a list of all market name values.) · Uses term and range operators. |
operator: "term" field: "marketId" value: "112" |
| marketName | string | The market name to use as a filter when searching for mentions. (See "Appendix 2: Markets" for a list of all market name values.) | operator: "term" field: "marketName" value: "Los Angeles, CA" |
| hourOfDay | integer | The hour of day (24-hour format) to use as a filter when searching for mentions. | operator: "term" field: "hourOfDay" value: "8" |
| dayOfWeek | integer | The numeric value assigned to a day of the week to use as a filter when searching for mentions. · Uses the range and term operators. Possible values: "1" (Monday) "2" (Tuesday) "3" (Wednesday) "4" (Thursday) "5" (Friday) "6" (Saturday) "7" (Sunday) |
operator: "term" field: "dayOfWeek" value: "4" |
| dayOfMonth | integer | The numeric value assigned to a day of the month to use as a filter when searching for mentions. · Uses the range and term operators. |
operator: "term" field: "dayOfMonth" value: "13" |
| month | integer | The numeric value assigned to a calendar month to use as a filter when searching for mentions. · Uses the range and term operators. |
operator: "term" field: "month" value: "4" |
| year | integer | A four-digit year to use as a filter when searching for mentions. · Uses the range and term operators. |
operator: "range" field: "month" gte: "2015" |
| mentionStatusName | string | A mention status to use as a filter when searching for mentions. · Values are case sensitive and must use initial caps. Possible values: "Pending Verification" "Auto Verified" "Invalid" "Needs Review" "Processing Verification" "Request Bonus" "Verified" |
operator: "term" field: "mentionStatusName" value: "Verified" |
| Searches for records generated by a facial engine and other detected face attributes. | |||
| face-recognition.source | string | The ID of the face recognition engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "facial" as the value, and specify "id" and "name" as return fields. | operator: "term" field: "face-recognition.source" value: "84b513bd-d64d-3a35-9d42-579c8611fdbf" |
| face-recognition.series.entityId | string | The unique ID associated with the library entity (such as a person or an organization). | operator: "term" field: "face-recognition.series.entityId" value: "423aa55e-6135-4f10-9585-f65a1f3d909e" |
| face-recognition.series.start | string | The time in milliseconds from the beginning of the file where the fingerprint began. · Uses range and term operators. |
operator: "value" field: "face-recognition.series.start" lte: "54000" |
| face-recognition.series.end | string | The time in milliseconds from the beginning of the file where the fingerprint ended. · Uses range and term operators. |
operator: "value" field: "face-recognition.series.end" gte: "55000" |
| face-recognition.series.libraryId | string | The unique ID associated with the library. | operator: "term" field: "face-recognition.series.libraryId" value: "0fb02432-dcb1-40b0-bb6a-3f7e481aae3e" |
| face-recognition.series.originalImage | string | The URL of the library cover image. | operator: "term" field: "face-recognition.series.originalImage" value: "https://s3-us-west-1.amazonaws.com/prod-veritone-face/aed3ce42-97d0-46f1-89f9-48df4ba0ace2/35914952/318af5mf.983887/setId-0_frame-792.png" |
| Searches for records generated by a fingerprint engine and other detected fingerprint attributes. | |||
| fingerprint.source | string | The ID of the fingerprint engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "fingerprint" as the value, and specify "id" and "name" as return fields. |
operator: "term" field: "fingerprint.source" value: "c5eff1ad-d53e-8bb9-fb1f-1866da84d0b3" |
| fingerprint.series.start | integer | The time in milliseconds from the beginning of the file where the fingerprint began. · Uses range and term operators. |
operator: "range" field: "fingerprint.series.start" lte: "22000" |
| fingerprint.series.end | integer | The time in milliseconds from the beginning of the file where the fingerprint ended. · Uses range and term operators. |
operator: "range" field: "fingerprint.series.end" gte: "21000" |
| fingerprint.series.entityId | string | The unique Entity ID associated with the fingerprint. | operator: "term" field: "fingerprint.series.entityId" value: "e49c5344-622b-42bb-8e82-514d96d2df88" |
| fingerprint.series.entityIdentifierId | string | The unique Entity Identifier ID associated with the fingerprint. | operator: "term" field: "fingerprint.series.entityIdentifierId" value: "e4f95339-622b-42bb-8e82-514d96d2df88" |
| fingerprint.series.libraryId | string | The Library ID associated with the fingerprint. | operator: "term" field: "fingerprint.series.libraryId" value: "c034a463-2a82-4be5-b263-61f3b61e5282" |
| fingerprint.series.score | float | A probability score that indicates the similarity between features in a fingerprint sample and a stored entity. This score can be used as a filter to prioritize more salient fingerprints when searching. Scores closer to 0.0 are less similar, while scores closer to 1.0 are high in similarity. · Uses range and term operators. |
operator: "range" field: "fingerprint.series.score" gte: ".055" |
| Searches for records generated by a logo engine and other detected logo attributes. | |||
| logo-recognition.source | string | The ID of the logo recognition engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "logo recognition" as the value, and specify "id" and "name" as return fields. |
operator: "term" field: "logo-recognition.source" value: "bf50303a-55f1-5a27-17a1-d213ae0c7f55" |
| logo-recognition.series.found | string | The name of the detected logo. · Case-sensitive – value must match indexed logo name. | operator: "query_string" field: "logo-recognition.series.found" value: "ESPN" |
| logo-recognition.series.start | integer | The time that the logo was first identified in milliseconds from the beginning of the recording. · Uses range operator only. |
operator: "range" field: "logo-recognition.series.start" gte: "20700" |
| logo-recognition.series.end | integer | The time that the logo was last identified in milliseconds from the beginning of the recording. · Uses range operator only. |
operator: "range" field: "logo-recognition.series.end" lte: "20800" |
| Searches for records generated by an object recognition engine and various attributes of detected objects. | |||
| object-recognition.source | string | The ID of the object recognition engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "object detection" as the value, and specify "id" and "name" as return fields. |
operator: "term" field: "object-recognition.source" value: "070148f0-3fd0-1bdc-b412-1e79b8aa36a2" |
| object-recognition.series.boundingPoly.x | string | The "x" coordinate of the object found on the screen. · Uses range operator. |
operator: "range" field: "object-recognition.series.boundingPoly.x" lte: "418" |
| object-recognition.series.boundingPoly.y | string | The "y" coordinate of the object found on the screen. · Uses range operator. |
operator: "range" field: "object-recognition.series.boundingPoly.y" gte: "269" |
| object-recognition.series.found | string | A label for the detected object. (e.g., person, laptop) | operator: "term" field: "object-recognition.series.found" value: "girl" |
| object-recognition.series.start | string | The time in milliseconds from the beginning of the file where the object was first identified. · Uses range and term operators. |
operator: "range" field: "object-recognition.series.start" gte: "59000" |
| object-recognition.series.end | string | The time in milliseconds from the beginning of the file where the object was last identified. · Uses range and term operators. |
operator: "range" field: "object-recognition.series.end" lte: "60000" |
| object-recognition.series.saliency | float | A probability score that measures the similarity of a recognized object to a reference model. This score can be used as a filter to prioritize more salient objects when searching. Scores closer to 0.0 are less similar, while scores closer to 1.0 are high in similarity. · Uses range and term operators. |
operator: "range" field: "object-recognition.series.saliency" gte: "80" |
| Searches for records generated by an OCR engine and performs full-text search for various attributes of recognized text. All queries should use the query_string operator. | |||
| text-recognition.source | string | The ID of the text recognition engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "text recognition" as the value, and specify "id" and "name" as return fields. |
operator: "term" field: "text-recognition.source" value: "9a6ac62d-a881-8884-6ee0-f15ab84fcbe2" |
| text-recognition.series.start | integer | The time in milliseconds from the beginning of the file where the text was first recognized. · Uses range and term operators. |
operator: "range" field: "text-recognition.series.start" gte: "544000" |
| text-recognition.series.end | integer | The time in milliseconds from the beginning of the file where the text was last recognized. · Uses range and term operators. |
operator: "range" field: "text-recognition.series.end" lte: "545000" |
| text-recognition.series.ocrtext | string | One or more identified words displayed as text. · Value must be all lowercase. · Uses term and query_string operators. |
operator: "term" field: "text-recognition.series.ocrtext" value: "diego" |
| Searches for records generated by a sentiment engine and other attributes for detected sentiment. | |||
| sentiment-veritone.source | string | The ID of the sentiment engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "sentiment" as the value, and specify "id" and "name" as return fields. |
operator: "term" field: "sentiment-veritone.source" value: "104a6b61-5d7d-8a1c-fa32-d37b4c931e7c" |
| sentiment-veritone.series.start | string | The time in milliseconds from the beginning of the file where the sentiment was first detected. · Uses range and term operators. |
operator: "range" field: "sentiment-veritone.series.start" lte: "84000" |
| sentiment-veritone.series.end | string | The time in milliseconds from the beginning of the file where the sentiment was last detected. · Uses range and term operators. |
operator: "range" field: "sentiment-veritone.series.start" gte: "844690" |
| sentiment-veritone.series.score | float | A probability score that measures the similarity of a person’s sentiment to a reference model. This score can be used as a filter to prioritize more salient instances when searching. Scores closer to 0.0 are less similar, while scores closer to 1.0 are high in similarity. The value must include 0 before the decimal. · Uses range and term operators. |
operator: "range" field: "sentiment-veritone.series.start" gte: 0.81 |
| Searches for records generated by a transcription engine and words/phrases in a transcript. | |||
| transcript.source | string | The ID of the transcription engine to use as a filter when searching. For a list of possible values, make a request to the Engines query. Pass "category" as an argument with "transcription" as the value, and specify "id" and "name" as return fields. |
operator: "term" field: "transcript.source" value: "818aa3da-0123-33a4-8c5b-2bc3e569c52a" |
| transcript.transcript | string | This field is used to find keywords or phrases in transcription text. · Value must be entered as lowercase. |
operator: "query_string" field: "transcript.transcript" value: "so you know atom" |
| Searches for user-created tags. This field’s values are case-sensitive and must be entered exactly as they appear in Veritone to return a match. | |||
| tags.key | string | This field is part of a key value pair (using the query object type and value field below) in a complex query. | operator: "term" field: "tags.key" value: "host" |
| tags.value | string | This field can be used in a complex query as part of a key value pair (using the query object type and key field above) or as a stand-alone in a simple query. | operator: "term" field: "tags.value" value: "Ellen" |
| tags.displayName | string | This field is used in simple queries to find a tag by name. | operator: "term" field: "tags.displayName" value: "Adam Levine" |
| Search options for various aspects of tasks run on a recording. | |||
| veritone-job.insert-into-index | boolean | Searches for tasks that were indexed when set to true. | operator: "term" field: "veritone-job.insert-into-index" value: true |
| veritone-job.mention-generate | boolean | Searches for tasks that generated a mention when set to true. | operator: "term" field: "veritone-job.mention-generate" value: true |
| veritone-job.status | string | The status of the job as a whole. Possible values are: · accepted: The job is valid and has been accepted for processing. · running: The job is running. · failed: At least one task failed and execution was terminated. · complete: All tasks in the job finished normally. |
operator: "term" field: "veritone-job.status" value: "complete" |
| veritone-job.{engineId} | boolean | Returns jobs for the stated engine ID when set to true. For a list of possible engine ID values, call the Engines query. Pass "records" as a request parameter and "id" and "name" as return fields. |
operator: "term" field: "veritone-job.imagedetection-facerecognition-veritone" value: true |
| Full text search for various attributes of files imported to CMS. | |||
| veritone-file.filename | string | The name of the file. Value must be input as all lowercase. | operator: "term" field: "veritone-file.filename" value: "morning drive 15" |
| veritone-file.mimetype | string | The file type. Value must be input as all lowercase. | operator: "term" field: "veritone-file.mimetype" value: "video/mp4" |
| veritone-file.size | long | The size of the file. | operator: "term" field: "veritone-file.size" value: 0 |
| Searches various aspects of nationally broadcasted programs. | |||
| veritone-public.isNational | boolean | Specifies whether a program is national when set to true. | operator: "term" field: "veritone-public.isNational" value: true |
| veritone-public.marketCount | integer | Searches for a specific number of markets. | operator: "term" field: "veritone-public.marketCount" value: "3" |
| veritone-public.markets | string | Searches for recordings in specified markets. Refer to "Appendix 2: Markets" for a list of possible values. | operator: "terms" field: "veritone-public.markets" values: ["88", "50", "167"] |
| veritone-public.primaryMarket | string | Searches for recordings in the specified primary market. Refer to "Appendix 2: Markets" for a list of possible values | operator: "term" field: "veritone-public.primaryMarket" value: "167" |
| veritone-public.primaryState | string | Searches for recordings in the specified primary US state. Enter values using the two-letter state abbreviation. | operator: "term" field: "veritone-public.primaryState" value: "CA" |
| veritone-public.stateCount | integer | Searches for a specific number of states. | operator: "term" field: "veritone-public.stateCount" value: "3" |
| veritone-public.states | string | Searches for recordings in the specified US states. Enter values using the two-letter state abbreviation. | operator: "terms" field: "veritone-public.states" values: ["CA", "NY", "WA"] |
The following list provides the possible market ID values for the veritone-public.markets and veritone-public.primaryMarket fields in Appendix 1.
| Market ID/Market Name | Market ID/Market Name |
| "1" "Abilene-Sweetwater, TX" "2" "Albany-Schenectady-Troy, NY" "3" "Albany, GA" "4" "Albuquerque-Santa Fe, NM" "5" "Alexandria, LA" "6" "Alpena, MI" "7" "Amarillo, TX" "8" "Anchorage, AK" "9" "Atlanta, GA" "10" "Augusta, GA" "11" "Austin, TX" "12" "Bakersfield, CA" "13" "Baltimore, MD" "14" "Bangor, ME" "15" "Baton Rouge, LA" "16" "Beaumont-Port Arthur, TX" "17" "Bend, OR" "18" "Billings, MT" "19" "Biloxi-Gulfport, MS" "20" "Binghamton, NY" "21" "Birmingham, AL" "22" "Bluefield-Beckley-Oak Hill, WV" "23" "Boise, ID" "24" "Boston, MA" "25" "Bowling Green, KY" "26" "Buffalo, NY" "27" "Burlington, VT-Plattsburgh, NY" "28" "Butte-Bozeman, MT" "29" "Casper-Riverton, WY" "30" "Cedar Rapids-Waterloo-Iowa City-Dubuque, IA" "31" "Champagne-Springfield-Decatur, IL" "32" "Charleston-Huntington, WV" "33" "Charleston, SC" "34" "Charlotte, NC" "35" "Charlottesville, VA" "36" "Chattanooga, TN" "37" "Cheyenne, WY-Scottsbluff, NE" "38" "Chicago, IL" "39" "Chico-Redding, CA" "40" "Cincinnati, OH" "41" "Clarksburg-Weston, WV" "42" "Cleveland-Akron, OH" "43" "Colorado Springs-Pueblo, CO" "44" "Columbia-Jefferson City, MO" "45" "Columbia, SC" "46" "Columbus-Tupelo-West Point, MS" "47" "Columbus, GA" "48" "Columbus, OH" "49" "Corpus Christi, TX" "50" "Dallas-Ft. Worth, TX" "51" "Davenport, IA-Rock Island-Moline, IL" "52" "Dayton, OH" "53" "Denver, CO" "54" "Des Moines-Ames, IA" "55" "Detroit, MI" "56" "Dothan, AL" "57" "Duluth, MN-Superior, WI" "58" "El Paso, TX" "59" "Elmira, NY" "60" "Erie, PA" "61" "Eugene, OR" "62" "Eureka, CA" "63" "Evansville, IN" "64" "Fairbanks, AK" "65" "Fargo-Valley City, ND" "66" "Flint-Saginaw-Bay City, MI" "67" "Fresno-Visalia, CA" "68" "Ft. Myers-Naples, FL" "69" "Ft. Smith-Fayetteville-Springdale-Rogers, AR" "70" "Ft. Wayne, IN" "71" "Gainesville, FL" "72" "Glendive, MT" "73" "Grand Junction-Montrose, CO" "74" "Grand Rapids-Kalamazoo-Battle Creek, MI" "75" "Great Falls, MT" "76" "Green Bay-Appleton, WI" "77" 8Greensboro-High Point-Winston Salem, NC" "78" "Greenville-New Bern-Washington, NC" "79" "Greenville-Spartanburg, SC-Asheville, NC" "80" "Greenwood-Greenville, MS" "81" "Harlingen-Weslaco-Brownsville-McAllen, TX" "82" "Harrisburg-Lancaster-Lebanon-York, PA" "83" "Harrisonburg, VA" "84" "Hartford-New Haven, CT" "85" "Hattiesburg-Laurel, MS" "86" "Helena, MT" "87" "Honolulu, HI" "88" "Houston, TX" "89" "Huntsville-Decatur-Florence, AL" "90" "Idaho Falls-Pocatello, ID" "91" "Indianapolis, IN" "92" "Jackson, MS" "93" "Jackson, TN" "94" "Jacksonville, FL" "95" "Johnstown-Altoona, PA" "96" "Jonesboro, AR" "97" "Joplin, MO-Pittsburg, KS" "98" "Juneau, AK" "99" "Kansas City, KS-MO" "100" "Knoxville, TN" "101" "La Crosse-Eau Claire, WI" "102" "Lafayette, IN" "103" "Lafayette, LA" "104" "Lake Charles, LA" "105" "Lansing, MI" "106" "Laredo, TX" "107" "Las Vegas, NV" |
"108" "Lexington, KY" "109" "Lima, OH" "110" "Lincoln-Hastings-Kearney, NE" "111" "Little Rock-Pine Bluff, AR" "112" "Los Angeles, CA" "113" "Louisville, KY" "114" "Lubbock, TX" "115" "Macon, GA" "116" "Madison, WI" "117" "Mankato, MN" "118" "Marquette, MI" "119" "Medford-Klamath Falls, OR" "120" "Memphis, TN" "121" "Meridian, MS" "122" "Miami – Ft. Lauderdale, FL" "123" "Milwaukee, WI" "124" "Minneapolis – St. Paul, MN" "125" "Minot-Bismarck-Dickinson, ND" "126" "Missoula, MT" "127" "Mobile, AL-Pensacola, FL" "128" "Monroe, LA-El Dorado, AR" "129" "Monterey-Salinas, CA" "130" "Montgomery, AL" "131" "Myrtle Beach-Florence, SC" "132" "Nashville, TN" "133" "New Orleans, LA" "134" "New York, NY" "135" "Norfolk-Portsmouth-Newport News, VA" "136" "North Platte, NE" "137" "Odessa-Midland, TX" "138" "Oklahoma City, OK" "139" "Omaha, NE" "140" "Orlando-Daytona Beach-Melbourne, FL" "141" "Ottumwa, IA-Kirksville, MO" "142" "Paducah-Cape Girardeau-Harrisburg-Mt Vernon" "143" "Palm Springs, CA" "144" "Panama City, FL" "145" "Parkersburg, WV" "146" "Peoria-Bloomington, IL" "147" "Philadelphia, PA" "148" "Phoenix, AZ" "149" "Pittsburgh, PA" "150" "Portland-Auburn, ME" "151" "Portland, OR" "152" "Presque Isle, ME" "153" "Providence, RI-New Bedford, MA" "154" "Quincy, IL-Hannibal, MO-Keokuk, IA" "155" "Raleigh-Durham, NC" "156" "Rapid City, SD" "157" "Reno, NV" "158" "Richmond-Petersburg, VA" "159" "Roanoke-Lynchburg, VA" "160" "Rochester, MN-Mason City, IA-Austin, MN" "161" "Rochester, NY" "162" "Rockford, IL" "163" "Sacramento-Stockton-Modesto, CA" "164" "Salisbury, MD" "165" "Salt Lake City, UT" "166" "San Angelo, TX" "167" "San Antonio, TX" "168" "San Diego, CA" "169" "San Francisco-Oakland-San Jose, CA" "170" "Santa Barbara-Santa Maria-San Luis Obispo," "171" "Savannah, GA" "172" "Seattle-Tacoma, WA" "173" "Sherman, TX – Ada, OK" "174" "Shreveport, LA" "175" "Sioux City, IA" "176" "Sioux Falls-Mitchell, SD" "177" "South Bend-Elkhart, IN" "178" "Spokane, WA" "179" "Springfield-Holyoke, MA" "180" "Springfield, MO" "181" "St. Joseph, MO" "182" "St. Louis, MO" "183" "Syracuse, NY" "184" "Tallahassee, FL-Thomasville, GA" "185" "Tampa-St Petersburg-Sarasota, FL" "186" "Terre Haute, IN" "187" "Toledo, OH" "188" "Topeka, KS" "189" "Traverse City-Cadillac, MI" "190" "Tri-Cities, TN-VA" "191" "Tucson, AZ" "192" "Tulsa, OK" "193" "Twin Falls, ID" "194" "Tyler-Longview, TX" "195" "Utica, NY" "196" "Victoria, TX" "197" "Waco-Temple-Bryan, TX" "198" "Washington, DC" "199" "Watertown, NY" "200" "Wausau-Rhinelander, WI" "201" "West Palm Beach-Ft. Pierce, FL" "202" "Wheeling, WV- Steubenville, OH" "203" "Wichita – Hutchinson, KS" "204" "Wichita Falls, TX –Lawton, OK" "205" "Wilkes Barre-Scranton, PA" "206" "Wilmington, NC" "207" "Yakima-Pasco-Richland-Kennewick, WA" "208" "Youngstown, OH" "209" "Yuma, AZ-El Centro, CA" "210" "Zanesville, OH" "211" "Adelaide, SA" "212" "Melbourne, VIC" "213" "Brisbane, QLD" |

