Query content requests

Returns the content requests of your workspace, most recent first, filtered by the JSON body you send. The list is paged with a cursor: send meta.cursor.next back as cursor until meta.cursor.has_more is false. It returns 25 content requests per page by default: set limit (up to 100) to get more or fewer.

Route

POST/api/v3/content-requests/query

Access modes

Use a workspace API key. The workspace is inferred from the key.

Authorization: Bearer sk_live_...

Body parameters

Every field is optional: an empty body returns the first page of every content request. A field that is not listed is refused with 422.

Field	Type	Description
cursor	string	The `meta.cursor.next` of the previous response, to fetch the next page. Omit it for the first page. It only works with the filters it was issued for: reused with other filters, or sent empty, it is refused with `422`. See Pagination.
limit	integer	Number of items per page, from 1 to 100. Defaults to 25.
created_at_from	string	Only requests created at or after this moment. ISO 8601 date and time with a UTC offset, for example `2026-09-01T00:00:00Z`. A date without a time is refused with `422`. Both bounds are included.
created_at_to	string	Only requests created at or before this moment. ISO 8601 date and time with a UTC offset, for example `2026-09-01T00:00:00Z`. A date without a time is refused with `422`. Both bounds are included.
type	string	Only requests of this type: `account_mapping` or `key_account_content`.
statuses	string[]	Only requests in one of these statuses: `pending`, `in_progress`, `completed`, `failed`. There is no default: when you leave it out, every request is returned, finished ones included.
company_ids	integer[]	Only results whose company is one of these companies. Pass company IDs, as returned by Query companies. Between 1 and 100 values.
company_domains	string[]	Only results whose company has one of these website domains, for example `acme.com`. Between 1 and 100 values.
company_linkedin_handles	string[]	Only results whose company has one of these LinkedIn handles, the last part of the LinkedIn page address. Between 1 and 100 values.
company_linkedin_urls	string[]	Only results whose company has one of these LinkedIn page URLs. Between 1 and 100 values.

The four company filters add up: a result matches when its company is any of the company_ids, or has any of the domains, LinkedIn handles or LinkedIn URLs you send. A value that matches no company in your workspace matches nothing, so the answer is an empty list, never an error. The company filters and every other filter all have to match.

Requests are sorted from the newest to the oldest. Requests created at the same moment keep a stable order, so no request is skipped or repeated from one page to the next.

Example request

curl -X POST "https://api.getsillage.com/api/v3/content-requests/query" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":10,"type":"account_mapping","statuses":["pending","in_progress"],"company_domains":["acme.com","example.com"]}'

Success response

Status: 200 OK

{
  "data": [
    {
      "id": 43821,
      "type": "account_mapping",
      "status": "in_progress",
      "label": "Mapping the account",
      "failed_reason": null,
      "persona_ids": [12],
      "created_at": "2026-06-12T08:30:00.000Z",
      "updated_at": "2026-06-12T09:10:00.000Z",
      "company": {
        "id": 8421,
        "name": "Acme",
        "domain": "acme.com",
        "linkedin_url": "https://www.linkedin.com/company/acme",
        "linkedin_handle": "acme",
        "logo_url": "https://example.com/acme-logo.png"
      }
    },
    {
      "id": 43790,
      "type": "account_mapping",
      "status": "pending",
      "label": "Waiting to start",
      "failed_reason": null,
      "persona_ids": [12],
      "created_at": "2026-06-12T08:30:00.000Z",
      "updated_at": "2026-06-12T08:52:00.000Z",
      "company": {
        "id": 8421,
        "name": "Acme",
        "domain": "acme.com",
        "linkedin_url": "https://www.linkedin.com/company/acme",
        "linkedin_handle": "acme",
        "logo_url": "https://example.com/acme-logo.png"
      }
    }
  ],
  "meta": {
    "cursor": {
      "next": null,
      "has_more": false
    },
    "resolved_companies": [
      {
        "company": {
          "id": 8421,
          "name": "Acme",
          "domain": "acme.com",
          "linkedin_url": "https://www.linkedin.com/company/acme",
          "linkedin_handle": "acme",
          "logo_url": "https://example.com/acme-logo.png"
        },
        "matched_by": "company_domains",
        "identifier": "acme.com"
      },
      {
        "company": {
          "id": 9103,
          "name": "Example",
          "domain": "example.com",
          "linkedin_url": "https://www.linkedin.com/company/example",
          "linkedin_handle": "example",
          "logo_url": null
        },
        "matched_by": "company_domains",
        "identifier": "example.com"
      }
    ]
  }
}

