Query Content Requests

Returns a paginated list of content requests for the workspace, newest first. Behaves exactly like List content requests, but takes its filters as a JSON body instead of query-string parameters — useful when a filter value (such as several company_domain values) is easier to send as a native array. By default, requests in every stage except completed are returned.

Query content requests

POST/api/v2/partner/workspaces/{partner_workspace_id}/content-requests/query

Path parameters

Parameter	Type	Description
partner_workspace_id	string	Opaque workspace identifier from the partner system.

Request body

All fields are optional.

Field	Type	Default	Description
page	integer	1	Page number. Must be greater than or equal to 1.
page_size	integer	25	Number of items per page. Must be between 1 and 100.
date_from	string (date-time)		Return requests created on or after this date (ISO 8601).
date_to	string (date-time)		Return requests created on or before this date (ISO 8601).
type	string		Filter by request type: `account_mapping` or `top_account_content`.
stage	array of string	all except completed	Filter by stage. Native JSON array.
company_id	integer		Filter by company id. Takes priority over the identifier fields below.
company_domain	array of string		Filter by company domain. Native JSON array, OR filtering across multiple companies.
company_linkedin_handle	array of string		Filter by company LinkedIn handle. Native JSON array.
company_linkedin_url	array of string		Filter by company LinkedIn URL. Native JSON array.

An unresolved company_domain, company_linkedin_handle, or company_linkedin_url never returns a 404 — it returns an empty page ("data": []).

Example request

curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/content-requests/query" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"page": 1, "page_size": 25, "type": "top_account_content"}'

Example response

{
  "data": [
    {
      "id": 7001,
      "type": "top_account_content",
      "stage": "completed",
      "created_at": "2026-06-12T09:00:00.000Z",
      "updated_at": "2026-06-12T10:00:00.000Z",
      "company": {
        "id": 456,
        "name": "Acme Inc",
        "domain": "acme.com",
        "linkedin_url": "https://www.linkedin.com/company/acme"
      },
      "inputs": {}
    }
  ],
  "meta": {
    "pagination": {
      "page": 1,
      "page_size": 25,
      "page_count": 1,
      "total": 1
    },
    "resolved_companies": []
  }
}

Response fields

Field	Type	Description
id	integer	Id of the content request.
type	string	Request type: `account_mapping` or `top_account_content`.
stage	string	Current processing stage. See Stages.
created_at	string	When the request was created (ISO 8601).
updated_at	string	When the request was last updated (ISO 8601).
company	object or null	The associated company, if any.
company.id	integer	Id of the company.
company.name	string or null	Company name.
company.domain	string or null	Company domain.
company.linkedin_url	string or null	Company LinkedIn URL.
inputs	any	Request-type-specific input payload.
meta.pagination.page	integer	Current page number.
meta.pagination.page_size	integer	Items per page.
meta.pagination.page_count	integer	Total number of pages.
meta.pagination.total	integer	Total number of matching content requests.
meta.resolved_companies	array	One entry per company identifier from the request body that resolved to a known company.

Errors

Status	Meaning
400	Invalid request body.
401	The master key is missing or invalid.
403	Top account content requests is not enabled for this workspace.
404	No workspace found for this `partner_workspace_id`.
429	Too many requests.
500	An unexpected server error occurred.

Error responses use RFC 9457 problem documents with Content-Type: application/problem+json.

Query Content Requests