Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions mcp-server.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -284,6 +284,10 @@ validation, routing, failover, pricing, and billing are identical.

For long-running work, `run_api` waits briefly, then returns a Request ID with a
`nextAction`. Call `get_request` instead of repeating `run_api`.

`linkedin.ads_search` may also return a `date_adjusted:` hint with the dates used
for your search. These dates remain unchanged on replay. See
[LinkedIn ad date filters](/quickstart#linkedin-ad-date-filters).
</Accordion>
<Accordion title="get_request - resume durable work" icon="clock">
Retrieve a durable Request by ID. It never repeats the paid operation.
Expand Down
11 changes: 11 additions & 0 deletions quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,17 @@ yourself, follow the steps below.
</Step>
</Steps>

## LinkedIn ad date filters

For `linkedin.ads_search`, LinkedIn accepts `startDate` and `endDate` from one year ago
through yesterday in UTC. If your date range overlaps that window, AnyAPI moves an earlier
start date forward and moves today or a later end date back to yesterday. The response's
optional `hint` starts with `date_adjusted:` and names the adjusted dates used for your search.
The dates stay the same if the response arrives after midnight or you replay the request.

A reversed range or a range with no accepted day is rejected before the search. You are not
charged for that rejection.

## Find an API

To browse by eye, start at [the full catalog](https://getanyapi.com/catalog) or a
Expand Down
Loading