When nothing matches, data is an empty array and meta.cursor.has_more is false.

Response fields

Field	Type	Description
data[].id	integer	ID of the content request.
data[].type	string	What the request does: `account_mapping` or `key_account_content`.
data[].status	string	Where the request is: `pending`, `in_progress`, `completed` or `failed`. See Statuses.
data[].label	string	A short, readable description of the current step, for example `Mapping the account`, `Account mapping failed`, `Gathering content failed` or `Completed`. It is meant to be shown as is.
data[].failed_reason	string or null	Why a content request (`key_account_content`) failed, when its `status` is `failed`. Always `null` for an `account_mapping` request, and for any request that has not failed. See `failed_reason`.
data[].persona_ids	integer[]	IDs of the personas the request maps people for, as returned by List personas. Empty when none applies.
data[].created_at	string	When the request was created, in ISO 8601.
data[].updated_at	string	When the request last changed, in ISO 8601.
data[].company	object or null	The company the request is about.
data[].company.id	integer	ID of the company in your workspace.
data[].company.name	string or null	Name of the company.
data[].company.domain	string or null	Website domain of the company.
data[].company.linkedin_url	string or null	LinkedIn page of the company.
data[].company.linkedin_handle	string or null	LinkedIn handle of the company, the last part of its LinkedIn page address.
data[].company.logo_url	string or null	Logo of the company.
meta.cursor.next	string or null	Pass it as `cursor` to fetch the next page. `null` on the last page.
meta.cursor.has_more	boolean	`true` when more requests exist after this page, `false` on the last page.
meta.resolved_companies	array	The companies your company filters matched. See `meta.resolved_companies`.

Statuses

status	Meaning
pending	The request is waiting to start.
in_progress	The request is being worked on.
completed	The request is finished.
failed	The request stopped without completing. `failed_reason` says why.

`failed_reason`

Why a content request (key_account_content) failed, when its status is failed. It is always null for an account_mapping request, even a failed one, and for every request that has not failed.

Value	Meaning
`no_employee_resolved`	No employee matching your persona was found for this company.
`persona_without_job_titles`	Your persona has no job title: add one to map accounts.
`missing_linkedin_target`	The company had no usable LinkedIn page to work from.
`request_timed_out`	The request took too long and was stopped.
`insufficient_credits`	Your workspace ran out of credits before the request could complete.
`internal_error`	The request failed on our side. Contact support if it keeps failing.

`meta.resolved_companies`

Lists the companies your company filters matched, one entry per company and per filter value that matched it. It is an empty array when you send no company filter.

Field	Type	Description
company	object	The matched company, as a summary: `id` (its ID in your workspace), `name`, `domain`, `linkedin_url`, `linkedin_handle` and `logo_url`.
matched_by	string	The filter that matched this company: `company_ids`, `company_domains`, `company_linkedin_handles` or `company_linkedin_urls`.
identifier	string	The value you sent in that filter, a domain, a handle, a URL, or a company ID as a string.

Errors

Status	Meaning
401	The API key is missing or invalid.
422	The body is not valid: an unknown field, a value that is not allowed (for example a value in `statuses` that is not one of the four), a date without a time, a `limit` outside 1 to 100, or a `cursor` that was not issued to you by this endpoint, was issued for other filters, or is empty (`errors` then names `cursor`). A range that ends before it starts (`created_at_from` after `created_at_to`) is refused with the code `invalid_date_range`; `errors.created_at_from` says "must be on or before created_at_to".
429	Rate limit exceeded.
500	An unexpected server error occurred.

Error responses use RFC 9457 problem documents with Content-Type: application/problem+json. type is always about:blank; code tells one problem from another, detail says what went wrong this time, and errors names the field at fault. For example, with a statuses value that is not known:

{
  "type": "about:blank",
  "title": "Unprocessable Entity",
  "status": 422,
  "code": "invalid_body",
  "detail": "Invalid request body",
  "instance": "/api/v3/content-requests/query",
  "errors": {
    "statuses[0]": [
      "Invalid option: expected one of \"pending\"|\"in_progress\"|\"completed\"|\"failed\""
    ]
  }
}

Query content requests

On this page