post
https://api.marketcircle.net/v1/projects/_search
Search for projects
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
See the search filtering documentation for details about the query syntax. The searchable attributes and the operators each one accepts are listed in the request body below.
Project-specific notes
statustakes one ofnew_status,in_progress,deferred,cancelled,abandonedordone. New projects are returned with the statusnew, but search usesnew_status:
{ "status": { "any": ["new_status", "in_progress"] } }priority(0 to 10) andestimated_time(in seconds) are numbers and must be sent as JSON numbers:
{ "estimated_time": { "greater_than": 3600 } }categorymatches by name, e.g.{ "category": { "equal": "Internal" } }.- Contacts and companies take a search filter for that record type with
any, so you can match by reference or by any of its attributes:
{ "contacts": { "any": { "contact": { "equal": "/v1/contacts/1000" } } } }
{ "companies": { "any": { "name": { "contains": "Acme" } } } } opportunity(the opportunity the project was converted from) also takes an opportunity search filter, orblank/not_blank:
{ "opportunity": { "any": { "opportunity": { "equal": "/v1/opportunities/1000" } } } }- Linked records (
appointments,notes,tasks,groups,forms,email_messages) work the same way, using the linked record's reference:
{ "tasks": { "any": { "task": { "equal": "/v1/tasks/1000" } } } } rolematches the name of a role a contact or company has on the project.projectandproject_idmatch the project itself, by reference or by numeric ID.