/applications/status/

Used to understand API usage

• key (query, required) — User application key

/reports/

Obtain report output

• report_hash (query, required) — Unique report hash
• baseline (query) — Default value will be 'world'
• report_date (query) — report_date represents a Unix timestamp of when the report was generated. Default value will be the latest report generated. You can request the /report/dates/ endpoint in order to obtain available timestamps. Date must be in the future.
• sample (query, required) — Sample report indicator

/reports/

Obtain report output

• report_hash (query, required) — Unique report hash
• baseline (query) — Default value will be 'world'
• report_date (query) — report_date represents a Unix timestamp of when the report was generated. Default value will be the latest report generated. You can request the /report/dates/ endpoint in order to obtain available timestamps. Date must be in the future.
• sample (query, required) — Sample report indicator

/reports/custom/create/

Step 3 of executing custom report

• upload_hash (query, required) — Upload hash to be used for inserting handles
• filter (query) — Filtering options to be used when creating a filtered report. The options must be in JSON form, example: {'gender':['male'],'ages':['18-24'],'countries':['usa']}

/reports/custom/create/

Step 3 of executing custom report

• upload_hash (query, required) — Upload hash to be used for inserting handles
• filter (query) — Filtering options to be used when creating a filtered report. The options must be in JSON form, example: {'gender':['male'],'ages':['18-24'],'countries':['usa']}

/reports/custom/generate/

Step 1 of executing custom report

• report_name (query, required) — Name of the report

/reports/custom/generate/

Step 1 of executing custom report

• report_name (query, required) — Name of the report

/reports/custom/insert/

Step 2 of executing custom report

• upload_hash (query, required) — Upload hash to be used for inserting handles
• ids (query, required) — List of twitter ids, separated by commas, to be inserted into report. Ids must be enclosed with brackets ie. [177490485] or [177490485,23423434]

/reports/custom/insert/

Step 2 of executing custom report

• upload_hash (query, required) — Upload hash to be used for inserting handles
• ids (query, required) — List of twitter ids, separated by commas, to be inserted into report. Ids must be enclosed with brackets ie. [177490485] or [177490485,23423434]

/reports/dates/

Get report dates available for a specific report

• report_hash (query, required) — Unique report hash

/reports/dates/

Get report dates available for a specific report

• report_hash (query, required) — Unique report hash

/reports/status/

Get list of generated reports

• report_hash (query, required) — Unique hash belonging to report

/reports/status/

Get list of generated reports

• report_hash (query, required) — Unique hash belonging to report

/reports/tweet/create/

Used to create tweet reports

• report_name (query, required) — Name of report
• start_date (query, required) — A unix timestamp. start_date will be set to the previous midnight.
• end_date (query, required) — A unix timestamp. end_date will be set to the next midnight.
• terms (query, required) — If you are tracking a single term, then the keyword itself is suffice otherwise, tracking multiple terms must be in JSON form, example '[{"operator":"","word":"http://google.com"},{"operator":"or","word":"#test"},{"operator":"and","word":"test2"}]' Which results in filtering tweets containing 'http://google.com' OR '#test' AND 'test2'. (NOTE) Make sure to URL encode the terms value for multiple terms.
• filter (query) — Filtering options to be used when creating a filtered report. The options must be in JSON form, example: {'gender':['male'],'ages':['18-24'],'countries':['usa']}

/reports/tweet/create/

Used to create tweet reports

• report_name (query, required) — Name of report
• start_date (query, required) — A unix timestamp. start_date will be set to the previous midnight.
• end_date (query, required) — A unix timestamp. end_date will be set to the next midnight.
• terms (query, required) — If you are tracking a single term, then the keyword itself is suffice otherwise, tracking multiple terms must be in JSON form, example '[{"operator":"","word":"http://google.com"},{"operator":"or","word":"#test"},{"operator":"and","word":"test2"}]' Which results in filtering tweets containing 'http://google.com' OR '#test' AND 'test2'. (NOTE) Make sure to URL encode the terms value for multiple terms.
• filter (query) — Filtering options to be used when creating a filtered report. The options must be in JSON form, example: {'gender':['male'],'ages':['18-24'],'countries':['usa']}

/reports/twitter/create/

Used to create twitter follower report

• twitter_id (query) — (required if twitter_handle is not supplied) twitter_id must be sent with all client requests. Multiple handles are separated by commas.
• twitter_handle (query) — (required if twitter_id is not supplied) twitter_handle must be sent with all client requests. Multiple ids are separated by commas.
• filter (query) — Filtering options to be used when creating a filtered report. The options must be in JSON form, example: {'gender':['male'],'ages':['18-24'],'countries':['usa']}

/reports/twitter/create/

Used to create twitter follower report

• twitter_id (query) — (required if twitter_handle is not supplied) twitter_id must be sent with all client requests. Multiple handles are separated by commas.
• twitter_handle (query) — (required if twitter_id is not supplied) twitter_handle must be sent with all client requests. Multiple ids are separated by commas.
• filter (query) — Filtering options to be used when creating a filtered report. The options must be in JSON form, example: {'gender':['male'],'ages':['18-24'],'countries':['usa']}